Identifiers and Required Fields
A Product communicates its required parameters through specific identifier fields. These dictate the data needed for a transaction.
Possible Required Fields
The specific fields required for a transaction depend on the Product, Service, and Operator.
Credit Party Identifier
The receiving party of the product value (e.g., mobile number or account number).
Debit Party Identifier
Sender details (e.g., sender mobile number for validation).
Sender & Beneficiary Fields
Details about the transaction parties, such as full names, emails, and addresses.
Statement Identifiers (Bills)
Information used for bill payments (e.g., reference number, due date).
Statement Identifiers (Misc)
Miscellaneous identifiers (e.g., Purchaser ID for Gift Cards).
What Happens If Required Parameters Are Missing?
If required parameters are not provided, the API returns a validation error, preventing the transaction. Clients must ensure all required fields are included in the request payload.
Example
For the Mobile Recharge product (Product Type
FIXED_VALUE_RECHARGE
), the mobile number is a
required Credit Party Identifier.In contrast, a
FIXED_VALUE_PIN_PURCHASE
product typically does not require a mobile number.
Updated 3 months ago