Persistent Wallet Account

Generate a Paga Persistent Account for your customers

Persistent accounts are static account numbers (NUBAN) generated from Paga that allow merchants to receive payment via Bank Transfers. This account number does not expire and allows merchants to receive payment in perpetuity from the customer unless deleted or deactivated by the merchant

📘

Persistent vs Dynamic Accounts

  • Persistent Account: For repeat use, linked to a customer permanently. Must be deleted to deactivate.
  • Dynamic Virtual Account: For one-time use only. Expires after a transaction or set time.

How to Get Paid Using a Persistent Account

3 Simple Steps

  1. Generate a persistent account number for your customer.
  2. Display it with the bank name Paga.
  3. After successful payment, we will send you a callback with details of the payment.

Step 1: Get all the needed information

Below is the list of parameters required to generate account number

ArgumentData TypeDescriptionRequired
referenceNumberStringA unique reference number representing this request. The same reference number will be returned in the response and can be used to query the payment request status
hashIndex-1
True
phoneNumberStringThe phone number of the customer. This must be provided if the email is not provided.True
accountNameStringThe acountname of the customer.True
firstNameStringThe first name of the customerTrue
lastNameStringThe last name of the customerTrue
accountReferenceStringThis is a unique reference number provided by the Organization which identifies the persistent account Number. It should have a minimum length of 12 characters and a maximum length of 30 characters
hashIndex-2
True
financialIdentificationNumberStringBVN of the customer
hashIndex-3
False
emailStringThe email of your customer. This must be provided if the phoneNumber is not provided.False
creditBankIdStringIf included, this is the UUID of the bank that you want deposits to be transferred directly to for every payment. You can get destination bank UUID from getBank Endpoint
hashIndex-4
False
creditBankAccountNumberStringThis must be provided if creditBankId is included in the request payload. It is the bank account number of the bank that you want deposits to be transferred to. This must be a valid account number for the bank specified by creditBankId
hashIndex-5
False
callbackUrlStringA custom callback URL for the payment webhook notifications for this specific account to be sent to. If provided, requests are sent to this URL exactly as provided. This allows you to set custom query parameters to the URL which you will be provided during webhook notifications for this specific account.
hashIndex-6
False

How to Generate the Hash (HMAC)

To secure the request, compute an HMAC SHA-512 hash over the concatenated string of selected parameters in this order:

referenceNumber + phoneNumber + accountName + accountReference + financialIdentificationNumber + creditBankId + creditBankAccountNumber + callbackUrl
  • Omit any empty/null fields but do not change the order**.
  • Then generate the hash using your HMAC secret key.

Example in JavaScript:

const crypto = require("crypto");

function generateHash(payload, secret) {
  const rawData = payload.referenceNumber + payload.phoneNumber +
    payload.accountName + payload.accountReference +
    (payload.financialIdentificationNumber || "") +
    (payload.creditBankId || "") +
    (payload.creditBankAccountNumber || "") +
    (payload.callbackUrl || "");

  return crypto.createHmac("sha512", secret).update(rawData).digest("hex");
}

Sample Success Response

{
    "referenceNumber": "0053459875439143453000",
    "statusCode": "0",
    "statusMessage": "success",
    "accountReference": "123467891334",
    "accountNumber": "1061871576"
}

Step 3: Share the Account Number

Show the account details in your app or via email:

  • Account Number: 1061871576
  • Bank: Paga

Step 4: Handle Payment Callback

After every payment, we’ll send a callback notification to the callback URL you provided in your request
More about callback parameters

{
  "statusCode": "0",
  "statusMessage": "success",
  "transactionReference": "SC-C_20220915113942190_4293418_ND8K0_6dg5g",
  "fundingPaymentReference": null,
  "accountNumber": "2830163290",
  "accountName": "Bellview Walker",
  "financialIdentificationNumber": null,
  "amount": "200.00",
  "clearingFeeAmount": "1.50",
  "payerDetails": {
    "payerAccountNumber": "0745089449",
    "paymentReferenceNumber": null,
    "paymentMethod": "MONEY_TRANSFER",
    "payerName": "Bello Ramon"
  },
  "hash": "0d57b7d8d1a21a94eec7edd951aaeaeb5e8597672d05fb732f146e93e79ac7caa520ff86ed069f28c3322e469af4898a7d72f3e0c83d919d61c535140b4eef8e"
}

📘

Is callback retry available? Yes

The persistent account callback retries as follows:

  • At the initial time when the payment is made, it tries three times in succession to notify your endpoint with the following intervals: immediately, 1 second later, 5 seconds later, 15 seconds later

  • If none is successful, it gets added to a queue for intermittent retries every 5 minutes for the next 30 minutes or until a callback is successful

With the above, there shouldn't be any case where you do not receive the notification callback unless your callback endpoint is offline for more than 30 minutes

We have few more endpoint available to give you more flexibilty


What’s Next