Skip to main content
Bank Transfers let customers pay directly from their bank account. They don’t need a card or other payment instrument. The customer confirms the transfer on a page hosted by the payment service provider (PSP) or in their banking app. Payrails processes bank transfers through two PSPs. The flow is the same with each one, but the supported countries and the required request fields differ. Pick a PSP below for its setup steps and request examples.

​
How a bank transfer payment works

Bank Transfers use a redirect flow:
  1. The customer selects bank transfer at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to the PSP’s payment page.
  3. The customer completes the transfer from their bank account.
  4. The PSP sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every transfer on its own. Payrails captures bank transfer payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

The supported countries and currencies depend on the PSP:
  • Flutterwave supports NGN (Nigerian naira) in Nigeria and ZAR (South African rand) in South Africa.
  • dLocal receives the customer’s country and the payment currency as you send them. Bank transfers through dLocal work in the countries enabled on your dLocal account. Nigeria and South Africa are among them.

​
Integrate bank transfers

Choose the PSP that processes bank transfers for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

dLocal

Bank Transfers via dLocal

Flutterwave

Bank Transfers via Flutterwave

​
Compare PSPs

Neither PSP supports saving a bank transfer instrument or merchant-initiated transactions (MIT). Each bank transfer is a new customer-initiated payment.

​
Ways to integrate bank transfers

  • Payrails SDK: the Web SDK shows bank transfer when your workflow returns it as a payment option, and redirects the customer to the PSP’s payment page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with bankTransfer as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026