The Build vs. Buy Question
Every fintech or bank that reaches a point where its customers need cross-border payments faces the same question: do we build this capability internally or do we integrate with a provider that already has it?
The question sounds like a product decision. In reality, it is primarily a regulatory and balance-sheet decision. Cross-border payments require infrastructure that takes years and significant capital to build. The product layer is the easy part.
What Licensing Actually Requires
To move money across borders legally, you need to be a licensed entity in the jurisdictions where you originate and receive payments. The licensing requirements differ significantly by country. In the US, you need a money transmitter license in each state where you operate — 50 separate licenses, each with its own application, surety bond, and ongoing reporting obligation. In the UK, you need FCA authorization as a payment institution. In the EU, a PSD2 license in one member state allows passporting, but obtaining the initial license takes 12 to 18 months and requires demonstrating adequate capital, systems, and qualified management.
The licensing process is not simply a matter of filling out forms. Regulators require evidence of a compliance program, transaction monitoring systems, AML/CFT policies, business continuity plans, and audited financials. The upfront cost of obtaining major jurisdiction licenses is typically in the range of USD 500,000 to USD 2 million when legal, consulting, and compliance costs are included. Annual ongoing compliance costs add substantially to this.
For a fintech building a product in a single country, acquiring multiple international licenses to support payments in 20 or 30 corridors is rarely the right use of capital.
Banking Relationships Are the Real Constraint
Licenses authorize you to provide payment services. They do not give you access to the banking system in foreign countries. For that, you need correspondent banking relationships — agreements with banks in each country that will hold accounts for you and process payments on your behalf.
Establishing correspondent banking relationships is significantly harder than it used to be. Global banks have dramatically reduced the number of payment companies they will bank, particularly smaller or newer firms. The due diligence process for a new correspondent relationship takes 6 to 18 months, involves extensive documentation, and frequently results in rejection. Banks that do agree to work with payment companies often impose strict volume minimums, reporting requirements, and restrictions on certain corridors or client types.
Building a correspondent network that covers 40 or 50 countries takes 3 to 5 years in practice, even for well-capitalized firms with strong compliance programs.
Compliance Is a Continuous Overhead
AML/CFT compliance for cross-border payments is not a one-time setup. It requires ongoing transaction monitoring, case management, regulatory reporting, and adaptation to changing requirements across multiple jurisdictions. FATF guidelines change. Local regulators update their rules. Sanctions lists are updated daily.
A team capable of running a serious compliance program for a multi-corridor payments business typically requires dedicated compliance officers with regional expertise, a transaction monitoring system with rule-tuning capabilities, a legal and regulatory monitoring function, and relationships with local counsel in key jurisdictions. This is a fixed cost that runs regardless of volume.
What API Integration Covers
When a fintech integrates a cross-border payments provider via API, they are accessing a layer of infrastructure that sits below their product. The integration covers:
- Payment instruction: the fintech submits a payment instruction (beneficiary details, amount, currency, corridor) via API
- FX rate provisioning: the provider returns a quoted rate with an expiry window; the fintech displays this to its user
- Execution and settlement: the provider handles the actual movement of funds through its own banking relationships
- Status and reconciliation: the provider returns status updates at each stage of the payment lifecycle
The fintech's product manages the user experience. The provider manages the regulatory, banking, and operational layers underneath.
What White-Label Means in Practice
White-label integration goes further than API access. The provider's infrastructure operates invisibly under the fintech's brand. Users see the fintech's interface, the fintech's account names, and the fintech's pricing. The underlying payment rails, licenses, and banking relationships belong to the provider.
This structure works well for fintechs and banks that want to offer international payment capabilities without taking on the regulatory and banking infrastructure themselves. It is also appropriate for product areas where cross-border is a supporting feature rather than the core product — adding supplier payments to an accounting platform, or international transfers to a savings product.
Questions Worth Asking Before Committing
Before integrating any cross-border infrastructure provider, the key questions are: which jurisdictions are they licensed in, and are those the ones you need? Who are the banking partners underlying the service, and how stable are those relationships? What is the uptime and reliability track record? What does the API documentation and support look like for integration? How does the provider handle compliance obligations — and which ones remain with you?
The answers matter because a cross-border integration is not a standard SaaS switch that can be changed in two weeks. Once your product is built on a provider's rails, migrating is a significant undertaking. The selection decision is worth taking seriously.
