#adam_api
cedar cipherBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1253307571419484231
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
distant bay
There's an overall guide here: https://docs.stripe.com/payments/payment-methods/transitioning
The general flow you outlines saving payment methods for future usage, is that right? If so, then you'd be transitioning to a Setup Intent to save the details
We make reference to properties, returned at step (2), like 'error', 'sepa_debit.last4' and 'sepa_debit.mandate_reference'. Will those properties still exist when we switch to the Payment Intents API ?
Likely map to different fields on the new corresponding objects in the API
We already accept card payments via the Payment Intents API so should we be, basically, looking at copying that code but just changing the data we send ?
If you're using intents today for card payments, then the flow would overall be the same. The intent flows are generally PM agnostic assumign you're using our payment UIs
forest knoll
Hi @distant bay , thanks for the reply.
Yes, we basically create the equivalent of a Direct Debit mandate (without taking any money ) then make monthly charges to it via the POST charges endpoint (and passing the 'src....' ID).
We also allow customers to make an immediate, one off payment, via a debit/credit card
Is a Setup Intent different to a Payments Intent ?
distant bay
Yes, a Setup Intent would be used in the scenario you describe: collecting and save details for future use without an initial payment: https://docs.stripe.com/payments/setup-intents
If you do have an initial payment, you can save the details for re-use during that initial payment. If they're not saved then they're not reusable by default: https://docs.stripe.com/payments/save-during-payment
forest knoll
Thanks again.
Currently there is no 'link' between the initial payment and future payment [ they can be from different sources ]; it is usually a case of "pay £10 now on a card and then x payments of £25 via sepa debit".
I will take a look through all the links you've posted and see if it makes sense 🙂
distant bay
Sure, happy to answer any follow-ups
forest knoll
Actually, looking at our code again ....
We only seem to call the payments_intent API once - when we actually take the card payment - and, even for card payments, we call the setup_intents before hand
distant bay
Sure, then that should also work with IBAN/SEPA payments: https://docs.stripe.com/payments/sepa-debit/set-up-payment
cedar cipherBOT