#Kinno-connect-statement-descriptors

1 messages · Page 1 of 1 (latest)

subtle horizon
#

Hey, do you have an example PI I can check?

frank tree
#

that might be hard for me to get at this very moment since I don't have prod access to stripe as a contractor 😅 Is there any other info that could potentially help while I try to get the payment intent id?

subtle horizon
#

What kind of Connect accounts and payments are you using?

frank tree
#

Custom accounts, with charge/transfer capabilities, we use ACH/BACH/*Card payments iirc, card -> payment intent and ACH/BACH -> charge

#

I should be able to debug why we get the facebook.com as descriptors for some accounts since it's likely just a bad setup somewhere for some connected accounts, I was just hoping to know if the workflow I described above is reasonable so we could avoid user mistakes and set the descriptor for them explicitly

subtle horizon
#

I was wondering if setting the statement descriptor prefix for ALL our connected accounts to the name of our *platform account and then using the dynamic suffix for the name of the specific connected account is allowed?
Is there somewhere that we advise against this?

frank tree
#

Not explicitly against, but the guide for statement descriptors documents 1 workflow only and I was wondering if there's a legality reason for it on your side

subtle horizon
#

Not AFAIK, it could just be confusing for end customers