For merchants · banks · EMIs · PSPs · processors

Closed-loop payments on rails you already own

One balance in Apple Wallet and Google Wallet. Spent at the POS terminal you already run, through a checkout widget on your merchant's site, or as a payment method inside your PSP gateway. No customer app. No EMI licence. Weeks, not months.

  • No app for customers
  • No new hardware
  • 0% interchange

Why 7Konto exists

Closed-loop economics are worth building, and nobody wants to build them

A merchant who holds prepaid balances keeps the float, pays no interchange and sees every transaction. That is the whole reason chains build their own payment products. What stops everyone else is the ledger, the wallet integration, the terminal work and the compliance reading — twelve months of it, before a single card exists.

So we made it the part you switch on

7Konto is the ledger, the Wallet issuance and the three integration paths, already built and already in production. The card lands in a wallet the customer already has, and the payment runs on the terminal the merchant already has. Configuration and go-live take three to five business days.

Zero friction, at every layer

Every closed-loop system tries to add something — an app, a device, a rebuild. These are the four we removed.

No app for customers

Cards issue directly to Apple Wallet and Google Wallet. The customer scans a QR code, taps “Add to Wallet”, and is done in about ten seconds. No download, no account, no registration form to abandon.

No new hardware

It runs on the POS terminals already on your counters — PAX, Verifone, Ingenico and others. Where there is no terminal, staff run the same flow from an ordinary phone. Nothing dedicated to buy, deploy or maintain.

No site changes

Online works the same way. Embed the checkout widget on a merchant site with one line of JavaScript, or embed 7Konto into a PSP gateway once and every merchant on it gets the payment method with no work at all.

No interchange

Closed-loop accounts settle internally. Nothing routes through Visa or Mastercard, so no scheme fees apply and 100% of the transaction data stays with you and the merchant. Your economics, your rules.

The platform at a glance

Eight things that are true of every deployment, and four that depend on the integration path you pick.

True of every deployment

Product category
Closed-loop payment platform with its own ledger
Customer app
None — a pass in Apple Wallet or Google Wallet
Time to get a card
About 10 seconds from scanning a QR code
Merchant hardware
The POS terminals already deployed, or any phone
Interchange
0% — the transaction never reaches a card scheme
Transaction data
100% stays with you and the merchant
Licence needed
None for the usual programmes: PSD2 limited-network exemption
Time to go live
3–5 business days for configuration and launch

Depends on the path

POS integration
QR on any terminal that can draw one; Terminal SDK where deeper
Online widget
One line of JavaScript, four one-click auth methods
PSP embedding
One gateway integration covers the whole merchant portfolio
White-label
Your domain, logo and palette on cards, admin and widget

One balance

Three ways to pay, one account behind them

At the counter the cashier enters an amount and the terminal shows a QR the customer scans with their own phone. Online the customer picks 7Konto at checkout — on the merchant's site or inside your PSP gateway. Same balance, same admin panel, same transaction ledger. The channel is a surface, not a separate product.

One admin panel

Balances, cards, merchants and limits in one place, whether the money moved at a till or in a browser.

One reporting stream

Offline and online volume in the same dataset, separable by channel when you want it and joined when you don't.

Proven at scale

The Wallet issuance and ledger underneath have been running in production for years through our sister brand 7Stamp.

Build it, or switch it on

Every business that wants closed-loop payments faces the same fork, and the cost of the two branches is not close.

Build the stack yourself

A ledger that balances, Apple and Google Wallet certifications, terminal software on three vendors' hardware, a checkout flow, an admin panel, and a compliance opinion on whether any of it needs a licence. Six to twelve months and a team, before the first card is issued — and the result is a payment system you now have to operate.

Run it on a platform that exists

The ledger, the wallet issuance, the terminal flow, the widget and the PSP embedding are already built and already carrying transactions. You configure the programme — cards, balances, limits, merchants — and go live in three to five business days. A free 30-day pilot proves it before anyone signs anything.

