Partner programme
One more thing your terminals can accept
A terminal that accepts closed-loop balances as well as cards is worth more to the merchant buying it, and the flow does not touch the certified payment application at all — so adding it is a software decision rather than a recertification project.
Updated
At a glance
- Requirement
- The terminal can display a QR on screen
- Integration
- QR flow: none. Terminal SDK: a vendor build
- Certification
- Not required — the flow sits outside the payment application
- Installed base
- Works on terminals already in the field
Updated
Two depths of integration
The QR flow needs nothing from the terminal beyond drawing a code on screen. It works on hardware already installed in the field, which makes it the fastest way to put the capability in front of merchants.
The Terminal SDK is for vendors who want the flow inside their own application: amount entry, code display and result handling in the native interface, with the ledger call handled for them.
Either way the payment application is untouched, so nothing about the existing certification changes.
- Merchants keep the same terminal, the same till integration and the same receipts.
- The flow adds no step for the cashier beyond the amount already being entered.
- A vendor can ship it to the installed base as a software update rather than a hardware cycle.
Working with us
- 01
Confirm the display path
Most modern PAX, Verifone and Ingenico models already qualify.
- 02
Choose QR or SDK
QR to move fast on the installed base; SDK for a native experience.
- 03
Build against the sandbox
With documentation and our engineers available throughout.
- 04
Ship to the field
As a software update, with no recertification in the way.
Details
- Supported vendors
- PAX, Verifone, Ingenico and others
- Fallback
- Staff phone, where a merchant has no terminal
- Speed
- About 5 seconds end to end
- Offline
- Not supported for payment — balances verify live
- Branding
- White-label available on the merchant-facing surfaces
- Commercials
- Per-terminal fee, revenue share or hybrid
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.
Add closed-loop to the terminals you ship
A free 30-day pilot, configured and supported by our team.