Entering a second market is not held up by connecting a provider but by the chart of accounts, the reporting calendar and the data protection regime. Here is what to prepare and in what order.
countries with a ready chart of accounts
jurisdictions in the data protection regime
currencies for books and settlement
The payment channel is the easy part. What comes after it is what costs.
Bookkeeping in the second country follows local rules: its own account structure, its own disclosure requirements, its own mapping to international reporting standards.
The regulator expects reports in its format and on its calendar. The first mandatory filing arrives sooner than it seems, and it does not move.
Where customer data is stored, how long you have to answer a data subject, whom to notify within how many hours after a breach — the answers differ country by country.
Not "multi-jurisdiction support" in the abstract, but the three specific things that usually eat a quarter.
A ready account structure with local requirements and a mapping to international reporting standards. Your own accounts are added on top of it, not instead of it.
Report template, delivery channel and filing schedule. The dry run happens before the first mandatory date rather than the night before it.
Response deadlines for data subject requests, the notification procedure for an incident, and a decision log — under the rules of that specific jurisdiction.
The most expensive mistake is starting with the payment channel. A provider connects in weeks, after which the operator discovers that transactions are flowing but there is nothing to book them into and nothing to report them with. The right order is the reverse: chart of accounts and reporting calendar first, then the data regime, and only then acceptance. That way the very first live transaction lands in the correct books.
The second question is the legal form of your presence. Own entity, branch, or operating through a licensed partner — this determines both the reporting set and whose name appears on the customer contract. The decision is made once and is expensive to change, so it deserves a conversation with a lawyer before the first terminal is configured.
And about timing. A quarter is a realistic target for a country where you already have a legal presence and a clear regulator. If you need your own licence, the timeline is set by the regulator rather than by the platform, and planning it against our schedule is pointless. An honest conversation about that at the start saves more than any automation.
Five setup wizards. The operator runs them alone — no development needed.
Country, chart of accounts, mapping to reporting standards, and your own accounts on top of the base structure.
Report template, delivery channel, filing schedule and a dry run before the first mandatory date.
Response deadlines for data subjects, the regulator notification procedure for an incident, and a log of the decisions taken.
The country's local payment rail: participant credentials, wallet and directional terminal, limits and operating window, and a trial operation before going live.
Indirect tax rates broken down by region, withholding at source by recipient type, ledger accounts and a trial calculation on a real payout.
Run the jurisdiction wizard before connecting a provider: a chart of accounts created after transactions have started means re-posting entries, and that is work nobody plans for.
Register and go through the jurisdiction wizard yourself: chart of accounts, reporting calendar, data regime. Your own licence is a separate conversation — its timeline is set by the regulator, not the platform.
Get started