Airwallex Payment

Prepare an Airwallex account

Sign in to the Airwallex demo environment  or production environment . Under Settings → Developers → API Keys, create an API key and save the Client ID. The API key is shown only when it is created; regenerate it if it is lost.

If the account uses a legal entity or linked payment account, obtain the Legal entity ID and Linked payment account ID under Settings → Entities.

Activate Airwallex

Open Action → Payment → Airwallex (Web) and select Activate. If this is the project’s first gateway, select the order table.

After activation, open the generated Airwallex Payment Processing Actionflow from Related Actionflows. Select its Webhook Trigger and copy the Webhook URL.

Create the Airwallex webhook

Under Settings → Webhooks in Airwallex, create a Webhook with:

• API version: Enter the fixed value 2025-11-11.
• Account: Select the account represented by the Linked payment account ID, or the current collection account when no linked account is used.
• Notification URL: Paste the Webhook URL from the Airwallex Payment Processing Actionflow.
• Events: Select the following events.

payment_intent.succeeded
payment_intent.cancelled
invoice.finalized
subscription.in_trial
subscription.active
subscription.unpaid
subscription.cancelled
subscription.modified
refund.accepted
refund.failed

Copy the Webhook secret after creating the Webhook.

Enter the payment settings

Save and publish the payment configuration, system tables, Actionflows, and frontend changes. Do not mix demo credentials with the production environment.

Create an order and add the action

Create an order in the bound order table, then add Airwallex → One-off payment from the Payment category under a page or component Trigger.

Disable or debounce the payment button until the action returns or checkout closes to avoid opening multiple checkouts.

The action’s On success branch means the frontend call returned successfully and cannot contain data mutations. Confirm the final payment result through the Webhook.

Handle the payment webhook

The Sync Payment Status node exposes:

Run successful fulfillment only when paymentId is present, paymentStatus is SUCCESSFUL, and alreadyProcessed is false. Compare the payment amount and currency with the trusted order first.

Restrict permissions and add the action

Refund actions should not be available to regular users. Under Settings → Permissions → Payment, enable Airwallex refunds only for a trusted administrator role.

Add Airwallex → Refund from the Payment category:

Check successful refund records and the cumulative refunded amount before starting another refund.

Handle the refund webhook

The Sync Refund Status node exposes:

Handle the result only when refundId is present and alreadyProcessed is false.

Start a subscription

Add Airwallex → Recurring payment → Initiate.

The frontend branches represent the subscription authorization interaction. Treat the status synchronized by the Webhook as the actual activation result.

Cancel a subscription

Add Airwallex → Recurring payment → Cancel and bind the Recurring payment id from recurring_payment.

Handle subscription status

Airwallex Payment Processing receives subscription.in_trial, subscription.active, subscription.unpaid, subscription.cancelled, and subscription.modified, then updates recurring_payment.

The synchronization result includes recurringPaymentId and status. Stored states include INCOMPLETE, TRIALING, ACTIVE, UNPAID, and CANCELED. subscription.modified is a Webhook event, not a stored status named MODIFIED.

Enable, pause, or revoke subscription benefits in the ACTIVE, CANCELED, or other state branches required by your product.

Create renewal orders

An invoice.finalized event starts renewal processing. Momen obtains or creates the current payment record from the Invoice ID and opens the Airwallex Subscription Renewal Processing Actionflow.

In the reserved order-creation section:

1. Create the period’s business order from the first subscription order and fill in its amount, account, and other fields.
2. Pass the new order ID to the following system step so the current payment record is associated with it.
3. Fulfill the period only after the corresponding payment status is confirmed.

The template checks whether the current payment already has an order ID to avoid creating the renewal order twice. Any additional business nodes still require their own idempotency controls.