Menu

Behind every Pay by Bank click: six API calls and a bank you didn't choose
📰

Behind every Pay by Bank click: six API calls and a bank you didn't choose

DEV Community: api·arun rajkumar·about 8 hours ago
#HqUovjDW
#devtoapi#devto#dev#bank#payment
Reading 0:00
15s threshold

When you add Pay by Bank to a checkout, you call one endpoint. Your provider gives you a link, the customer taps it, picks their bank, approves, and comes back. Done.

At the bank end, that one tap is about six API calls. And the bank isn't one you picked. Your customer picked it. If they bank with someone whose API has a rough night, that's your checkout having a rough night.

I run engineering at a payment initiation provider, so those six calls are what my team works on every day. Here's what they are, and what the latest public numbers say about the banks behind them.

The six calls

This is the UK Open Banking flow for a single domestic payment. Names are from v3.1 of the spec, which is what most banks still expose.

Before any of it, you register as a client with the bank (dynamic client registration, using your Open Banking certificates). Once per bank. Then again for the next bank.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.