Skip to main content

Prefunding and Balance Management

Under the Account-Based API Model, prefunding of a CellPay wallet is not required. Instead, all transactions are executed directly against the API consumer’s linked bank account.

API consumers are responsible for maintaining adequate balance in the linked account to ensure uninterrupted transaction processing. Balance availability is validated in real time during transaction execution. Transactions will fail if sufficient funds are not available at the time of authorization.

CellPay may apply configurable thresholds, limits, or alerts to support balance monitoring and operational continuity. Any overdraft or credit arrangements, if applicable, must be explicitly agreed upon and documented during onboarding.

Transaction Processing Behavior​

Transactions initiated under the Account-Based API Model follow CellPay’s standard validation and authorization workflow, with additional account-level controls.

Upon receiving a transaction request:

  • Input parameters are validated against service rules
  • Account status and permissions are verified
  • Real-time balance sufficiency checks are performed
  • Transactions are authorized and routed through CellPay’s banking and service provider infrastructure

If all validations are successful, the transaction is executed and recorded with a unique transaction reference. Failed or rejected transactions do not result in partial debits.

All transaction states, including success, failure, or reversal, are logged and made available for reconciliation and audit purposes.

Settlement and Reconciliation​

Settlement under the Account-Based API Model is performed directly between the API consumer’s linked bank account and CellPay’s settlement accounts, in accordance with the agreed settlement arrangement.

Settlement may occur in:

  • Real time, or
  • Scheduled cycles (e.g., intraday or end-of-day), depending on the service and partner bank configuration

CellPay provides transaction reports and settlement statements to support reconciliation. These reports include transaction identifiers, timestamps, amounts, service details, and settlement status.

API consumers are expected to perform regular reconciliation between:

  • Their internal transaction records
  • Bank account statements
  • CellPay-provided settlement reports

Any discrepancies must be reported to CellPay within the agreed dispute resolution timeline.

Risk and Operational Considerations​

The Account-Based API Model is subject to enhanced risk controls due to its direct interaction with bank accounts. Key considerations include:

  • Stricter transaction and volume limits may apply
  • Transactions are subject to real-time fraud and AML monitoring
  • Service availability may depend on banking partner uptime
  • Unauthorized or malformed requests are rejected immediately

API consumers must implement adequate internal controls, including credential security, transaction monitoring, and access management. Any misuse, abnormal transaction patterns, or security incidents may result in temporary suspension of API access.

CellPay reserves the right to adjust limits, enforce additional controls, or suspend services to comply with regulatory or risk requirements.

Applicability​

The Account-Based API Model is best suited for:

  • Enterprises with high transaction volumes
  • Institutions requiring direct bank settlement
  • Partners with established treasury and reconciliation processes
  • Use cases where wallet prefunding is operationally inefficient

This model may not be suitable for:

  • Small merchants requiring instant wallet-based balance visibility
  • Use cases requiring micro-transactions or offline tolerance
  • Partners unable to meet bank-level compliance and monitoring requirements

Selection of the Account-Based API Model is subject to CellPay’s assessment of operational readiness, regulatory compliance, and risk profile.