> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.

# Bank Transfers via Flutterwave

> Set up bank transfer payments through Flutterwave in Payrails for customers in Nigeria and South Africa, with the request fields it needs.

<picture noZoom>
  ![Bank Transfers logo](https://assets.payrails.io/img/logos/banktransfer/logo.svg)
</picture>

<picture noZoom>
  ![Flutterwave logo](https://assets.payrails.io/img/logos/flutterwave/logo-full-bleed.svg)
</picture>

Accept [bank transfer](https://docs.payrails.com/docs/integrations/payment-methods/bank-transfers) payments from customers in Nigeria and South Africa with Flutterwave as the payment service provider (PSP). The customer selects bank transfer, completes the transfer on the Flutterwave payment page and returns to your site.

## Supported workflows

<table>
  <thead>
    <tr><th>Workflow</th><th>Supported</th></tr>
  </thead>

  <tbody>
    <tr><td>Payrails SDK</td><td>✔</td></tr>
    <tr><td>Payrails API</td><td>✔</td></tr>
    <tr><td>[Delayed / Manual Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✖</td></tr>
    <tr><td>[Instant Capture](https://docs.payrails.com/docs/orchestration/payment-acceptance/capture-and-cancel-modes.md#capture-mode)</td><td>✔</td></tr>
    <tr><td>[Cancel / Void](https://docs.payrails.com/docs/orchestration/payment-acceptance/cancel-a-payment.md)</td><td>✖</td></tr>
    <tr><td>[Refund / Reverse](https://docs.payrails.com/docs/orchestration/payment-acceptance/refund-a-payment.md)</td><td>✔</td></tr>
    <tr><td>[Save Instruments](https://docs.payrails.com/docs/resources/manage-instruments.md)</td><td>✖</td></tr>
    <tr><td>[Merchant Initiated Transaction (MIT)](https://docs.payrails.com/docs/resources/payments/authorization-flags.md)</td><td>✖</td></tr>
  </tbody>
</table>

## Before you begin

Complete these steps before you send your first bank transfer payment through Flutterwave:

1. Set up a Flutterwave integration in your workspace. Follow the [Flutterwave integration setup guide](https://docs.payrails.com/docs/integrations/payment-providers/flutterwave.md) if you don't have one yet.
2. In the Flutterwave dashboard, go to **Settings → Business Preferences → Payment Methods** and enable bank transfer.
3. In the Payrails Portal, go to **Settings → Integrations**, open your Flutterwave integration, select **Bank Transfer** under **Payment methods**, and save.
4. Add bank transfer as a [payment option](https://docs.payrails.com/docs/integrations/payment-methods/set-up-payment-methods.md) in your workflow.

## Request fields for Flutterwave

Send these fields in the authorize request, in addition to the standard [authorize fields](https://docs.payrails.com/reference/authorizeaction.md). **Required** fields must be present for the payment to succeed. Payrails sends **Optional** fields to the PSP when you include them.

| Field | Status | Description |
| - | - | - |
| `amount.currency` | Required | `NGN` for a Nigerian bank transfer or `ZAR` for a South African one. Payrails rejects other currencies. |
| `meta.customer.email` | Required | Sent to Flutterwave as the customer email. |
| `meta.customer.name` | Optional | Sent to Flutterwave as the customer name. |
| `meta.customer.phone` | Optional | Sent to Flutterwave as the customer phone number. Payrails joins the country code and the number. |

## Authorize a bank transfer payment

Call [authorize a payment](https://docs.payrails.com/reference/authorizeaction.md) with `bankTransfer` as the `paymentMethodCode`. The response includes the redirect to the Flutterwave payment page.

```json Authorize request theme={null}
{
  "amount": {
    "value": "5000.00",
    "currency": "NGN"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "bankTransfer",
      "amount": {
        "value": "5000.00",
        "currency": "NGN"
      }
    }
  ],
  "meta": {
    "customer": {
      "email": "chiamaka.okafor@example.com",
      "name": "Chiamaka Okafor",
      "phone": {
        "countryCode": "+234",
        "number": "8012345678"
      }
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}
```

After the customer completes the transfer, Flutterwave returns them to your `success` or `error` URL. Confirm the result through [webhook notifications](https://docs.payrails.com/docs/orchestration/payment-acceptance/receive-notifications.md) or the execution status before you fulfill the order.

## How Flutterwave handles bank transfers

* The payment currency selects the market. With `NGN`, Flutterwave offers its Nigerian bank transfer. With `ZAR`, it offers its South African bank payment.
* When the customer returns, Payrails fetches the transaction from Flutterwave to confirm the result.
* To return funds after a successful payment, refund it.


## Related topics

- [Bank Transfers](https://docs.payrails.com/docs/integrations/payment-methods/bank-transfers.md)
- [Bank Transfers via dLocal](https://docs.payrails.com/docs/integrations/payment-methods/bank-transfers/dlocal.md)
- [Flutterwave](https://docs.payrails.com/docs/integrations/payment-providers/flutterwave.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.