Run in Apidog
šø Execute Payment ā Final Step in Invoice Flow# This method allows clients to submit a payment request for a postpaid product after completing Steps 1 and 2 of the invoice workflow. It finalizes the process by confirming the amount, recipient data, and operation details. š Description# 1.
Retrieved the required input fields via Get Parameters
2.
Queried the invoice with those fields and obtained a transaction_code
...this endpoint is used to execute the payment . The request must include: All fields listed in the pay array from Step 1
Any additionalData returned in Step 2
The amount to send (in cents)
Optionally: a beneficiaryPhoneNumber for SMS confirmation, if enabled
š„ Request# Field Type Required Description amountToSendX100integer ā
Yes Amount to send, in cents (e.g., 5000 = ā¬50.00) localDateTimestring ā
Yes ISO 8601 timestamp representing when the transaction is initiated beneficiaryPhoneNumberstring Optional If SMS notifications are enabled, use this to inform the end user additionalDataarray ā
Yes Key-value array including all fields from pay (Step 1) and data from Step 2 invoiceNumbersarray Optional List of strings obtained from get invoices (Step 2)
š About additionalData# The additionalData array must contain: All static fields required in the pay array from Step 1 (e.g., card_code, document_number)
All dynamic values returned in Step 2 (e.g., transaction_code, due_date)
š¤ Response# {
"rc" : 0 ,
"items" : [
{
"finalstatus" : 0 ,
"resultcode" : "0" ,
"resultmessage" : "Payment successful" ,
"supplierreference" : "CSQ-REF-2024-XYZ" ,
"suppliertoken" : "TXN-987654321" ,
"destinationcurrency" : "EUR" ,
"destinationamount" : 5000
}
]
} š§ Usage Notes# Always call this method last , after successfully completing Steps 1 and 2 of the payment flow.
The additionalData field must include all expected keys and values: Static fields required in pay
Dynamic values returned in the invoice step
For DISCRETE payment types: Include invoiceNumbers client wants to pay.
The value must be a String list of selected invoice references
The amount sent (amountToSendX100) must match the logic of the product (TOTAL, DISCRETE, or OPEN)
The response contains reference information (supplierreference, suppliertoken) useful for audit and reconciliation
In case of failure, check rc, resultcode, and resultmessage for diagnosis
Request Body Params application/json
{
"amountToSendX100" : 0 ,
"localDateTime" : "2019-08-24T14:15:22Z" ,
"beneficiaryPhoneNumber" : "string" ,
"invoiceNumbers" : [
"string"
] ,
"additionalData" : [
{
"key" : "string" ,
"value" : "string"
}
]
} Request Code Samples
curl --location --request POST 'https://evsb.csqworld.com/post-paid/bill-payment/payment///123456789' \
--header 'U: {{U}}' \
--header 'SH: {{SH}}' \
--header 'ST: {{ST}}' \
--header 'Content-Type: application/json' \
--data-raw '{
"amountToSendX100": 0,
"localDateTime": "2019-08-24T14:15:22Z",
"beneficiaryPhoneNumber": "string",
"invoiceNumbers": [
"string"
],
"additionalData": [
{
"key": "string",
"value": "string"
}
]
}' Responses
{
"rc" : 0 ,
"items" : [
{
"finalstatus" : 0 ,
"resultcode" : "string" ,
"resultmessage" : "string" ,
"supplierreference" : "string" ,
"suppliertoken" : "string" ,
"destinationcurrency" : "string" ,
"destinationamount" : 0
}
]
} Modified atĀ 2025-07-28 20:17:51