Skip to main content
Airwallex is a global financial platform that provides cross-border payment processing for businesses of all sizes. The platform supports card payments with features like delayed capture, partial capture, partial refunds, 3-D Secure authentication, network tokenization, and digital wallet integration across multiple currencies and countries.

​
Setup

Airwallex offers self-service sign-up for production and demo (sandbox) accounts:

​
Credentials

When setting up Airwallex in the dashboard, configure the following credentials. The Client ID and API Key can be found in the Airwallex web app under Developer -> API keys, and the Webhook Secret is generated under Developer -> Webhooks.
  • Client ID - The unique identifier for your Airwallex account.
  • API Key - A secret API key used to authenticate requests. Treat this value as a password.
  • Webhook Secret (optional) - The signing secret used to validate webhook payloads. Generate this when creating a webhook endpoint in the Airwallex web app.

​
Connector configuration

After setting up your Airwallex connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:
  • Using Flow - Configure Airwallex as the target connector in Flow to automatically route card transactions to this connector
  • Using the API - Explicitly set the payment_service_id parameter to the Airwallex connector ID when creating transactions. This overrides any Flow routing rules.
The connector ID can be found in the dashboard under Connections -> Configured connections.

​
Features

Airwallex supports the following features:
  • Delayed capture - Authorize a payment and capture it at a later time
  • Partial capture - Capture a portion of the authorized amount
  • Refunds - Refund transactions in full
  • Partial refunds - Refund a portion of the captured amount
  • Void - Cancel an authorized transaction before capture
  • Zero auth - Verify a card without charging it
  • Digital wallets - Support for Apple Pay and Google Pay via wallet pass-through
  • Network tokens - Network-level tokenization is enabled by default for enhanced security and approval rates
  • 3-D Secure - Support for both hosted and pass-through 3DS authentication
  • Transaction sync - Automatic synchronization of transaction status updates
  • Webhooks - Receive asynchronous status updates for payment intents and refunds

​
Supported countries

Airwallex supports transactions from buyers in the following countries:
Country codeCountry codeCountry codeCountry codeCountry codeCountry codeCountry codeCountry code
ATAUBEBGBRCACHCN
CRCYCZDEDKEEESFI
FJFRGBGFGIGPGRHK
HRHUIDIEILIMINIS
ITJPKRKYLILTLULV
MFMHMOMQMTMXMYNL
NONZPHPLPRPTRERO
SCSESGSISKTHTWUS
VGVIVNWSYT

​
Supported currencies

Airwallex supports processing payments in the following currencies:
Currency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency code
AEDALLAMDAOAARSAUDAWGAZN
BAMBBDBDTBHDBIFBMDBNDBOB
BRLBSDBTNBWPBZDCADCHFCLP
CNYCOPCRCCVECZKDJFDKKDOP
DZDEGPERNETBEURFJDFKPGBP
GELGHSGIPGMDGNFGTQGYDHKD
HNLHUFIDRILSINRISKJMDJOD
JPYKESKGSKHRKMFKRWKWDKYD
KZTLAKLBPLKRLRDLSLLYDMAD
MDLMGAMKDMNTMOPMURMVRMWK
MXNMYRNADNGNNIONOKNPRNZD
OMRPABPENPGKPHPPKRPLNPYG
QARRONRSDRWFSARSBDSCRSEK
SGDSHPSLESRDSVCSZLTHBTJS
TMTTNDTOPTRYTTDTWDTZSUAH
UGXUSDUYUUZSVNDVUVWSTXAF
XCDXOFXPFZARZMW

​
Limitations

The following features are not supported by this connector:
  • Over capture - Capturing more than the authorized amount
  • Multi capture - Performing more than one capture against a single authorization
  • Partial authorization - Accepting a partial amount when the full amount cannot be authorized
  • Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
  • Settlement reporting - Automatic settlement reporting is not supported

​
Integration

To accept card payments with Airwallex, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which automatically routes the payment to your configured Airwallex connection based on your Flow rules or explicit payment_service_id parameter.

​
Sending billing information

Airwallex strongly recommends that merchants pass enhanced risk data fields to improve the performance of the risk engine. For more details on how Airwallex leverages a wide range of signals to safeguard transactions, see Enhance fraud protection with comprehensive payment data. Billing details on the buyer object can be sent using either an inline guest buyer or a stored buyer reference when creating a transaction.

​
Device fingerprinting

A key integration requirement for all Gr4vy merchants using Airwallex is to load the Airwallex Risk JavaScript on the checkout page and forward the resulting device data to Airwallex via Gr4vy’s API.
  1. Load the Airwallex Risk JavaScript and collect device data. Follow Step 1 and Step 2 in the Airwallex device fingerprinting integration guide to load the script on your checkout page and collect device data. The device data is stored in the order session ID via data-order-session-id="ORDER-SESSION-ID".
  2. Pass the collected device data to Airwallex when creating a transaction using the anti_fraud_fingerprint field.

​
External 3-D Secure and risk engines

To enable an external 3-D Secure provider or external risk engine for Airwallex — including Gr4vy-provided 3DS or risk tools — contact your Airwallex Account Manager for support.

​
Webhooks

Airwallex uses webhooks to deliver asynchronous status updates for payment intents and refunds. Register a notification URL and select the events to receive in the Airwallex web app under Developer -> Webhooks to keep transaction and refund statuses in sync. The generated signing secret is optional for connector setup, but Gr4vy recommends adding it to the Webhook Secret field on your connector so Gr4vy can validate webhook signatures.

​
Testing

For testing in the Airwallex demo environment, you can use standard test card numbers. Airwallex supports industry-standard test cards for simulating different transaction scenarios: Successful transactions:
  • Visa: 4111 1111 1111 1111
  • Mastercard: 5555 5555 5555 4444
  • American Express: 3782 822463 10005
Use any future expiry date and any 3-digit CVV (4 digits for American Express). For more test scenarios and additional card numbers, refer to the Airwallex testing documentation or contact your Airwallex representative.