#prashanth

1 messages · Page 1 of 1 (latest)

drowsy sigilBOT
serene birch
#

Hi @floral junco

floral junco
#

Hi can you share a PaymentIntent example with the statement descriptor and what you are expecting ?

#

In the bank statement, the payment descriptor looks inconsistent with what we sent.
Unfortunately banks and card issuers will sometimes display the wrong friendly name for some transactions (statement descriptor).
Stripe has no control over the mapping systems banks and card issuers use to produce friendly names for their cardholders, and the friendly names displayed often use multiple data points from a transaction to determine which friendly name to display (only one of which may be the statement descriptor.

#

But let's double check first using a sample PaymentIntent

serene birch
#

Sure, I use stripe.payouts.create to create manual payouts

#

In this I add attribute {statement_descriptor: ${invoice_number} {customer_name} LFPay}

floral junco
#

Can you share an example of a Payout Id ?

#

and what was shown in the bank statement ? (screenshot)

serene birch
#

Yes sure

#

Please find here: po_1MhepsER2bUX4Lm9UIncyKI8

#

po_1MW7JWER2bUX4Lm9yVUAaeAR

floral junco
#

And the bank statement screenshot

#

But for Stripe point of view, the statement descriptor is sent correctly.

serene birch
serene birch
#

Yes but the bank description is not the same as the statement descriptor. Is there a way to show only the intended descriptor?

#

What is the reason to specifically pick the account's contact url when we already provide a framed statement descriptor?

floral junco
serene birch
#

Ok, Thanks. One more clarification for payment descriptor!

#

Similarly for payments I am trying to create a charge using stripe.charges.create() and the statement descriptor set to the charge is a dynamic one {statement_descriptor: ${bill_number} ${supplier_name}. I am passing the intended statement descriptor in my 'Request POST body' and hope to get a valid response. The problem is when I look at the bank statement the statement descriptor appends the static descriptor set in the Stripe dashboard. The static statement descriptor occupies the majority of the 22-char length and the dynamic descriptor which was set in code is hidden due to appending or truncating. example payment ID: py_1MWPPQ2EjgoXXYg24WnUVhel

floral junco
serene birch
#

Can I DM you?

floral junco
#

No we can continue to discuss here in this thread.

serene birch
#

Ok

#

May I know what mistake I am doing while sending the dynamic descriptors to stripe in both payment and payout. In both the cases the bank statement is not showing the one which I send to the stripe. It uses the settings/public/statement descriptor for payments and for payouts accounts/contact information/website?

rigid berry
#

Hi! I'm taking over this thread.

#

Can you share an object ID where you don't see the correct statment descriptor?

serene birch
#

payout: po_1MW7JWER2bUX4Lm9yVUAaeAR, I can see the valid statement descriptor in stripe portal. You can also confirm it with the payload and response for POST /v1/payouts for this particular payout but in my bank statements I don't see the descriptor which I set while creating a manual payout.
example of this payout inconsistent bank statement is attached

rigid berry
#

Got it. If the statement descriptor appears correctly on Stripe's end, it means it's the bank who is displaying the wrong statement description, which sometimes happen. So you would need to contact the bank directly to understand the issue.

serene birch
#

ok, Thank you.

#

Could you please keep this thread open? for few more mins?

rigid berry
#

We automatically close threads after some inactivity. But feel free to reopen a new thread if needed.

serene birch
#

For payments, Is prefix and suffix mandatory and should consists of 22 char long combined or prefix alone can be 22-char length to set a statement descriptor?