In development Planned launch: April 2027 · Services are not yet available
Let's talk
The Single Control platform

Four services.
One shared back-end.

The Single Control Plane combines Wallet, Onboarding, Compliance and License as a Service. They share transaction records through one back-end. You keep your brand and customer experience, with programme responsibilities agreed in advance.

Your branded wallet sends transaction data to Single Control. License, Onboarding, Wallet and Compliance as a Service share one back-end, where data is recorded before it reaches your systems through the API.
Your solution connects to four services through one shared back-end. Transaction data is recorded in Single Control before your systems access it through the API.
Wallet as a Service

A wallet under your brand.

Offer a white-label wallet that fits your product, with multiple currencies and assets managed through one back-end.

Your brand

One customer wallet

EURGBPOther agreed assets

Your customer sees balances and activity inside your product.

Shared back-end

Each transaction updates the relevant wallet record.

Balance records

Track value by customer, currency and asset.

API access

Bring recorded activity into your own systems for reconciliation.

Currencies and assets are agreed for each programme.

Onboarding as a Service

Get started with the right evidence.

Onboarding as a Service helps you prepare the information a review needs, with a named contact to guide the process.

A named contact throughout

Coordinates requests, explains progress and follows up on outstanding evidence.

Agree the scope

Define the product, customer groups and activities to be reviewed.

Prepare and review

Submit the relevant information. We identify specific gaps and help you address them.

Confirm the next step

Receive the decision and any remaining conditions before moving forward.

When information is missing, the request returns to your team with a clear explanation of what is needed.

Compliance as a Service

Compliance that considers your business.

Compliance as a Service combines transaction records with human review. We explain decisions promptly where permitted and consider new evidence.

Record the activity

Transaction data reaches Single Control and is stored in our back-end first.

Assess the activity

Apply the relevant controls using transaction records and customer context.

Within the agreed controls

Handle the activity under the programme rules.

Needs attention

A named contact requests evidence and explains the next step where permitted.

New evidence returns to the review. We reassess the decision where the rules allow. Mandatory restrictions remain in force.

Your systems access recorded transaction data through the API. Data access and permission to execute a payment are separate parts of the programme.

License as a Service

Define the regulatory responsibilities.

License as a Service gives eligible programmes an agreed regulatory arrangement, with documented roles and limits.

Programme agreement

One documented arrangement

Activities, markets and service limits define the scope.

Your business

Owns the brand and customer experience, and fulfils the responsibilities agreed for its role.

Responsibility matrix

Decision authority
Support ownership
Data access
Provider dependencies

Regulated entity

Retains responsibility for its regulated activities and the controls required by law.

The agreement establishes who does what. License as a Service provides a regulatory arrangement; the licence remains with the authorised entity.

How the compliance model works

Transactions come
to Single Control first.

Every transaction in a programme using our compliance service must reach Single Control and be stored in our back-end first. This gives the regulated entity the records it needs to carry out its duties.

Your systems can then access the records through our API. Transactions that bypass our back-end are outside the compliance service.

  1. Your programme

    Transactions are submitted to Single Control through the agreed integration.

  2. Single Control first

    Each transaction is stored in our back-end and included in the relevant compliance processes.

  3. Your connected systems

    The API makes each transaction available to your own systems under the agreed data access model.

This diagram describes the transaction-data sequence, not a settlement guarantee. Funds movement, decision timing, access rights and retention are specified for each programme before launch.

A partnership you can evaluate

Review the costs
before you commit.

During scoping, we identify programme costs, responsibilities and external providers so you can assess the business case.

ImplementationScoping, configuration and integration work.

Platform and usageA programme minimum and usage-based components.

External dependenciesIdentified banking, payment network, FX and specialist-provider requirements.

Migration and exitAgreed exports, responsibilities and constraints on changing providers.

No prices, performance measures or delivery commitments are binding until agreed.
Read the regulatory scope
Contact Single Control

Discuss your programme with us.

Tell us what your business needs from a payment provider. Investors can contact us to discuss the market and business model.

Let's talk