Schedule a demo

Pick a time with our team. The scheduler is provided by Calendly and sets its own cookies.

Prefer email? support@coriunder.com

We use your details to arrange your demo. Read our Privacy Policy.

The Package

Eight interfaces. All of them yours.

Your operators, your merchants, your partners, your developers and your customers each get a front end built for them. Every one of them carries your brand, your colours and your domain, and none of them mentions us.

Your package8 front endsOne platformMentions of us: 0
Admin
The operator console. Merchants, terminals, transactions, balances and settlements, scoped by role.
MerchantsTransactionsSettlementsBalancesRisk
AcmeLive
LumenLive
NorthwindIn review
admin.yourbrand.com
Merchants
The portal merchants run themselves from: processing, settlements, statements and sub-users
StatementsReportsSub-usersAPI keys
Partners
Referred merchants, volume, commission
Own merchants only
Reports
Transactions to settlement, exportable
Devcenter
Method wizard, code generation, simulation
Simulated response · 200 OK
Webservices
API endpoints for every platform function
200+
Uiservices
Hosted payment and product pages
pay.yourbrand.com
Wallet
Balances, IBANs, cards, digital assets
IBANCardsCrypto

Build a payments brand, not a reseller page

We have been doing this long enough to know that every account you hold needs a different set of services. Each interface is tailored to what that audience has to get done, and the whole set is branded to you.

8

Branded interfaces

Your

Domain and colours

200+

API calls behind them

0

Mentions of us

Why it is built this way

One platform is not the same as one screen

A merchant does not want the operator console with most of it greyed out, and a partner should never see another partner. Separate front ends over one platform is how you give each audience the right surface without forking the product.

1Set the look per brandLogo, colours, templates
YB
yourbrand.com
Email and SMS templates · 6 locales
2Several brands on one instance
yourbrand.comLive
secondbrand.comLive
fourthbrand.euSetup
3Admins see only their brand
DM
dana@secondbrand.com
Admin · scope: secondbrand.com
Other brands hidden

Branded end to end

Colours, logo, domain and email templates are set per brand, and an admin user scoped to a brand sees only that brand’s data. You can host several brands on one instance and none of them will know about the others.

Brand configuration
1One platform, many audiences
Operator
Per profile
Merchant
Own
Partner
Introduced
Customer
Own
2Permissions decide what shows
TransactionsOwn merchants
StatementsOwn merchants
Risk rulesNot granted
3Partner sees their merchants only
Acme StoreIntroduced Mar 2026€84,210
Lumen TravelIntroduced Jun 2026€31,905

Scoped by who is looking

What each interface shows is decided by permission rather than by building a cut-down copy. A merchant sees their own activity, a partner sees the merchants they introduced, and an operator sees what their profile allows.

Roles and permissions
1Merchant needs a statementNo ticket needed
Statement · October 2026
Acme Store · merchant portal
Download
2Does the rest themselves
Reports and exportsSelf-serve
Add sub-userSelf-serve
ConfigurationSelf-serve
3Your support desk stays quiet
Portal actions · Oct
1,284
self-service actions

Self-service by design

The merchant and partner portals exist so your support desk is not the interface to your platform. The things people ask for most, statements, reports, sub-users and configuration, are things they can do themselves.

The merchant portal
1One figure on the platform
Settled this month · Acme Store
€97,350.44
2Read by every front end
€97,350.44Operator
€97,350.44Merchant
€97,350.44Reports
3Nothing to reconcile
All screens match
No support call about a different number
In sync

The same data underneath

Every front end reads the same platform, so a figure your merchant is looking at is the figure your operator sees. That removes most of the reason for a support call in the first place.

Reporting across audiences
Value added services

The back end behind what you sell

The interfaces are the front. These are the services your customers actually buy, running underneath them on the same platform.

Frequently asked questions

  • Are these really separate interfaces?

    Yes, eight of them, each built for a different audience rather than one console with sections hidden. They read the same platform underneath, so the numbers always agree.

  • How far does the branding go?

    Domain, logo, colour scheme, email and SMS templates, and the company details on documents. A merchant using your platform sees your brand throughout.

  • Can we run more than one brand?

    Yes. A single instance hosts unlimited parent companies, each with its own branding and configuration, and data is isolated between them.

  • Do our merchants get their own logins?

    Yes, and they can create sub-users with narrower permissions than their own, so their finance person and their developer do not need to share an account.

  • What is the Devcenter for?

    It is the documentation surface for whoever integrates, with a payment method wizard, code generation, signature validation and response simulation for testing.

  • Is the wallet front end included?

    It is one of the eight. Corporate and individual customers use it to see balances, IBANs, cards and digital assets in one account.

Still have a question?

Show your customers your brand, not ours.

We will walk you through each interface as the audience that uses it.

Interface availability depends on the modules your deployment runs. Talk to our team.