If your store runs on WordPress and WooCommerce and you want to accept credit cards, Apple Pay, Google Pay, and various local payment methods, Airwallex is a directly integrable payment gateway with an official WooCommerce plugin. The plugin supports connecting via OAuth login or manual API credentials, and once set up enables card payments, express checkout, and multiple local payment options at checkout. For cross-border stores, pairing Airwallex with PayPal rather than relying on a single payment method is the stronger approach โ giving customers more options directly reduces cart abandonment from payment method mismatches.
What to Have Ready Before Starting
Per current official documentation: a functioning WooCommerce store on WordPress 4.5 or higher, WooCommerce 3.0 or higher, and PHP 7.3 or higher. An Airwallex account with the payment methods you need already activated in the dashboard. If using manual API key connection, prepare the Client ID, API Key, and Webhook Secret Key in advance. These are the minimum compatibility versions โ in practice, running current actively-supported versions of WordPress, WooCommerce, and PHP is the better approach. Test and back up before upgrading anything.
Step One: Complete Business Account Registration and Review
Account registration is prerequisite. After registering, submit business information and complete identity verification (KYB/KYC) and business review. The most commonly missed detail at this stage: the plugin can only use payment methods that are already activated in the Airwallex dashboard. Before configuring the WooCommerce plugin, go to Airwallex's Payments โ Payment Methods and activate the methods you need. Discovering a greyed-out option after installation, then realizing approval was never submitted, is an avoidable delay.
Step Two: Install the Plugin
Two paths exist. The simplest: in WordPress admin, go to Plugins โ Add New, search for Airwallex, find the official Airwallex Online Payments plugin, click Install Now, then Activate. Alternatively, it can be added through the WooCommerce Marketplace. For most WordPress users, the direct plugin directory install is the more straightforward route.
Step Three: Connect WooCommerce to Your Airwallex Account
After installation, go to WooCommerce โ Settings โ Payments โ Airwallex and open the API Settings tab. The recommended connection method is OAuth โ click Connect Account, log in to your Airwallex account, and after a successful connection the plugin displays a green "Connected" indicator next to the Airwallex logo. Save settings.
If OAuth fails, switch to manual API credential entry. The Client ID, API Key, and Webhook Secret Key are found in the Airwallex WebApp under Settings โ Developer โ API keys. The official recommendation is to use a scoped API key with only Edit and View permissions under "Payment Acceptance" โ not the full-access primary account key.
A common real-world issue: if the WooCommerce site URL doesn't exactly match the URL registered with Airwallex (for example, one uses https://example.com and the other uses https://www.example.com), OAuth connection will likely fail. In that case, switch to manual API key connection. If using manual connection, a Webhook must also be created manually โ OAuth handles this automatically, manual connection does not. Before going live, confirm the primary domain, HTTPS configuration, and www prefix are consistent across all relevant settings.
Step Four: Enable Card Payments
Go to WooCommerce โ Settings โ Payments โ Airwallex โ Cards and check Enable Airwallex Card Payments. The checkout page displays icons for card networks that are actually enabled in the Airwallex account โ Visa, Mastercard, American Express, UnionPay are among the supported networks, along with potentially JCB, Diners Club, Discover, and others. Which icons appear is determined entirely by which networks are activated in the account, not by installing the plugin.
Step Five: Enable Apple Pay and Google Pay
For cross-border e-commerce, card payment alone is insufficient. In markets with high mobile traffic, Apple Pay and Google Pay allow users to complete checkout using saved device payment information without re-entering card numbers, expiry dates, and CVCs โ a meaningful reduction in checkout friction. Both can be configured directly within the Airwallex WooCommerce plugin, but actual availability depends on your region, payment method eligibility review, domain configuration, and account approval status.
On Enabling All Payment Methods
If customers come from multiple countries, the Airwallex Drop-in payment component is worth examining โ it presents all activated payment methods (cards, Apple Pay, Google Pay, local payment methods) in a unified checkout interface. That said, enabling everything indiscriminately isn't the right approach. Match available methods to what customers in your target markets actually use: for the US market, prioritize Visa, Mastercard, American Express, Apple Pay, Google Pay, and PayPal; for Europe, add local options like Klarna, iDEAL, and Bancontact; for Asian markets, evaluate Alipay, WeChat Pay, and GrabPay by country. The number of local payment methods supported varies across different sources and continues to change โ the accurate reference is what's available for approval in your actual account.
Multi-Currency Checkout Requires Configuration
If products are priced in USD, whether European customers see EUR pricing depends on your Airwallex merchant account configuration โ it's not automatic. Which currencies to enable requires planning around your target markets, settlement currency settings, activated payment methods, and account configuration. Multi-currency support doesn't activate itself on installation.
Understanding Order Status: This Directly Affects Fulfillment
Payment success at checkout is not the same as order completion at the moment a user returns to the site. Airwallex PaymentIntents have several states: awaiting payment method, awaiting customer action, awaiting capture confirmation, processing, pending review, successful, and cancelled. Only a "successful" status confirms that payment has been genuinely captured. The official recommendation is to trigger fulfillment only after reaching that status. A "processing" status means payment is still in async processing โ wait for the final result before acting. Fulfilling orders based on the user landing back on the site, rather than waiting for confirmed payment status, leads to incorrect shipments or missed deliveries for businesses handling physical goods, automated delivery, or digital product access.
Why Webhooks Are the Most Critical Part of This Integration
The checkout page collects payment. Webhooks are how Airwallex actively notifies your system of the final payment outcome. The complete chain: user completes payment โ Airwallex processes and updates status โ Webhook pushes status change to WooCommerce โ WooCommerce updates order status. Production environments should rely on Webhooks to receive payment events rather than depending on user redirect back to the site. If a user closes the browser during payment, has a network interruption, or the redirect fails, that action may not occur even though payment succeeded. Redirect-based status detection is inherently unreliable.
For troubleshooting payment issues, enabling debug logging helps significantly. Add this to wp-config.php to enable WooCommerce debug logs:
// Add to wp-config.php โ enables WordPress debug logging (disable after troubleshooting)
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
Logs are viewable at WooCommerce โ Status โ Logs. When order status isn't syncing, check here first rather than guessing.
Test With Sandbox Before Going Live
In WooCommerce โ Settings โ Payments โ Airwallex โ API Settings, enable sandbox mode and connect to Airwallex's demo/sandbox account to simulate the complete payment flow without real funds. Test at minimum four scenarios: a normal successful payment (confirm checkout works, Airwallex receives payment, WooCommerce creates the order with correct status); a payment failure (intentionally use an invalid card or simulate insufficient funds โ confirm users can return to checkout rather than getting stuck on an error page); a 3D Secure verification flow (confirm the verification popup or redirect displays correctly); and a refund (confirm that processing a refund leaves both WooCommerce order status and Airwallex records consistent).
Switching From Sandbox to Production
After successful sandbox testing, disable sandbox mode, reconnect to the Production Airwallex account, save settings, and run a small-value real transaction. Sandbox passing means the basic technical connection works โ it doesn't guarantee everything works in production. Payment method approval status, merchant account risk controls, real 3DS verification behavior, variation across card types and user locations, real-environment Webhook triggering, and configuration validity under a live domain can all behave differently than in sandbox. Monitor the first few real orders closely.
Handling Refunds
In the Airwallex WebApp under Payments โ Payment Activity โ All payments, find the relevant order and select Refund for full or partial refund. The payment must be in a successful state and not under dispute to be eligible. Refunds return to the original payment instrument โ they cannot be redirected to a different card or account. For payments made with automatic currency conversion, calculate the refund based on the original transaction currency and amount rather than applying the current exchange rate โ the amounts won't match and can trigger disputes. Tell customers in advance that a successful refund operation doesn't mean immediate receipt โ final arrival depends on the customer's issuing bank or payment provider processing time, which Airwallex cannot control.
Common Post-Launch Issues and How to Diagnose Them
Payment succeeds but WooCommerce order status doesn't update: Check Webhook configuration, verify API credentials aren't mixing Production and Sandbox keys, review WooCommerce โ Status โ Logs, confirm Cloudflare, caching plugins, or security plugins aren't blocking payment callback requests, verify HTTPS certificate is valid.
Airwallex payment options not appearing at checkout: Confirm the payment method is actually activated in Airwallex; confirm the option is enabled in WooCommerce payment settings; clear browser and site cache; open browser JavaScript console for errors; temporarily deactivate recently installed payment or performance plugins to check for conflicts. JS lazy loading, JS/CSS combining, third-party security plugins, and Cloudflare optimization settings are frequent culprits.
Payment button click produces no response: Open the browser console with F12 immediately. 403, 401, CORS, blocked, or failed-to-load errors point toward API permissions, CDN blocking, firewall rules, Content Security Policy settings, or JS optimization plugins. Reinstalling WooCommerce is almost never the fix for this type of issue.
Cost Calculation
The real payment cost for a DTC store combines processing fees, cross-border costs, currency conversion costs, and refund or dispute costs. The specific numbers depend on merchant country, payment methods used, card type, transaction currency, settlement method, and account plan. Check Airwallex's current Pricing page directly โ the fee structure has changed multiple times and any article's stated figures (including this one) may be outdated.
One practical cost advantage worth noting: Shopify charges an additional third-party transaction fee when using non-Shopify-Payments gateways like Airwallex. WooCommerce, as a self-hosted open-source platform, has no platform layer extracting that additional cut. For total cost comparisons between Shopify and WooCommerce deployments, this difference is worth including in the calculation.
Is Airwallex Worth Integrating Into WooCommerce?
Yes, if customers come from multiple countries, multi-currency collection and local payment support matter, the business is primarily cross-border e-commerce, and you already use Airwallex for treasury management โ consolidating payments into the same financial ecosystem makes sense. No, if the site is primarily a corporate showcase with few orders, a highly concentrated customer base, or existing payment gateways running stably with no specific reason to switch.
What determines whether this integration runs stably isn't whether the plugin was installed โ it's whether the complete flow was walked through: account setup, payment method activation, OAuth or API connection, sandbox testing, Webhook and order status verification, and production launch. Skipping any stage risks problems appearing on real orders.