#sudhanshu4365
1 messages · Page 1 of 1 (latest)
hi
Do you mean how to collect a mandate and use later? https://docs.stripe.com/payments/payment-methods/bacs-debit-mandate-collection
hi
Yep, because it's behind a gate and your account doesn't have access. You'd need to sopeak to support for access
:question: Have a non-technical question, account issue, or need one-on-one support?
We wish we could help, but this community is focused on developers and technical discussions. Our support team will be able to assist you better than we can: https://support.stripe.com/contact
all i want to know how to send a mandate request while creating a payment method for bacs_debit using stripe API
is there any one?
I already told you, that feature is behind a gate. You need to speak to support for access on your account
Otherwise, you just use Checkout: https://docs.stripe.com/payments/bacs-debit/save-bank-details
Oops, sorry. Fixed: https://docs.stripe.com/payments/bacs-debit/save-bank-details
how to collect mandate for bacs_debit ?and use it to automatically charge customer for subscription cycle?
and is there any way we can charge customer who are having 3d secured cards?
I've already explained how: you use Checkout, or you speak to support and get access to BACS Debit on Setup Intents
I don't understand the question
if a user used 3d secured card for subscriptions , on next subscription cycle will stripe automatically debit the amount from that 3d secured card?
Yep, should do
its not it is asking for user action
Do you have an example?
in_1Ojc67I6jKdORQkOXT09eRG8
Charge customer for invoice
The invoice was finalised, but the customer needs to complete
3D Secure
authentication for the payment to succeed. This additional step is required by their bank to prevent fraud.
3D Secure emails are disabled in your settings, so you'll need to notify the customer manually
this is the invoice when i am charging it it throws the above errror
Taking a look now
this is in test mode btw
OK so the subscription in this case has a default PM using the 3220 test card, which always requires 3DS for every payment:
3D Secure authentication must be completed for the payment to be successful. By default, your Radar rules request 3D Secure authentication for this card.
So this is expected in this case
okay
You should instead test with 4000002500003155
That will require 3DS on the initial subscription invoice/payment, but subsequent recurring payments won't need auth:
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.
but how to handle always requires 3ds ?
Well you'd bring your customer back on-session and re-confirm the payment, which will handle the 3DS challenge flow for your customer
Your integration should be able to handle these scenarios and bank can and do request 3DS for off-session recurring payments even though why try to optimise to prevent that