Manual bank transfer and the unique code
Action needed if you show your own bank transfer instructions
Since 2026-11-09 every manual bank transfer has a unique code. If your app or site builds its own transfer instructions from amount, switch to pay_total. A payer who sends amount sends up to Rp999 too little, and that payment takes longer to confirm.
What the unique code is
When a payer picks manual bank transfer, RekberPay adds a small unique code of Rp1 to Rp999 to the total. No two open manual bank payments share the same total, so when the money lands in RekberPay's account, the exact figure tells RekberPay which payment it belongs to.
It applies to every product that can be paid by manual bank transfer:
| Product | Where the payer sees it |
|---|---|
| Rekber (escrows) | Start a payment and Get the payment status |
| Jasa Pembayaran | Pay for an order and Get the order payment status |
| Rekber B2B (enterprise deals) | Pay a milestone (live), Pay the whole deal and both payment status reads |
| Platform | The RekberPay hosted checkout shows it to the buyer. Your invoice read counts it in unique_code and paid_total |
A few things stay the same:
amountkeeps its meaning. It is the escrow, order or milestone amount plus the method fee, as before.- The code is part of the transfer fee. The payer pays it, it is never refunded, and it never reaches the seller or your settlement. Refunds and releases use the same amounts as before.
- Other methods do not change. A virtual account, e-wallet or store payment code has its own reference. Some automatic QRIS payments already add a code the same way and answer with the same fields.
- Sandbox payments do not get a code. Sandbox never creates a real payment.
The fields
Every answer that shows a manual bank transfer has two more fields:
| Field | Type | Meaning |
|---|---|---|
pay_total | integer | The exact figure to transfer: amount plus unique_code. Show this one |
unique_code | integer | The code, from 1 to 999 |
They appear on the pay answer and on every payment status read of that payment. Asking again for an open payment (resumed: true) gives the same code and the same pay_total. A new payment after the old one expired gets a new code.
Escrow example, a Rp250.000 escrow with the Rp1.000 manual bank fee:
{
"success": true,
"data": {
"payment_link_id": "77777771-7777-4777-8777-777777777777",
"gateway_order_id": "RBP-33333330-1791901398340-c41d9e02",
"method": "bank_transfer",
"provider": "bank_transfer_manual",
"va_number": "1234567890",
"va_bank": "bank_mandiri",
"expires_at": "2026-11-10T03:12:44.000Z",
"amount": 251000,
"escrow_amount": 250000,
"surcharge": 1000,
"payment_fee": 1000,
"fee_bearer": "buyer",
"seller_fee": 0,
"pay_total": 251347,
"unique_code": 347
}
}The payer transfers Rp251.347 to account 1234567890, not Rp251.000.
Enterprise example, a milestone with a funding amount of Rp30.600.000:
{
"success": true,
"data": {
"method": "bank_transfer",
"provider": "bank_transfer_manual",
"va_number": "1234567890",
"va_bank": "bank_mandiri",
"amount": 30601000,
"milestone_amount": 30600000,
"surcharge": 1000,
"pay_total": 30601347,
"unique_code": 347
}
}The payment status reads give the same pair. On the escrow and Jasa Pembayaran status reads amount is a decimal string ("251000.00"), while pay_total and unique_code are whole rupiah integers.
What to show the payer
- The bank, the account number and the account holder.
pay_totalas the figure to send, with a copy button.- A line such as "Transfer exactly this amount, down to the last 3 digits." In Indonesian, RekberPay's own screens say "Transfer persis sampai 3 digit terakhir".
- If you show a fee breakdown, fold the code into the transfer fee: "Transfer fee Rp1.347 (Rp1.000 + unique code Rp347)".
- The deadline from
expires_at. A manual bank transfer stays open for 24 hours.
Before the payment starts the code is not known yet. If you show a price first, say "+ unique code" next to the total (up to Rp999 more).
If the payer sends a different figure
| The payer sends | What happens |
|---|---|
Exactly pay_total | RekberPay recognises the transfer by its amount and confirms it after the payer reports it with I have paid (claim-payment) |
amount, without the code | The figure matches no open payment, so confirmation takes longer. Ask payers to send pay_total |
Less than amount | It does not pay the escrow, order or milestone. The payer contacts RekberPay support with the payment reference to settle it |
Payers on old app builds, and on integrations that still show amount, end up in the second row.
When no code is free
If RekberPay cannot find a free code for that total at that moment, the pay call answers 503 UNIQUE_CODE_BUSY. Nothing was created and nothing was charged. Try again in a moment, or pick another method.
Checklist for integrators
- [ ] Show
pay_total, notamount, wheneverpay_totalis present. - [ ] Copy buttons for the manual bank transfer copy
pay_total. - [ ] Your own pricing pages say "+ unique code" for manual bank transfer until the payment starts.
- [ ] Treat
pay_totalandunique_codeas optional. They are left out for methods that do not use them. - [ ] Do not add
unique_codeto your ledger, payout or refund figures. Those useamountand the escrow or milestone amounts, as before. - [ ] Handle
503 UNIQUE_CODE_BUSYwith a retry or another method. - [ ] Payers report the transfer with I have paid (
claim-payment) as before.