Search...
Log inGet started
Airwallex logo
Home
Core API
Payments
Transactional FX
Payouts
Issuing
Back to home
Get started
QuickstartManage API keys
Webhooks
Listen for webhook events
Event types
Payload examples
AccountBatch payoutsBillingConversionsChargesDepositsDirect debit payoutsTransfers PayoutsGlobal AccountsIssuing
Linked AccountsOnline PaymentsPlatformRFI
Code examples
Test webhook event payloadsView webhook eventsRe-trigger webhook events

Issuing

Listed below are the webhook events relevant for Issuing:

  • issuing.transaction.succeeded
  • issuing.transaction.failed
JavaScript

data is the transaction object from Get card transactions API. source_id is the transaction id this webhook corresponds to.

Examples of different transaction event data objects are displayed below.

Authorization and clearing

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 to the AUTHORIZATION event type in the Get Transactions Endpoint API) with the following properties:

JavaScript

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

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

Single-phase transactions

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

JavaScript

Refunds

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

JavaScript
On this page
  • Authorization and clearing
  • Single-phase transactions
  • Refunds