#ton-emendis-bv_api

1 messages · Page 1 of 1 (latest)

torn bearBOT
#

👋 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/1325856519090212966

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

undone heron
#

Good afternoon,
So we're building an ERP for one of my customers. They've asked me to investigate on an implementation of SEPA direct debit, which led me to you guys after checking multiple PSPs.

  • SEPA Direct debit is the only payment method I want to use.
  • It is not used for subscriptions, but to pay invoices that differ each week

I have read the documentation and came to the following solution.

Setup
We need to set up our account on stripe to get our API keys. Also to connect our bank etc.

In our ERP we'll ask the customers to fill in their IBAN and (company) name. This will trigger various actions in the following order

  • We'll create a customer in Stripe by means of the POST /v1/customers endpoint
  • Then we'll create the SEPA Direct Debit payment method for the stripe customer by means of the POST /v1/payment_methods endpoint
  • Then we'll create a SetupIntent by means of the POST /v1/setup_intents endpoint

After the first 3 steps the customer needs to approve this setup intent and make it active in their banking environment. This will then continue as follows

  • Depending on the webhook we'll create a job on our site to check the mandate status by means of the /v1/mandates/{mandate_id} endpoint.
    • Does the webhook fire multiple times? It might happen that we miss the webhook due to deployment or any type of reason.
    • If the webhook fires multiple times then we don't have to implement the job to retrieve the status.
#

After these steps we should be ready to go and send payments to our customers

  • We'll create payments for each customer by means of the /v1/payment_intents endpoint
  • Then again depending on the webhooks we should check the status of the payment intent by means of the /v1/payment_intents/{payment_intent_id} endpoint for which we'll create a job.
    • Does the webhook fire multiple times? It might happen that we miss the webhook due to deployment or any type of reason.
    • If the webhook fires multiple times then we don't have to implement the job to retrieve the status

Could someone take a look at this proposal and let me know if

  • There are other scenarios regarding SEPA Direct debit that I missed or need to keep in mind?
  • There are other endpoint that are involved in this process that I might need.

Also let me know if you need any clarifications on something ⁠:)

Thanks in advance!

#

I hope my description is clear!

dusk condorBOT
cursive basin
#

Hi 👋 it sounds like you have a good grasp of the flow, and if you're looking for sample code to get started you can review our guide for setting up SEPA Payment Methods:
https://docs.stripe.com/payments/sepa-debit/set-up-payment?platform=web&payment-ui=direct-api

The one thing I'd likely suggest here, is that you don't create the Payment Method directly and instead let the Setup Intent create that for you.

We do attempt to deliver Events to your webhook endpoints multiple times if we don't receive acknowledgement from your servers that you received the Events successfully:
https://docs.stripe.com/webhooks#retries

Save SEPA Direct Debit details for future payments

Learn how to save payment method details for future SEPA Direct Debit payments.

Receive Stripe events in your webhook endpoint

Listen to events in your Stripe account on your webhook endpoint so your integration can automatically trigger reactions.