#joshua.r-PaymentMethod

1 messages · Page 1 of 1 (latest)

cloud kiln
#

Normally it means the PaymentMethod Id you supplied doesn't exist. If you can provide a test request id req_xxx I can have a quick look

solid dock
#

req_ta8SyH3Kts5emg

cloud kiln
#

Okay I will try my best to explain

#

This request is a Connected Request, made by a Platform (acct_1ChTN1L9uALUbkBu) acting as a Connected account (acct_1KJVdmPrNLf50NMT)

#

However the used Payment method belongs to another connected account ( acct_1KHgspPtgiAdPDhw)

#

You need to use a PaymentMethod belongs to the first Connected account (acct_1KJVdmPrNLf50NMT)

solid dock
#

makes sense, I assumed it was something like that but I didnt see anything that linked the payment method to a specific account (at least from the returned response)

#

thanks for clarifying!

#

so if the payment method is created like stripe.createPaymentMethod("card");
then somewhere previously stripe is bound to the specific connected account?

cloud kiln
#

Yes you could create it like that for testing, but should never do it in real life. Normally you should collect Card information on client side, not server side, to avoid the burden of PCI Compliance

solid dock
#

yes this is happening client side