Licensing topology for cross-border embedded finance.

Partner-first, EU EMI, regional PI — when each makes sense.

The licensing decision is a product decision

Every fintech that crosses a border faces the same question: do we operate under the home country license with passporting, partner with a locally-licensed entity, or obtain a new license in the target market? The answer depends on the product, the volume, the regulator relationship, and the time horizon.

Coreal's recommendation for Wave 1 of a new market is almost always: partner first. Use an existing licensed entity — a local bank, a payment institution, an existing EMI — to get to market in 90 days. Prove the product. Build the regulator relationship. Then, if the market justifies it, obtain own licenses at Wave 2 or Wave 3.

Partner-first: the mechanics

Under a partner-first structure, the licensed entity is the principal. Coreal is the technology provider. The telco is the distribution channel. The customer agreement is with the licensed entity. The branded product is the telco's. The ledger, the BPM, and the compliance controls are Coreal's.

The key contractual elements: a white-label agreement between the licensed entity and the product entity (the JV), a technology services agreement between the JV and Coreal, and a distribution agreement between the JV and the telco. Each agreement must be reviewed by the licensed entity's regulator — typically as a material outsourcing notification.

When EU EMI is the right structure

An EU Electronic Money Institution license is the right structure when: the product operates in multiple EU markets, the volume justifies the compliance overhead, and the business needs direct control over the customer relationship rather than sharing it with a partner bank.

The EMI license enables IBAN issuance, account holding, and SEPA access directly. It does not enable credit. For credit products, you need a separate credit institution license or a partnership with one. This is a common design error: building toward EMI and then discovering that your product roadmap requires credit functionality.