An eSIM provider gives international travelers mobile connectivity in more than 180 countries. Travelers activate local data plans without a physical SIM, which avoids roaming charges and keeps data costs predictable abroad.
Payment processing was a bottleneck for international growth. With customers in more than 45 countries and transactions typically between 10 and 20 euros, the company ran on multiple disconnected processors and gateways. Each new market meant weeks of development to connect new payment methods, which slowed expansion and added maintenance work.
The checkout had to support multiple currencies, hold PCI compliance, and match the branded experience that airline and travel partners required. The fragmented setup also caused friction inside partner airline checkout flows, raising abandonment at the payment step, and the company needed to store payment details securely for returning customers who top up their plans while traveling. Low transaction values meant processing cost mattered to margins.
Choosing Orchestra
The company moved to a single integration and selected Orchestra for its documentation, sandbox testing, and support for the markets it was entering. Integrating multiple payment methods through one JavaScript library replaced the disconnected processors, and the team also used Orchestra’s REST API for backend routing.
Global payment support
Orchestra let the company enter 10 new markets without the usual payment infrastructure work, and grew the payment methods it offers from 8 to more than 20. The methods customers expected in each market, from SEPA Direct Debit in Europe to local bank transfers in Southeast Asia, were already supported. Integration time for new markets dropped by about 50%.
Smarter transaction routing
Orchestra’s REST API routes each transaction to the most suitable processor by currency, size, and location. European transactions go to an EU processor for better approval rates; high-value transactions route to the lowest-cost gateway. This routing optimization reduced processing costs by about 15%.
How they integrated
The company uses Orchestra’s REST API for backend routing and transaction logic, and the JavaScript library for front-end payment forms and PCI compliance. The library handles the security requirements while the company keeps control of the payment page design, which removed its PCI compliance burden. Its work on international payment processing shaped how it set up routing.
What changed
Multi-currency support
Through one integration, the company now accepts more than 30 currencies, with each transaction routed to the most cost-effective processor for its currency and geography.
Saved cards for repeat top-ups
About 65% of customers buy again while traveling. Orchestra’s tokenization lets them top up their plans with one click instead of re-entering card details.
Fitting into airline checkout flows
Each airline and travel partner has its own checkout requirements. Orchestra’s integration options let the company build payment experiences that fit each partner’s booking system. Since the change, checkout abandonment across airline partnerships has fallen by about 20%, which helped the company sign 6 new travel partnerships in the past year.
Results
Monthly transactions have grown from about 8,000 to roughly 13,000, across more than 30 currencies, and the company has entered 10 new markets. It has since added a multi-currency wallet that lets travelers load funds in their home currency and spend in local currencies without conversion fees.
