Skip to main content

Payment Model Overview

CellPay follows a standardized payment model for all utility services processed through its APIs. Under the Wallet-Based integration model, all transactions are executed against the prefunded CellPay wallet maintained by the API consumer.

Before initiating a payment, the API consumer must determine the appropriate service configuration, including the applicable payment type, service identifier, and required input parameters. These values are system-defined and are required to correctly route the transaction.

Depending on the nature of the service, transactions may require either fixed input parameters or dynamically retrieved configuration values. Some services expose predefined configurations such as packages or plans, while others accept direct user input without requiring additional configuration retrieval.

The Get Possible Values mechanism allows API consumers to dynamically obtain configuration data required for payment execution. This includes:

  • Available utility services enabled for the API consumer
  • Corresponding transferTypeId values
  • Required input fields for each service
  • Package or plan identifiers for package-based services
  • Field metadata such as field IDs and internal names

Where applicable, CellPay provides mechanisms to retrieve possible values required for transaction processing. These values are system-defined and may include service identifiers, required input fields, or package information. For services that do not require dynamic configuration, API consumers may proceed directly to the payment flow using known parameters.

API consumers must determine whether a service requires possible values based on the service configuration and integration guidelines provided by CellPay. Failure to use the correct or latest values may result in validation errors or rejected transactions.