Service status communicates whether checkout, transfers, FX conversion, card authorisations, or APIs are degraded.
Global finance teams should know which dependency failed: a card network, a local rail, an FX engine, or an API edge. The remediation differs in each case.
This information portal does not publish live Airwallex uptime meters or incident timelines.
Operationally mature companies subscribe to status alerts, define customer messaging templates, and decide when to pause payouts during incidents.
If payments fail, check method-specific behaviour and error codes before assuming a full platform outage.
Key points
- Status pages separate full outages from partial degradations
- Identify whether cards, rails, FX, or APIs are impacted
- This portal is not a live status monitor
- Prepare customer messaging for payment or payout delays