How it works
01
Customer selects bank payment
At checkout, the customer chooses to pay from their bank instead of by card.
02
Customer authenticates with their bank
They are taken to their own bank's authentication, where they approve the payment directly.
03
Payment is initiated
The transfer is initiated from the customer's account to yours, using the local instant rail where one is available.
04
Confirmation and reconciliation
Confirmation appears in your merchant dashboard alongside your card transactions, with the same reporting and export.
Availability, confirmation timing and settlement speed depend on the market, the customer's bank and the rails supported in that country.
Why merchants add bank payments
No card data in the flow
The customer authenticates with their own bank. There are no card credentials to capture, store or protect.
Customer-authorised at source
Because the customer approves the payment inside their own banking app, the payment carries a strong authorisation signal.
Local instant rails
Where an instant rail exists in the market, funds move on it rather than on a slower domestic route.
A complement, not a replacement
Bank payments sit next to card acceptance in the same checkout. Most merchants benefit from offering both.
How this differs from your account transfers
eazypay24 clients already send and receive SWIFT, SEPA and local transfers from their accounts. That is your business paying and being paid on your own instruction. Open and instant bank payments are a customer-facing acceptance method— your customer initiates the payment at your checkout, and it is reported as a merchant transaction. The two use different infrastructure and are onboarded separately.
FAQ's
Add bank payments to your checkout.
Tell us which markets you sell into and we will confirm what we can enable.