#battbot.
1 messages · Page 1 of 1 (latest)
Hey there
It is really up to the issuer what they display
So if you are passing the correct Statement Descriptor then there really isn't anything further you can do
pi_3OaH5zJ93KfFVesb10BA33aY is the payment intent id, we set
PALGONG TEA BRANTFORD
but the end user is seeing Gino's Pizza
how can we explain to our customer what went wrong?
can how can it be corrected? Because this isn't the first time it's happened for this merchant, they frequently have this problem
Do they need to contact the banks? @whole rune
Taking a brief look
One moment
Yeah so you can see that the calculated_statement_descriptor is indeed PALGONG TEA BRANTFORD which means that is what we are passing along to the issuer.
So your integration is indeed handling everything correctly and it appears the issuer is just providing the wrong SD
So yeah, the only path forward would be to reach out to the issuer to ask them why they are doing this.
Overall this isn't the most uncommon thing in the world. Sometimes issuers attempt to be "smart" with their SD mappings and it gets messed up
ok Thank you