#Santhosh Kumar R
jovial mica
Hello! Can you give me some more details? When you say the statement doesn't display is it just that the credit card statement doesn't match the statement descriptors you set?
rapid copper
Yes you are right
the credit card doesnt reflect the statment that is display in the paymentintent object
jovial mica
Can you share an example payment intent ID with me?
wispy socketBOT
whole star
Taking a look for you
In your creation request you've included both a statement_descriptor and a statement_descriptor_suffix and the latter is what gets used for card payments
https://dashboard.stripe.com/logs/req_EEU69gXGmCPucW
https://stripe.com/docs/account/statement-descriptors#dynamic
You can inspect the calculated_network_descriptor on the PI latest_charge to see what Stripe ultimately sends with the payment: https://stripe.com/docs/api/charges/object#charge_object-calculated_statement_descriptor
Looking at this for this payment, it matches the static prefix + dynamic suffix provided
rapid copper
so based on the pi i gave it must have sent "Happy Travel Montreal FTS"
whole star
No, that's not what you find on the charge and not how the doc explains descriptors work
What do you see on the statement?
rapid copper
I see FTS* FTS
the calculated_statment_descriptor picks what?
the suffix?
i remember this working last month and only recently its not
/**
* Extra information about the payment. This will appear on your customer's statement when
* this payment succeeds in creating a charge.
*/
public Builder setStatementDescriptor(String statementDescriptor) {
this.statementDescriptor = statementDescriptor;
return this;
}
this is what the API confirms
whole star
I see FTS* FTS
That's what's on the charge, so that matches accurately
whole star
the calculated_statment_descriptor picks what?
The final combined result sent to the card network
the combination of the static prefix from your account settings and the dynamic suffix you specified
As explained here: https://stripe.com/docs/account/statement-descriptors