#Nick Hamilton

1 messages · Page 1 of 1 (latest)

finite prawnBOT
loud iris
#

Hi 👋

Can you share an example Payment Intent ID/

plucky rivet
#

sure, py_1LriAt2UPWuaiOHApjIUWmyT

loud iris
#

Do you have a Charge or Payment Intent ID? They start with ch_ and pi_ respectively

plucky rivet
#

2 secs, must have

#

was this Payment Intent pi_3LriAYFBpd65PHq72vdR3CPr

#

(I say it was this, one example from many)

#

We set the statementDescriptor to "Kates Shop". This was an in house live test, it popped up on the tester's phone as a charge to a completely different business

loud iris
#

Okay I'm looking at the actual communication records with the issuing bank for the charge associated with that payment intent

#

I can see we sent them the card_acceptor_name as "KATES SHOP"

#

Unfortunately the bank decided to use something else to generate their statement descriptor. I am sorry to say this is something you or your customers will need to take up with the issuing bank.

#

Banks have their own rules and procedures for generating statement descriptors.

plucky rivet
#

OK, assuming that this is a caching type issue with the receiving bank we were wondering whether setting the on_behalf_of would help in this matter. We already set this for some customers who's currency doesn't match ours but didn't swap over wholesale as we weren't sure of the ramifications that this would have. What, if anything, would this change?

loud iris
#

If you are still specifying the statement descriptor in the Payment Intent then it wouldn't change what we send the bank in terms of that text. But it would send the details of the Connect Account instead of the Platform which the bank may use to determine which business the charge belongs to.