Persistent Payment Identifier

Persistent payment identifiers are static payment identifiers generated from Paga that allow merchants to receive payment via Bank Transfers. This payment identifier does not expire and allows merchants to receive payment in perpetuity from the customer unless deleted or deactivated by the merchant

📘

Persistent vs Dynamic Payment Identifier

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

How to Get Paid Using a Persistent Payment Identifier

3 Simple Steps

1. Generate a persistent payment identifier 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 a payment identifier

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 Payment Identifier

Show the account details in your app or via email:

• Payment Identifier: 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 payment identifier 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 flexibility

• Update a Persistent Payment Identifier - Update the the details of a persistent payment identifier you've previously created
• Delete a Persistent Payment Identifier - Delete a persistent payment identifier you've previously created
• Get a Persistent Payment Identifier - Get details and properties of an existing persistent payment identifier.