#lafafm-3ds
1 messages · Page 1 of 1 (latest)
What about production testing?
Or the only possibility is to somehow disable 3ds for card on signup, and activate it before payment?
you could I think add a 3D test card directly using https://stripe.com/docs/api/payment_methods/attach (just for testing only) instead of the usual flow you have(which should use SetupIntents. I'm not entirely sure what flow you're testing or parts of the API you're using.
If it's for subscriptions I would create a subscription with a trial period and a 3DS test card, an invoice is created after the end of the trial that acts as a recurring invoice and will fail
let customer = await stripe.customers.create({
email: "test@example.com",
});
let pm = await stripe.paymentMethods.attach("pm_card_authenticationRequired", {customer: customer.id});
let subscription = await stripe.subscriptions.create({
customer: customer.id,
trial_end:moment().add(5,"minutes").unix(),
default_payment_method : pm.id,
items: [
{
plan: "plan_DQYe83yUGgx1LE",
},
],
expand : ["latest_invoice"]
});
Ok, gonna try it
Thank you!
@south ice another question for 3ds, if possible. Just to not spam in channel
If we're having subscription w/ trial period - I'm creating a SetupIntent w/ pending_setup_intent property, for the future renewal payment
But if we want to make pre-auth check for $1 (that would be refunded immediately) - do we need to create a dedicated intent for it?
ah sorry missed this question
technically if you wanted to do that you'd use a separate PaymentIntent yes
but you should not do this at all, it's generally not recommended and banks/card companies dislike merchants doing that; it's not something we'd suggest you ever do.
I'm glad to, but not think it's possible due the business reasons
Is there any article / document for it? E.g. why it's not recommended, or so
no there is nothing specific I can point you to