#Naresh Kumar
sly condor
jolly osprey
Hi 👋 can you elaborate a bit on what you're trying to accomplish? Are you trying to override the static prefix for your statement descriptors on a per-payment basis, or are you trying to change the static prefix for your account?
Additionally, is this for card payments, payments for other types of payment methods, or a mixture?
north gulch
Yeah I would love to explain
- We are trying to override the Static Statement descriptor with dynamic statement descriptor on a per-payment basis.
- If there is an option at the account level you could explain this also
- This statement descriptor is mix of both the Card and ACH Payments
jolly osprey
For card payments you will need to use a static prefix+dynamic suffix approach,
https://stripe.com/docs/account/statement-descriptors#dynamic
but for non-card payments you can pass a payment-specific statement descriptor via the statement_descriptor parameter when creating the Payment Intent:
https://stripe.com/docs/api/payment_intents/create#create_payment_intent-statement_descriptor
https://stripe.com/docs/account/statement-descriptors#set-the-statement-descriptor-on-non-card-charges
north gulch
Yes I do understand @jolly osprey
- Is there a way to completely change the statement descriptor and test for the test mode? since it is not allowing me to do so
jolly osprey
Can you elaborate? What are you trying to do, and what is the behavior that you're seeing versus what you were expecting?
north gulch
We are trying to have two statement descriptors for test mode and live mode. Is there any options from the Stripe UI to do this?
We are creating a Payment with a card using the "Prefix+dynamic suffix approach"
We have default Statement Descriptor as: "LABFELLOWS"
Shortend Descriptor is: LFPAY
Dynamic Statement Descriptor display like: LFPAY* <INVOICE_NUMBER> <VENDOR NAME>
WE ARE PASSING LIKE THIS
const paymentIntent = await stripe.paymentIntents.create({
amount: 5850,
currency: 'usd',
payment_method_types: ['card'],
statement_descriptor_suffix: 'Statement Descriptor which we are providing',
});
But when we check the bank transaction the Dynamic statement descriptor for the Payments made it look different
jolly osprey
Was the descriptor on the actual statement similar to what you entered? You don't have control over what the customer's bank/issuer decides to put on their statements, they ultimately control that, you provide them with what you believe would be a good descriptor.
north gulch
Yes we are providing what looks good for us. But when we export the transactions from the bank side and then see it is not what we have sent ?
But in the stripe dashboard it seems perfect like how we have coded
jolly osprey
Can you share an example of one of those payments, and what you expected the statement descriptor to be? I can double check whether what we sent matched what you entered.
north gulch
This is the payment we made to a customer
But in the customer bank statement descriptor (description) it looks like
EB-6622 ePIC BIO LABFELLOWS <some random digits appended from the bank side>
We are not sure from where it is picking up like this
jolly osprey
Everything I'm seeing on our side is showing the same descriptor that is shown in the body of the request that you shared. So I believe the bank is making a change to what is provided on their end.
north gulch
Which means what ever the Statement Descriptor we formed is maintaining throughout the Stripe application
For the Payment
Is my understanding correct?
jolly osprey
Correct
north gulch
Okay understood !!
Then its not a fault from our end on how the bank displays right?
One another doubt is
We are trying to have two statement descriptors using the Stripe Profile one for test mode and one for live mode. Is there any options from the Stripe UI to do this? Since we are unable to achieve those
jolly osprey
No, the statement descriptor values are shared between live and test mode.
north gulch
okay understood