#kasunakalanka

1 messages · Page 1 of 1 (latest)

light mistBOT
hard yoke
#

Can you share some example payment IDs please

echo aurora
#

Initial Payment intent

    amount: stripePayAmount,
    currency: 'gbp',
    customer: customerStripeId,
    payment_method: payment_method_id,
    capture_method: 'manual',
    confirm: true,
    setup_future_usage: 'off_session',
});

Initial payment intent id -: pi_3Nl77WKhTkOXLGpI0RfGv8Z7```

**Subsequent payment intent**

```const paymentIntent = await stripe.paymentIntents.create({
    amount: stripePayAmount,
    currency: 'gbp',
    customer: customerStripeId,
    payment_method: payment_method_id,
    capture_method: 'manual',
    confirm: true,
});


Subsequent payment intent id -: pi_3Nl7CSKhTkOXLGpI0NVWOUYl```
#

Please note I'm using the same payment method id of the card for both of the cases

hard yoke
#

If the customer present/online in the payment flow for the subsequent payment(s)?

#

Or are they offline/merchant initiated?

echo aurora
#

customer is offline.

hard yoke
echo aurora
#

ohh. Isn't it; setup_future_usage: 'off_session'?

hard yoke
#

Yes, for the initial payment. That will ensure that the card/payment method is saved/setup for subsequent re-use

#

But if your user is offline for the subsequent payments, you need to mark those payment as such with off_session: true. Then we can apply for SCA exemptions

echo aurora
#

Thank you very much. I'll update my subsequent payment intent

hard yoke
#

However that's likely not the only issue

#

The test card you're using (4000000000003220) always requires 3DS/authentication

#

You should use 4000002500003155 instead:

This card requires authentication for off-session payments unless you set it up for future payments. After you set it up, off-session payments no longer require authentication.

echo aurora
#

Ohh okay. In a live environment, most of the actual cards would always require authentication right?

hard yoke
#

Initially, probably. Not necessarily for folllow-up payments if you save them correct (via setpu_future_usage). Then we will apply for SCA exemptions for follow-up payments

#

However banks ultimately determine whether 3DS/auth is requested on a per payment basis so your integration needs to account for that too

echo aurora
#

Thanks again. This SCA exemptions; will it be completed from stripe's end?

broken flame
#

Hi! I'm taking over from my colleague. Please, give me a moment to catch up.

broken flame
#

... as long as you use setup_future_usage.

echo aurora
# broken flame Yes, you don't need to worry about it

Thank you very much. Just one question; If the bank determines that the card should always be authenticated (for subsequent payments too), I will have to ask consumer to do so right? regardless of he is offline or not

broken flame
#

Normally, you would ask them to provide another card. It's easier than building an ad-hoc authentication flow.