Three integration paths

  1. 01 Path 1

    POS terminals

    On your existing PAX, Verifone or Ingenico fleet. The cashier enters the amount, the terminal displays a QR, the customer scans it with their own phone. Where there is no terminal, the same flow runs from a staff phone.

    Customer does
    Scans a QR with the phone camera
    You do
    Nothing to install on the counter
  2. 02 Path 2

    Checkout widget

    A ready widget for merchant websites, added with a one-line JavaScript embed. Four one-click ways to authenticate: the Wallet card itself, a phone by SMS or Flash-call, an email one-time code, or a corporate ID for B2B and B2E users.

    Customer does
    Picks 7Konto, authenticates in one tap
    You do
    Paste one line into the checkout page
  3. 03 Path 3

    Embedded in a PSP gateway

    7Konto appears as a new payment method inside your existing checkout. Merchants change nothing on their sites — “Pay with 7Konto” shows up next to the cards and wallets you already offer, for every merchant on the gateway.

    Customer does
    Sees a familiar checkout with one more option
    You do
    Integrate the gateway once, for the whole portfolio
  4. 04 Behind all three

    Smart Account Detection

    When the customer authenticates, the platform works out which account they hold — a personal gift or loyalty balance, or a corporate credit line or employee allowance — and applies that account's rules, limits and merchant restrictions to the payment.

    Customer does
    Nothing to choose or configure
    You do
    Set the rules once, per programme

What closed-loop actually pays you

The advantages are not marketing positions. They follow from one fact: the transaction never leaves your ecosystem.

100% of the data

Transaction data stays with you and the merchant. Not with Visa, not with Mastercard, not with a processor in between.

In practiceFull basket-level attribution, POS and online in one dataset.

0% interchange

No card scheme sits in the flow, so no scheme fee applies. The economics of the programme are yours to set.

In practiceNo per-transaction fee to a network, at any volume.

No EMI licence

PSD2's limited-network exemption covers closed-loop programmes, and comparable frameworks apply elsewhere.

In practiceGift cards, benefits, guest accounts and event payments all fit.

Float that stays

Prepaid balances sit in your programme until they are spent, which is the same mechanic a chain builds its own app to get.

In practiceTop-up now, redeem across the whole network later.

Products that sell themselves

Five closed-loop stories with real demand

These five have been asked for in every market we have served. High demand, quick to explain, fast to deploy — offline and online.

Most asked for

Gift certificates for chains

Digital gift cards in Apple and Google Wallet, sold online or in store, redeemable across every location and in the checkout widget.

Gift certificates
B2B2E

Fuel cards

Fuel networks, transport companies and drivers. Individual Wallet cards with per-driver limits and reservation of funds before dispensing.

B2B fuel cards
Closed territory

Corporate meals and campus

Factories, offices, hospitals and universities: one pool of users, several merchants on site, rules set by the employer.

Closed-loop campus
Online

E-commerce and PSP checkout

The same balances online — a widget on merchant sites, or embedded straight into a PSP gateway as a payment method.

Online and e-commerce

Every solution in full

Three parties, one platform

It is not only customer cards. It is B2B2E.

A merchant on 7Konto — a fuel network, say — can hand the platform to its own business customers, such as transport companies. Those businesses then enrol their own employees, the drivers, each with an individual Wallet card and per-user limits. The same pattern carries corporate meals, mobility and employee benefits: any case where a business has to distribute controlled spending to its people.

  1. 01 The merchant provides the platform to its business customers.
  2. 02 The business runs an internal programme for its employees.
  3. 03 The employees hold Wallet cards with individual limits and rules.

Thirty days, and we do the setup

Not a trial where you work it out alone. A real pilot, configured and supported by our team, with up to 10,000 operations included.

  • The platform configured end to end for your specific business.
  • Staff trained over a video call, so day one is not a scramble.
  • Help onboarding your first real customers onto real cards.
  • No credit card, no obligation — if it works you continue, if not you walk away.

Compared with the alternatives

Three ways to get closed-loop payments running, and what each one actually costs you.

Processes payments

Wallet-pass tools
No — passes only
Build it in-house
Yes, once built
7Konto
Yes, with its own ledger

Time to live

Wallet-pass tools
Days, but incomplete
Build it in-house
6–12 months
7Konto
3–5 business days

Customer installs an app

Wallet-pass tools
No
Build it in-house
Usually yes
7Konto
No

Works on existing terminals

Wallet-pass tools
Not applicable
Build it in-house
You write it
7Konto
PAX, Verifone, Ingenico and others

Online checkout

Wallet-pass tools
No
Build it in-house
You build it
7Konto
Widget and PSP embedding included

B2B2E accounts and limits

Wallet-pass tools
No
Build it in-house
You build it
7Konto
Built in from the Scale tier

Who carries compliance

Wallet-pass tools
You
Build it in-house
You, from scratch
7Konto
Structured with you, inside the exemption

