Skip to main content
The Airwallex integration is currently in Public Beta. During the beta, only self-serve (PLG) checkout is supported; enterprise contracts (SLG) and coupons aren’t supported yet.
Airwallex is a global payment service provider (PSP) with native support for cross-border and FX payments. Stigg’s native integration with Airwallex enables:
  1. Collecting payment for self-serve checkout (PLG), using Airwallex’s embedded payment form directly in Stigg’s checkout widget.
  2. Pushing the invoices Stigg generates to Airwallex, and collecting payment for them there.
  3. Charging customers in the currency of the prices you define in Stigg’s product catalog.
  4. Automatically vaulting a customer’s payment method for future recurring charges.
  5. Receiving payment status back from Airwallex (for example, a successful charge) to keep Stigg’s invoices up to date.

​
How it works

Customers select a plan and enter their payment details in Stigg’s checkout widget. Stigg provisions the subscription, generates an invoice, and Airwallex collects the payment for it.
Airwallex isn’t a catalog sync target. Stigg’s Invoicing module remains the system of record for your product catalog and subscriptions, and generates the invoices — Stigg then pushes each invoice to Airwallex, where the payment for it is collected. This is different from the Stripe and Zuora integrations, which sync the full product catalog to the billing platform. See Entity mapping below.

​
Entity mapping

Stigg’s product catalog and subscriptions are not synced to Airwallex — they’re managed entirely within Stigg’s Invoicing module. Only customers, payment methods, invoices, and payments are created in Airwallex.

​
Accessing Airwallex entities from Stigg

In the Stigg app, clicking on the link of the “billing ID” property will open the relevant entity in Airwallex:
  • Customers link to the customer in Airwallex.
  • Subscriptions and credit grants link to their invoice in Airwallex.
You can also view a customer’s saved Airwallex payment method from their Payment details section in the Stigg app.
Because the product catalog isn’t synced, plans, add-ons, and other catalog entities don’t have an Airwallex billing ID the way they do for Stripe or Zuora.

​
Setting up the integration

Setting up the integration takes two steps: get your credentials from Airwallex, then enter them in Stigg.

​
1. Get your credentials from Airwallex

In the Airwallex dashboard for the environment you’re connecting (sandbox or production):
  1. Go to Developer > API keys and click New scoped key.
  2. Give the key a name, grant it the permissions listed below, and create it.
  3. Copy the key’s Client ID (shown in the API keys table) and the generated API key.
  4. Obtain your Org ID (org_...). You can find it on the API key’s Overview page, under Access to > Organisation.
  5. Go to Settings, and under Entities, open the account you want Stigg to route checkouts to. Copy the Account ID (acct_...) from the Account details panel.
You’ll also need the API URL for the Airwallex environment you’re connecting:
Airwallex only shows the API key once. Store it securely — if it’s lost, generate a new scoped key and reconnect the integration in Stigg.

​
Permissions required

Grant the scoped API key the following permissions, at the level shown for each:
If the key is missing any of these permissions, or a permission is granted at the wrong level, Stigg can’t fully set up the integration. The integration still connects, but is flagged with a setup error (for example, “Insufficient permissions for subscribing to payment_intent.succeeded”) until you reconnect with a correctly scoped key.

​
2. Enter the credentials in Stigg

  1. In the Stigg app, go to Integrations and click Add integration.
  2. Select the Invoicing category and choose Airwallex.
  3. Fill in the credentials from step 1:
    • Client ID
    • API Key
    • API URL
    • Org ID
    • Account ID
  4. Click Connect.
That’s it — the integration shows as Active in your list of active integrations. Stigg automatically registers a webhook endpoint with Airwallex to receive payment status updates, so no manual webhook configuration is needed.

​
Removing the integration

To remove the integration, click on the dotted menu icon and select the Remove action. Confirm the action by clicking on the Remove button in the opened modal.
Removing the integration doesn’t affect already-collected payments or issued invoices, but new checkouts and payment-method updates can no longer be routed to Airwallex until it’s reconnected.