#mariacastro-connect
pastel sand
hi! that might happen really, since it's two separate merchants from the bank's perspective. Can you share an example failure request ID so I can understand exactly how you integrate?
primal hollow
of course, req_Vx4l2boMmdlTnu
pastel sand
I'm not seeing exactly where you handled 3D Secure on the platform?
I might be missing something but it looks like you
- created a token on the platform + attach to customer
- cloned it to the connected account
- attached the cloned token to a customer there
that last step can decline for any reason(including requiring 3D Secure), since a $0 charge is run against the card when attaching it(https://support.stripe.com/questions/unexpected-1-charge-on-customers-bank-statement) and banks sometimes decline those with 3D Secure required unfortunately.
The fix is to use our modern integrations of PaymentMethod+PaymentIntent+SetupIntent and https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods instead of this legacy token approach, overall.
the other less ideal option might be to pass the undocumented validate:false parameter when attaching the card to the customer, which skips the $0 charge and you would need to handle 3D Secure later when you actually charge the card