#Prasanga
1 messages · Page 1 of 1 (latest)
Isn't that something we should collect for SCA?
If you are using SetupIntent + PaymentElement, there's nothing specific to do on your end.
Are you creating e-mandate for India?
not at the moment. Is that something we should do manually?
I am not a stripe dev, just a dev who had to do e-mandate for India yesterday. I had to do it , since i want to charge users off-session.
For that in India we need mandate, outside India as far i tested, it works fine
ah right. We're also charging customers off-session and we might have customers in india
@spice timber the data for e-mandates had to be collected manually?
@mellow gull Our existing implementation uses the Card element and SetupIntent. Is SCA still taken care of by stripe in that case?
We have to add mandate values in the setupIntent. Rest will be taken care of stripe. By the end of card details capture, mandate will be generated for the setupIntent
The doc is very confusing, since its inconsistent. Only thing you have to do is add these in the setupIntent payload.
payment_method_options: {
card: {
mandate_options: {
reference: '{{REFERENCE}}',
description: '{{DESCRIPTION}}',
amount: '{{AMOUNT}}',
currency: 'inr',
amount_type: '{{AMOUNT_TYPE}}',
start_date: '{{START_DATE}}',
end_date: '{{END_DATE}}',
interval: '{{INTERVAL}}',
interval_count: '{{INTERVAL_COUNT}}',
supported_types: ['india']
}
}
oh one more thing, and then pass the customer mandate_id and payment_method_id in create invoice api
if you are charging via invoice
Thanks! this'll be useful
@mellow gull Our existing implementation uses the Card element and SetupIntent. Is SCA still taken care of by stripe in that case?