Bob the builder | Stripe Developers | Page 1

stone harborBOT Mar 28, 2023, 11:06 AM

#

fallen sierra Mar 28, 2023, 11:06 AM

#

Before cloning, the payment method was originally created in req_6H6geoaviuERfC

wary plume Mar 28, 2023, 11:09 AM

#

Hi
Checking...

#

It looks like this is a MOTO transaction right ?

fallen sierra Mar 28, 2023, 11:10 AM

#

Yes

#

There are other similar requests that succeeded

#

A follow up question - can we pass any additional data, so that such requests dont fail?

faint inlet Mar 28, 2023, 11:15 AM

#

it's because attaching a card to a customer can sometimes result in a $0 validation charge to check it with the bank(https://support.stripe.com/questions/unexpected-1-charge-on-customers-bank-statement) and that charge can be declined by the bank(as it was here).

#

can we pass any additional data, so that such requests dont fail?
there's an undocumented field validate on the customer attach endpoint , so "validate"=>"false" , which skips such validations. That also means skipping things like confirming the CVC is correct though, so if you use it incorrectly it can lead to more declines etc

I believe your account has an AE etc so probably best to discuss with them your overall integration as it's complex.

fallen sierra Mar 28, 2023, 11:17 AM

#

What's an AE?

faint inlet Mar 28, 2023, 11:18 AM

#

account executive, sales contact

fallen sierra Mar 28, 2023, 11:19 AM

#

Okay, thanks for the help. Will contact them to see if we can use validate for our use case.

faint inlet Mar 28, 2023, 11:20 AM

#

no worries, though they'll probbably just ask my team

#

so while I have you, is anything else unclear?

fallen sierra Mar 28, 2023, 11:20 AM

#

In that case - is there any regulatory reason why validate should not be used?

faint inlet Mar 28, 2023, 11:20 AM

#

regulatory? don't know

#

overall this cloning integration is not well supported unfortunately so it has bad interactions with the 3D Secure flows. I believe we suggest using validate=>false in these scenarios if you are convinced that the card is already valid based on how it was used on the platform; the main thing is that you can handle any declines/3DS step-ups on the actual charge attempts later.

#

using MOTO complicates this as well.
but overall what happens is you clone the card to the connected account and attach, we run a $0 validation by that connected merchants, the bank has not seen that merchant before, so they might request 3D Secure. You can use validate=false to skip that and then handle the actual payment later. This is why I'd prefer if you had some dedicated Stripe person to talk to, presumably you did when you built this integration in the first place

#Bob the builder