#irshad_sepadebit-fulfillment
jaunty groveBOT
đ 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/1216806879305662494
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
frigid lintelBOT
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.
- irshad-ali-jan_error, 4 days ago, 10 messages
- irshad-ali-jan_docs, 4 days ago, 27 messages
fringe needle
irshad_sepadebit-fulfillment
@oak mirage I would say it depends on your overall business model and what you're selling. It's up to you to decide whether to wait for payment success to give access to what you are selling or not.
For example if you are selling a physical product you likely want to wait for the payment to fully succeeds before you ship it. If you're giving access to some digital content then you might be okay giving immediate access and cutting off access a few days later if the payment failed
oak mirage
yes we are using digital product model. We are planning something similar to what you suggested to cutting off access few days later. But what are the minimum checks we can take a look at when we receive different events on our webhook in order to allow temporary access.
fringe needle
https://docs.stripe.com/payments/sepa-debit
Sepa Debit goes to processing for a few days while we work with the bank to see if the payment will succeed or fail. And based on that you'd get payment_intent.payment_failed or payment_intent.succeeded after a few days
oak mirage
can we be sure that the bank account details (IBAN) the customer provided was valid irrespective of if they had enough funds or not but at-least know that bank account is valid?
fringe needle
no that's impossible. You only know after a few days when the attempt to debit succeeds or fails
oak mirage
so it means user can add any bank details to fraud the system so where the stripe is helping out us with it?
fringe needle
We just recently added the ability to request micro-deposit verification for SEPA Debit bank accounts so you could use that feature
It's not yet fully public so you need to reach out to our support team for access: https://support.stripe.com/contact
oak mirage
aha that would be really helpful.
if its not public can we use it in our production?
and when it got added?
fringe needle
You have to ask for access, contact our support team: https://support.stripe.com/contact
oak mirage
ok i will contact. one more question regarding mandate object in sepa_depit response. Does this mean that mandate has been signed by customer?
fringe needle
no, it's a representation of you collecting their agreement, client-side, based on their IP address and such but it's not proof they did anything with their bank
oak mirage
but in order to sepa debit be fulfilled we need to send mandate to the bank right?
will stripe send it?
fringe needle
no there's no need to send a mandate to the bank, at least not that I know of. And you don't have to do anything specific with SEPA Debit.
oak mirage
okay thanks, what can we use mandate id for?
fringe needle
it's a record of you collecting permission to debit the customer and has information such as the date and their IP address which can be used for disputes for example with the bank. I don't know much more about this but our support team can help!