Why the difference holds

A pass is not a payment

PassKit-style tools distribute Wallet passes. They have no ledger, so a balance on them is a number printed on a card rather than money that can be charged.

The hard part is the middle

Issuance and a checkout screen are the visible ends. The ledger, the reconciliation and the limit engine between them are what takes the year.

The terminals already exist

Any deployment that needs new hardware on every counter is priced and paced by that hardware, not by the software.

Flat monthly pricing, by plan

A plan covers a transaction allowance and a number of locations. Issuing cards to Wallet is always free, however many you create.

Network · most chosen

$149

Per month. 10,000 transactions, up to 5 locations, gift card module, online checkout widget, REST API and webhooks.

See pricing
Every plan

$49 – custom

Solo at $49, Network at $149, Scale at $349 with B2B2E accounts, and Enterprise quoted. Every new business starts with the free 30-day pilot.

Start free pilot

See all four plans and what counts as a transaction

Updated

Terms

Four words used precisely

Payments vocabulary is overloaded, and two of these decide which regulations apply to a programme. This is what they mean on this site.

Closed-loop payment
A payment system where funds can only be spent within a defined ecosystem — one merchant, a group of related merchants, or a specific programme. Because the transaction never leaves that ecosystem, no card scheme sits in the middle of it.
Wallet card
A digital pass stored in Apple Wallet or Google Wallet that represents value (a balance, a prepaid amount) or access rights (tickets, membership). It is added from a QR code in about ten seconds and needs no app installed.
Commercial account
A business-controlled prepaid or spending account, distributed to the employees or customers of the account owner, usually with spending limits. It is what makes a fuel card, a meal allowance or a benefits budget work.
B2B2E
Business-to-Business-to-Employee: a distribution model where a platform serves a business, and that business in turn serves its own employees or end users through prepaid accounts. Three parties, one platform — the pattern behind fuel cards, corporate meals and employee benefits.

Read the full glossary

The questions we get asked first

What is a closed-loop payment platform?

It lets you issue and process payments inside your own ecosystem — gift cards, prepaid balances, employee accounts — without routing every transaction through Visa, Mastercard or a bank. The funds stay in your system, so the fees, the data and the customer experience are yours to set.

Do my customers need to install an app?

No. Cards issue straight to Apple Wallet or Google Wallet, which are already on every phone. The customer scans a QR code with the camera, taps “Add to Wallet”, and the card is there in about ten seconds. No download, no account, no registration form.

Does it work with my existing POS terminal?

Yes. The cashier enters the amount on the terminal you already run, the terminal shows a QR code, and the customer scans it with their own phone. That works on any terminal that can draw a QR on screen, which covers modern PAX, Verifone and Ingenico fleets. If there is no terminal at all, staff can run the same flow from a phone.

Do you handle online payments too, or just POS?

Both, on one balance. There is a checkout widget for merchant sites and a direct embedding into PSP gateways as a payment method. One admin panel, one transaction ledger, one reporting stream — offline and online together.

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.

How does the free 30-day pilot work?

Thirty days of full platform access with up to 10,000 operations. Our team configures the platform for your business, trains your staff over a video call and helps you onboard the first customers. No credit card, no obligation. If it works you pick a plan; if not, you walk away.

How much does 7Konto cost?

Solo is $49 a month for one location with 2,500 transactions. Network is $149 for up to five locations, 10,000 transactions, the gift card module and the online checkout widget. Scale is $349 for up to twenty locations, 30,000 transactions, B2B2E accounts and smart account detection. Enterprise is quoted. Every new business starts with the free pilot.

How is 7Konto different from PassKit or Badge?

Those are Wallet pass products: they distribute passes, they do not process payments. 7Konto is a closed-loop payment platform with a ledger, transaction processing, POS integration, an online checkout widget and PSP embedding. A card issued here carries a real balance that is charged in real time.

Which industries does 7Konto support?

Retail chains, restaurants and HORECA, hotels, corporate meal programmes, employee benefits and fuel cards, cashless events, coalition loyalty, property management, campus environments, and e-commerce merchants who want closed-loop alongside their PSP.

Ready to launch closed-loop payments?

Start free pilot

A free 30-day pilot. We handle the setup and the training — you watch it work.

We use analytics cookies to see how the site is used. Nothing is set until you choose, and rejecting changes nothing about how the site works. Read the cookie policy