Issuing

As described in the Purchase lifecycle docs, card transactions may come to you in two phases:

In the first phase, you would receive an issuing.transaction.succeeded authorization event (matching the AUTHORIZATION event type in the Get Transactions API) with the following payload:

In the second phase, if your transaction authorization succeeded, you would receive an issuing.transaction.succeeded event (matching the CLEARING event type in the Get Transactions API) within 7 days with the following payload. You can match clearing events to their corresponding authorization events using the matched_authorizations field:

• If your transaction authorization failed, you would receive an issuing.transaction.failed event with the following payload:

• If your transaction authorization was reversed or has not been cleared within 7 days, you would receive an issuing.transaction.succeeded event (matching the REVERSAL event type in the Get Transactions API) with the following payload. The matched_authorizations field indicates the original authorization that was reversed:

Card transactions may come to you in one single phase and you would only receive one issuing.transaction.succeeded event (matching the CLEARING event type in the Get Transactions API) with the following payload:

In the event of a refund (of a previously cleared transaction), you would receive an issuing.transaction.succeeded event (matching the REFUND event type in the Get Transactions API) with the following payload:

In the event Airwallex renews an issued card you would receive an issuing.reissue.succeeded event with the following payload. The card ID will remain the same while other details such as the expiry date and CVV will be updated.