Partner programme
Closed-loop as a service, across a whole network
A network does not want a payment product; it wants something its members can each run as their own. Multi-tenant administration, per-tenant branding and separate settlement make one deployment serve many issuers without any of them seeing each other.
Updated
At a glance
- Structure
- One master account, many tenants beneath
- Branding
- Per tenant, not only per network
- Settlement
- Separate per tenant and per merchant
- Reporting
- Per tenant, plus a consolidated view
Updated
What multi-tenant has to mean here
Tenancy in a payment platform is not a filter on a dashboard. Each tenant needs its own balances, its own merchants, its own limits and its own settlement, and no query from one tenant may ever reach another's data.
Above that, the network needs a consolidated view — total volume, active cards, transaction mix — without that view becoming a way around the separation underneath.
Branding is per tenant too: a member issuing cards under its own name should not be handing its customers a card with the network's logo on it, unless that is the design.
- Each tenant administers its own merchants, cards and rules.
- Settlement runs per tenant and per merchant, never pooled.
- The network sees aggregate reporting without cross-tenant data access.
How a network deploys it
- 01
Model the tenancy
Which members are tenants, and what the network sees across them.
- 02
Set the branding policy
Network-wide, per tenant, or a mix.
- 03
Integrate once
API and Terminal SDK at the network level, inherited by every tenant.
- 04
Onboard members
Each as a tenant, with its own merchants and its own programme.
Details
- Tenants
- Unlimited under one master account
- Data separation
- Enforced at the ledger, not the interface
- Per-tenant limits
- Cards, merchants, programmes and spending rules
- Consolidated view
- Aggregate only, by design
- Onboarding
- By API, for members at volume
- Commercials
- Network-level agreement, per-tenant pricing
Questions about this
How does 7Konto embed into a PSP checkout?
7Konto appears as a new payment method inside your existing checkout, next to the cards and wallets you already offer. Every merchant on that gateway sees “Pay with 7Konto” without changing a line on their own site: we integrate once with the gateway, and the whole portfolio has it.
What data stays with us, and what goes to Visa or Mastercard?
All of it stays, and none of it goes. Closed-loop transaction data belongs to you and the merchant, nothing routes through the card schemes, and interchange does not apply. You get full attribution — who spent what, where and when — across POS and online in one dataset.
Do I need an EMI or banking licence?
Not for the usual closed-loop cases: gift cards, employee benefit accounts, hotel guest accounts, event payments. They fall under the limited-network exemption in PSD2 and comparable frameworks elsewhere. Where a programme approaches the edge of that exemption — a very broad merchant network, for instance — we say so before it is built, not after.
Is this the Starbucks model?
The same economics, without the app. Starbucks built a custom application customers had to install, and holds a very large prepaid float as a result. 7Konto delivers the closed-loop side of that through Apple Wallet and Google Wallet, so there is no app to develop and no install step to lose people at — and through PSP embedding it extends to a whole merchant portfolio rather than one brand.
Who can partner with 7Konto?
Banks, EMIs, acquirers, payment service providers, processors, POS terminal vendors and payment networks. Each has its own programme: you extend what you offer merchants with closed-loop capability under your own brand, offline and online.
Do you provide an API as well as a ready widget?
Three paths. The REST API and Terminal SDK for partners with engineering who want full control. The checkout widget as a ready JavaScript embed with four one-click auth methods. And PSP checkout embedding, where 7Konto becomes a native method inside your gateway and merchants integrate nothing at all.
Talk to us about your network
A free 30-day pilot, configured and supported by our team.