#heidi_api
1 messages Β· Page 1 of 1 (latest)
π Welcome to your new thread!
β²οΈ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
β±οΈ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
π This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1377720356328046822
π Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there π
I am taking a look at this, but might take a second for me to come back with some more information about this
hey no worries, I probably could've written a novel for each box but for the character limits
we generally built our new interface using this guide: https://docs.stripe.com/payments/save-and-reuse
i'm also searching through the discord history for other qas that might help
When you create a SetupIntent, can you add mandate info on the payment_method_options.card parameter?
https://docs.stripe.com/api/setup_intents/create#create_setup_intent-payment_method_options-card-mandate_options
other relevant details - early in our rewrite we did get failures from Indian cards where the messaging was "Your card does not support this type purchase" - I believe at the time we had rewritten part of the flow to use payment intents, but hadn't figured out the setup intent part yet. Not sure if that is relevant. But that's what we're afraid of happening right now. And then also related, it's not a subscription workflow. and it's hard to tease out from the docs when it references async payments if it's just for subscriptions or also affects us
oh, I haven't written it like that yet. I have
confirmParams: {
return_url: window.location.href,
mandate_data: {
customer_acceptance: {
type: "online",
online: {
ip_address: window.constants.ip_address || '127.0.0.1',
user_agent: window.constants.user_agent || 'Chrome/90.0.4430.93',
}
}
}
},
let me try adding that
that worked, thank you βΊοΈ . I get the mandate back once I confirm the setup intent, and also I had the auth step trigger. I think there's one thing I'm confused about still. In that Indian mandate documentation it references a 26 hour holding period before a charge will go through. In testing just now I was able to charge the card and show the charge as succeeded. Is the testing environment accurate in that sense?
Basically yes. This is the expected behavior in test environment. Did you pass inoff_session=true when you confirm the Payment Intent? For on-session, the payment goes through immediately, while off-session payments, will enter the processing state and transition after 15 minutes.
https://docs.stripe.com/india-recurring-payments?integration=paymentIntents-setupIntents&testing-method=card-numbers#testing
Yep, using off_session: true
oh! I didn't know how to interpret that 15 min. Basically, that's simulating the 26 hours then?
Yes, that's how it should work
neat, thank you, I appreciate you getting me over this hump. Was very easy in retrospect but I have so many docs and tabs open π