Handle exceptions
The response returned from your remote authorization gateway may differ from Airwallex’s final decision on a transaction. The Airwallex platform webhooks provide a solution to reconcile these discrepancies.
Once you have configured and enabled remote authorization, a remote_auth field will be added to your webhook notifications indicating how Airwallex processed your response and how it has affected the transaction authorization as a whole. This field will not be returned for transactions that do not use remote authorization, e.g. capture requests. You can retrieve authorization transactions using Get transactions API and Get authorization status API.
Timeouts
A timeout occurs when Airwallex fails to receive a response from your endpoint to the remote authorization request within two seconds. This is required to comply with the card network SLA. The transaction proceeds using the default action configured in your account settings. The sample below shows the remote_auth field returned in the authorization response for a timeout scenario.
Errors
If your remote authorization endpoint doesn't return a valid response or a success response (HTTPS status code 200), the transaction proceeds using the default action configured in your account settings.
The sample below shows the remote_auth field returned in the authorization response for an error scenario.
Failed internal checks
If the transaction fails Airwallex’s internal risk or regulatory checks (see, Authorization controls ), Airwallex can decline an authorized remote authorization request as the final decision for the authorization transaction.
The sample below shows the remote_auth field returned in the authorization response for a failed internal check. However, the status field for the authorization will return FAILED.