Accepting Bank Transfer Payments Through Paystack

When a customer selects bank transfer at Paystack checkout, the flow is:

1. Paystack generates a temporary bank account number (usually at a partner bank like Wema or Providus)
2. The checkout page displays the account number, bank name, and the exact amount to transfer
3. The customer opens their banking app (GTBank, First Bank, Kuda, OPay, etc.) and initiates a transfer to that account for the exact amount
4. The customer's bank processes the transfer
5. Paystack's partner bank receives the funds and notifies Paystack
6. Paystack confirms the payment and fires a charge.success webhook
7. The temporary account expires and can no longer receive transfers

The customer never shares card details, which is why many Nigerians prefer this channel. They are transferring from their own banking app, using the same interface they use for everyday transfers.

var response = await fetch('https://api.paystack.co/transaction/initialize', {
  method: 'POST',
  headers: {
    Authorization: 'Bearer ' + process.env.PAYSTACK_SECRET_KEY,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    email: 'customer@example.com',
    amount: 500000, // 5,000 NGN
    currency: 'NGN',
    channels: ['bank_transfer'],
    callback_url: 'https://yoursite.com/payment/callback',
  }),
});

var data = await response.json();
// Redirect to data.data.authorization_url
// Paystack checkout shows the temporary account details

If you include bank_transfer alongside other channels (like ['card', 'bank_transfer']), the customer can choose between card and bank transfer on the checkout page.

Paystack's checkout handles displaying the account number, bank name, and amount. It also shows a countdown timer for how long the temporary account is valid and a status indicator that updates when the transfer is confirmed.

Bank transfer confirmation is not instant. After the customer initiates the transfer from their banking app, there is a delay while the inter-bank settlement system processes it. This typically takes anywhere from 30 seconds to a few minutes, but can occasionally take longer during peak banking hours or system maintenance.

The Paystack checkout page shows a waiting indicator after the customer indicates they have transferred. When Paystack confirms the payment, the page updates and the customer is redirected to your callback URL.

From your server's perspective, the charge.success webhook is the reliable confirmation. Do not rely on the customer telling you they transferred. Wait for the webhook.

// Webhook handler for bank transfer confirmation
app.post('/webhooks/paystack', function(req, res) {
  res.sendStatus(200);

  var event = req.body;

  if (event.event === 'charge.success') {
    var channel = event.data.channel;
    if (channel === 'bank_transfer') {
      console.log('Bank transfer confirmed: ' + event.data.reference);
    }
    // Fulfill regardless of channel
    fulfillOrder(event.data.reference);
  }
});

What happens if the customer transfers the wrong amount?

• Less than required: The payment is not confirmed. The transaction remains pending. The customer needs to make up the difference or the transaction eventually expires.
• Exact amount: The payment is confirmed normally.
• More than required: Paystack's handling of overpayments may vary. The excess may be refunded according to Paystack's policy.

The checkout page clearly displays the exact amount and instructions to transfer that exact amount. Most banking apps allow the customer to enter the exact figure. The most common issue is rounding: if the amount includes kobo (like 5,000.50 NGN), the customer might transfer 5,000 or 5,001.

To avoid this, consider rounding your amounts to whole Naira values when bank transfer is a primary channel. A 5,000 NGN charge (500000 kobo) is less error-prone than a 5,000.50 NGN charge (500050 kobo).

Bank transfer through Paystack checkout uses temporary accounts: one-time-use account numbers generated per transaction. For ongoing collections, Paystack offers dedicated virtual accounts (DVAs): permanent account numbers assigned to specific customers.

Feature	Temporary Account	Dedicated Virtual Account
Lifespan	One transaction	Permanent
Per customer	No (per transaction)	Yes
Amount flexibility	Fixed per transaction	Any amount
Setup	Automatic via checkout	API call to create
Use case	One-time purchases	Wallets, recurring deposits

For wallet top-up flows or apps where customers deposit money regularly, dedicated virtual accounts are the better choice. See dedicated virtual accounts implementation for the full guide.

Bank transfer involves the customer copying an account number and switching to a different app. Make this as smooth as possible:

• Copy button: Paystack checkout includes a copy button next to the account number. If you build a custom UI, add one too.
• Clear instructions: "Transfer exactly N5,000 to the account below using any banking app."
• Timer: Show how long the account is valid. Creates gentle urgency and sets expectations.
• Confirmation message: After the customer says they have transferred, show "Confirming your transfer..." with a loading indicator.
• Fallback: If confirmation takes too long (over 5 minutes), offer the option to check status later or contact support.

Bank transfer is the fastest-evolving Paystack payment channel. New partner banks and features are added regularly.

Sign up for the McTaba newsletter to stay informed about Paystack bank transfer updates.