rikz_api

[noble saffron]

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

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

[honest sun]

Hi 👋 no, our flows will ensure the general formatting of the number is correct, but can't validate the number points to an existing acocunt.

[quaint rover]

Sure thanks for the info

[honest sun]

Any time!

[quaint rover]

In one of our old implementations we used token api to create token using iban and create sepa direct debit source to validate IBAN. If one of this method throws error then we identified as IBAN validation failure.

This is somehow very old implementation and we source API is going to deprecate soon hence I need to get rid of it

Thats why I am looking for a alternative solution here

[sage relic]

In our current flows the IBAN is validated as part of the intent confirmation process. Have you looked much in to what your process will look like with setup intents or payment intents?

To be clear just asking so I'm not explaining stuff you already know

[quaint rover]

Yes we already use payment intents But I havent check the IBAn validation through this process
May be I can test this out. If it is working then I can get rid of this old logic

[sage relic]

Yeah if you use an incorrect IBAN that last confirm call should give you an error in some way. If you test that in test mode and see some other behavior I can look further in to it