v1
latestOpenAPI 3.1.02026-07-24416405768.8 KBGet a payment by ID
Path parameters
Query parameters
send includeCallbackResult to enrich extraInfo field with callback data
Response
OK
If the payment can be made by card then the allowed card schemes that can be used
The ways that the payment can be made
The amount payable. Amounts are in major currency unit
Contain Json string for purchase amount minimum and maximum. If it is not empty then the purchase amount must be in between of min and max amount specified in this attribute(min and max inclusive) and that amount must be sent on the updated purchase request
Deprecated. Use phone instead
URL to open in an iFrame or browser where customer can securely complete 3DS details if required. Normally this will not be provided until the payment has been posted/updated with sufficient data to be processable. However this is provided for GLOBAL_PAYMENT_LINK payments as these dont require further info from the API caller for the payment to be made
When the payment was posted
The currency of the payment amount - e.g. USD, ZAR, NGN, TSH
A description for the payment created from the payment data.E.g. Merchant info and QR description for a QR payment
Data delivered to the chip card including the ARPC cryptogram for online issuer authentication
This will only be populated if there was an error
When the payment must complete by. If not in final state before this time, Eclipse will timeout the payment
Loosely typed data resulting from the payment. E.g. could be a voucher id if the payment was for a VAS. The structure depends on what was being paid for.
The transaction identifier for this payment as provided by the gateway itself
When the payment was last modified
Optional. Any location information to add to the payment such as GPS coordinates or branch name etc
The unique identifier for the merchant
The name of the merchant to whome the payment will go
Reference for the merchant
payment receiver’s wallet ID, if applicable.
Will be true if the value allows a partial payment and amount must be sent on the updated purchase request
Loosely typed data about the payment. Depends on the payment type. E.g. could be a QRCode
Unique identifier for this payment transaction
The deduced type of payment being done based on the type and paymentData
Status of a payment BUILDING: Not yet submitted as more data needs to be captured, PENDING:Being processed and can no longer be enhanced, SUCCESSFUL: Successfully completed, ERROR_PERM: Failed and wont ever succeed, ERROR_TEMP: Currently having an error but its being retried and may succeed or permanently fail, TIMEOUT: Failed as the process was not finalised in time, CANCELLED: Cancelled prior to SUCCESS or FAILURE, REVERSED: Reversed after success
Tracing data about the payment
Example response
{
"created": "2022-03-10T12:15:50-04:00",
"expires": "2022-03-10T12:15:50-04:00",
"lastModified": "2022-03-10T12:15:50-04:00"
}