Company overview

A digital marketing and advertising technology group operates several products across ad serving, traffic monetization, link building, and affiliate marketing. The group has separate legal entities in the United States, European Union, and United Kingdom, each with its own bank accounts and settlement requirements.

The challenge

Each legal entity had its own payment processor. The US entity processed through a US payment provider in USD. The EU entity used a European processor settling in EUR. The UK entity had a third relationship for GBP transactions.

This meant three separate integrations, three onboarding processes, three sets of API credentials, and three reconciliation workflows. When a customer in the US purchased services from the EU entity, the transaction routed through the European processor, resulting in lower approval rates and higher processing fees.

Adding a new payment method in one region had no effect on the others. When the EU entity added SEPA support, the integration was completely separate from the US card processing setup. Each regional expansion required its own implementation project.

The group needed a way to maintain separate legal entities and settlement currencies while processing payments through a single technical integration.

The solution

Orchestra sits between the group’s products and all three regional processors. The group configures which processor handles which entity and currency. Each product sends transactions to Orchestra’s API, and Orchestra sends them to the right processor based on that configuration.

A US customer paying the US entity gets routed to the US payment provider. A German customer paying the EU entity gets routed to the European processor with EUR settlement. A UK customer paying the UK entity goes through the UK payment provider in GBP. All three flows use the same API integration from the group’s side.

When the group negotiated a new UK processing relationship, switching was a configuration change in Orchestra, not a re-integration project. The stored tokens carried over because they live in Orchestra’s vault, not in any individual processor’s system.

Orchestra also handles the cases where customers cross regional boundaries. A US-issued card paying the EU entity can be processed through the US payment provider for better approval rates, with settlement to the EU entity’s bank account handled directly between the processor and the entity.

How it works

The group’s products embed Orchestra’s JavaScript library on their payment pages. The JS library handles card capture, 3D Secure verification where required, and sends the transaction to the configured processor for that entity. For server-to-server flows that don’t require 3DS (such as recurring charges using stored tokens), the products call Orchestra’s REST API directly.

Every transaction returns in a unified, single-format response structure regardless of which PSP processed it. This makes it straightforward for the group to log and track transactions across all three regions in their own systems.

Outcome

The group processes payments across three continents through one integration. New regional entities or processor relationships are configuration changes, not engineering projects. Cross-border transactions route through local payment providers where possible, and the finance team has consolidated reporting across all entities.