After selecting a product through API discovery, transactions can be processed in either synchronous or asynchronous mode
Asynchronous (Recommended)
- The HTTP connection closes immediately, preserving system resources.
- Ideal for efficient processing.
- Retrieve the final status with a callback or by querying the API.
Synchronous
- The HTTP connection remains open to receive the final status from the operator.
- Response time varies; the system waits up to 180 seconds (configurable upon request).
- The response includes either a final status (
COMPLETED
,DECLINED
,REVERSED
,CANCELLED
) or an intermediateSUBMITTED
status, depending on the operator's processing time. - If
SUBMITTED
, the transaction is still being processed by the operator. - Applications can close the connection early and query the final status later.
Upon transaction confirmation, the transfer order is sent to the operator for immediate processing, and the transaction enters a CONFIRMED
status.
Obtaining Final Transaction Status
Regardless of the processing mode, your application must capture the final transaction status. This can be achieved in the following ways:
API Query (Pull)
- Check the status of a specific transaction by using the API method.
Callback URL (Push)
- Receive status updates by configuring a callback URL in the transaction creation request.