keithm-pm-cloning

[quick stratus]

Hey! Yep, calls to attach a PM like that can indeed trigger a 3DS/auth request from the bank. We generally don't recommend that endpoint

Instead you'd do it this way: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods

[potent oak]

Hey, ah ok - that makes sense. Just wondering/to double check does the way linked above have a chance of an 3DS/auth request?

could be completely wrong here but I thought the way we had done it before was the Stripe recommended way but this was most likely 2-3 years ago so could be out of date

Also, sorry for bombarding you with questions, is there a test card we can use that would allow us to replicate this error?

[quick stratus]

Potentially, I'm not sure. But we rarely recommend attaching directly like that now as it often triggers auth request with no way to facilitate the auth fulfilment

[quick stratus]

It shouldn't, no

[quick stratus]

Which error?

[potent oak]

ok great

[potent oak]

perfect

[potent oak]

The card authentication error sorry, in a perfect world we'd like to reproduce this error with a test card on our existing codebase, make the suggested change and run again to verify its all fixed

[quick stratus]

Got it. Plenty test card options here: https://stripe.com/docs/testing#regulatory-cards

[potent oak]

oh, sorry we've tried the above here and they don't trigger this error on our existing logic

we're looking for a card that'll reproduce this exact error (if one exists) just so we can add to test suit to confirm our logic is good going forward

[quick stratus]

Well it depends on which API/integration you're using as to whether an error will be thrown/expected

[potent oak]

Ok cool, we'll update our logic to this and hopefully it resolves the issue

thank you very much

[quick stratus]

Np!