Skip to content

BBPS Guides

Handling Pending Bill Payments and Reconciliation in BBPS

Why some bill payments stay pending, why they must never be treated as failed automatically, and how a sound reconciliation workflow works.

Infycore Editorial 6 min read

Most bill payments complete in seconds. A small share do not return a final status immediately and remain pending. How your panel handles these cases decides whether customers get charged twice and whether your books balance.

Why payments go pending

A payment passes through several systems: your platform, the operating unit, BBPS and the biller. A timeout or delayed response anywhere along the way can leave the final result unknown for a while, even when the payment has actually succeeded.

The golden rule: pending is not failed

Never assume a pending payment has failed. If the system treats it as failed and the customer pays again, the same bill can end up paid twice. Refunding the duplicate then takes time and support effort.

A safe panel should:

  • Show the transaction clearly as pending, not as failed.
  • Warn or block when someone tries to pay the same bill again while a payment is pending.
  • Run status enquiries until the final status is confirmed.
  • Update the transaction, the receipt and the ledger only when the final status arrives.

A practical status workflow

  1. The payment is submitted and stored with an internal reference.
  2. If no final response arrives, it is marked as pending.
  3. The system runs status enquiries at sensible intervals.
  4. On success, the receipt is finalised with the BBPS reference.
  5. On failure, any amount held or debited is reversed according to the agreed process.
  6. Every change is recorded in an audit trail.

Reconciliation

Reconciliation compares three views of the same activity: your platform's transactions, the settlement and reports from your operating-unit partner, and your internal ledger.

  • Match on both the internal reference and the BBPS reference.
  • Investigate any mismatch, such as a payment that succeeded in one view but is pending in another.
  • Run reconciliation daily, not monthly.
  • Give finance teams exportable reports, not screenshots.

Complaints for disputed payments

When a customer disputes a payment, the complaint should be raised against the specific transaction, so the reference, status history and receipts are already attached. This shortens resolution time considerably.

Good pending-payment handling is invisible when it works. It is one of the most important things to verify before you choose a BBPS platform.

Planning to launch BBPS bill payments?

Compare our BBPS White Label and BBPS Panel, or book a demo to see both.

Book a Demo
All resources

See the panel and plan your launch

Book a demo to walk through the white-label setup, the retailer and distributor panel, and the onboarding steps.