Enter only the fields the provider requires
Merchant Client ID, write-only API key, Live/Test mode and automatically provisioned exact webhook.
- Selected business profile
- Explicit live or test mode
- Write-only secret editing
Payment integration
Connect Airwallex without treating checkout as proof
Connect an Airwallex merchant directly to Invoice Crowd for hosted invoice checkout and verified consent-based recurring payment support.
- Status: Active hosted checkout
- Verified against application docs
- Provider terms still apply
Last updated:
Configuration to settlement
How Airwallex fits the Invoice Crowd payment boundary
Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.
Connect the merchant account
Credentials and mode stay tied to the selected business.
Confirm provider eligibility before rollout
Airwallex controls merchant onboarding, supported markets/currencies, account features and fees.
- Merchant country and account
- Invoice and settlement currency
- Provider fees and review
Understand the customer path
Availability is evaluated before a customer enters checkout.
Use the supported one-time flow
Hosted Payment Page uses tenant-owned credentials and settles only after an authenticated exact-account PaymentIntent read in SUCCEEDED state.
- Server-owned amount
- Bound invoice allocation
- Provider-controlled payment step
Read the recurring-payment boundary separately
Saved PaymentConsent support exists for scheduled merchant-initiated charges, but the bounded recurring scheduler is disabled by default until rollout gates pass.
- One-time and recurring differ
- Existing bindings may be compatibility-only
- Retired creators stay unavailable
Verify before recording money
The final local state follows provider evidence, not the browser.
Match the commercial record exactly
Signed webhook or return-triggered provider re-read, account and request binding, allocation, amount, currency, SUCCEEDED state and verified consent where reused.
- Merchant account and mode
- Allocation, amount and currency
- Successful provider state
Keep the current limitation visible
No platform connected account is created. Scheduled charging must remain disabled until production migration, sandbox connection and rollout checks are complete.
- No inferred settlement
- Pending stays pending
- Mismatch fails closed
Integration facts
What to verify before using Airwallex
The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.
-
Availability
Active hosted checkout
-
One-time payment
Hosted Payment Page uses tenant-owned credentials and settles only after an authenticated exact-account PaymentIntent read in SUCCEEDED state.
-
Recurring payments
Saved PaymentConsent support exists for scheduled merchant-initiated charges, but the bounded recurring scheduler is disabled by default until rollout gates pass.
-
Merchant setup
Merchant Client ID, write-only API key, Live/Test mode and automatically provisioned exact webhook.
-
Settlement evidence
Signed webhook or return-triggered provider re-read, account and request binding, allocation, amount, currency, SUCCEEDED state and verified consent where reused.
-
Regional fit
Airwallex controls merchant onboarding, supported markets/currencies, account features and fees.
-
Current boundary
No platform connected account is created. Scheduled charging must remain disabled until production migration, sandbox connection and rollout checks are complete.
-
Invoice data
Amount, currency and allocation are derived from the current server-side invoice state.
-
Customer result
A provider screen or browser return is a locator, not sufficient settlement proof.
-
Retries
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
-
Provider fees
Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.
-
Alternative gateways
Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.
Questions
Airwallex and Invoice Crowd, answered
Is the Airwallex integration currently available in Invoice Crowd?
Current status: Active hosted checkout. Hosted Payment Page uses tenant-owned credentials and settles only after an authenticated exact-account PaymentIntent read in SUCCEEDED state.
What do I need to connect Airwallex?
Merchant Client ID, write-only API key, Live/Test mode and automatically provisioned exact webhook. Airwallex controls merchant onboarding, supported markets/currencies, account features and fees.
How does Airwallex one-time checkout work?
Hosted Payment Page uses tenant-owned credentials and settles only after an authenticated exact-account PaymentIntent read in SUCCEEDED state.
Does Airwallex support recurring payments in Invoice Crowd?
Saved PaymentConsent support exists for scheduled merchant-initiated charges, but the bounded recurring scheduler is disabled by default until rollout gates pass.
How does Invoice Crowd decide that a payment succeeded?
Signed webhook or return-triggered provider re-read, account and request binding, allocation, amount, currency, SUCCEEDED state and verified consent where reused. A browser return or posted status alone cannot settle the invoice.
Are gateway fees included in Invoice Crowd pricing?
No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.
Test Airwallex with a representative invoice
Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.
- No browser-only settlement
- Provider terms apply
- Current status is visible