#adam_api
merry chasmBOT
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.
- adam_sepadebit-migration, 5 days ago, 18 messages
- adam_api, 6 days ago, 13 messages
mild orchidBOT
👋 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/1255535292702789655
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
gray mural
I don't think that we have calls that only do that, that validation would be part of saving or tying to charge the SEPA payment method. For your validation method, is that to say that our test IBANs aren't passing the SEPA equivalent of the Luhn algorithm?
atomic moat
I believe they are passing the Luhn algorithm (we do all manner of tests around account number length, country codes, check digit comparisons, etc) but we then call an external 3rd party API to also check the number. If that all comes back OK then we try to save it @ Stripe.
If we can rely on Stripe doing validation at the **save ** point, and informing us of an issue, then we can maybe ditch the 3rd party call ?
gray mural
How are you doing this saving? With a SetupIntent I assume? We should actually be reaching out to the bank at that point as far as I know
atomic moat
Currently, this is being done by creating a source and attaching it the customer .... [ and, yes, we know the sources endpoint is shortly being deprecated 😀 and that we need to start using setup intents ]
gray mural
I will check with my colleagues if we do a validation at that point. I know we do a validation when attaching PaymentMethods at least for cards, but I am not sure if there are source<->PM or card<->SEPA differences here
atomic moat
I have just done a dummy test with a clearly wrong IBAN number and the sources POST call does indeed come back with a "The provided IBAN is not a valid one." error which is good enough for out purposes 🙂
gray mural
Awesome, was just about to get back with that info. We do do that check but don't reach out to the bank. Glad that works for you!