Home / Companies / Airwallex / Blog / Post Details
Content Deep Dive

My 2025 reflections: Ten years to reach the starting line

Blog post from Airwallex

Post Details
Company
Date Published
Author
Jack Zhang
Word Count
3,329
Company Posts That Month
10
Language
English
Hacker News Points
-
Post removed?
No
Summary

Airwallex’s 2025 year-end reflection presents the company’s effort to build an integrated global financial platform that combines payment acceptance, multi-currency accounts, foreign exchange, payouts, corporate cards, expense management, procurement, billing, and embedded-finance APIs. It reports reaching US$1 billion in annual recurring revenue in October 2025, representing 90% year-on-year growth, serving more than 200,000 customers, achieving EBITDA profitability in the fourth quarter, and receiving an US$8 billion valuation in its Series G funding round. The company says its network now processes more than US$266 billion annually, routes over 95% of transactions through local payment rails in 127 countries, supports transfers to more than 200 countries, and saved customers an estimated US$1.2 billion in 2025 through lower-cost payment routing and foreign-exchange features. Product expansion included broader account, payout, currency-holding, card, payment-method, procurement, recurring-billing, and developer-platform capabilities, alongside AI tools intended to improve onboarding, payment optimization, reconciliation, and automated financial workflows. Airwallex also outlined plans to enter more than 10 markets in 2026, invest US$1 billion in US expansion and over US$500 million in the UK, and pursue a long-term target of one million customers and US$10 billion in annual recurring revenue.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Real-time 8 6,858 1,506 281 +0%
AI Agents 3 4,743 1,017 258 -5%
Vector Search 1 2,556 510 164 +22%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.