Solution
The balance they use in store, used online
A closed-loop programme that only works at a counter is half a programme. The same card, the same balance and the same rules work in the merchant's own checkout — added with one line of JavaScript, or appearing automatically through a PSP gateway.
Updated
At a glance
- Integration
- Widget embed, PSP gateway, or REST API
- Authentication
- Wallet card, phone, email code, corporate ID
- Account routing
- B2C and B2B/B2E handled automatically
- Plan
- From Network; account detection from Scale
Updated
Three ways a merchant gets it
Through a PSP that has already integrated 7Konto, the method simply appears in the checkout with no work at all on the merchant's side.
On their own site, a single JavaScript embed puts “Pay with 7Konto” in the payment list, styled to their palette.
For a bespoke checkout, the REST API exposes the same authorisation, capture and refund calls the widget uses.
- No card data passes through the flow, so PCI DSS scope does not change.
- Refunds return to the same balance, from the admin panel or the API.
- Online and POS volume land in one ledger and one reporting stream.
What the customer does
- 01
Picks 7Konto at checkout
Next to the cards and wallets the merchant already offers.
- 02
Signs in with one click
Their Wallet card, a phone code, an email code, or a corporate ID.
- 03
The right account is chosen
Smart Account Detection applies the limits and merchant rules of whichever balance is paying.
- 04
The order completes
Success returns to the merchant's order flow like any other payment method.
Details
- Embed size
- One script tag
- Styling
- Style tokens, or full API control
- Guest checkout
- No account creation at any point
- Corporate users
- Sign in by corporate ID, never a consumer signup
- Reporting
- Channel-separable inside one dataset
- Availability
- Network plan and above
Questions about this
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 the online checkout widget work?
The merchant adds it to the checkout page with a one-line JavaScript embed. When a customer picks “Pay with 7Konto” they authenticate in one of four ways — scan their Wallet card, take an SMS code or Flash-call, enter an email one-time code, or sign in with a corporate ID — and the widget debits the balance and returns success to the merchant.
Do merchants have to change their websites?
It depends on the path. Through a PSP that has integrated 7Konto: nothing at all — the method simply appears. With the standalone widget: one line of JavaScript. For a bespoke checkout: the REST API.
How does 7Konto know whether a customer is B2C or B2B/B2E?
Smart Account Detection. When the customer authenticates, the platform routes them to the right account type — personal gift and loyalty balances for consumers, corporate credit lines or employee allowances for B2B and B2E users — and applies that account's rules, limits and merchant restrictions.
Can a merchant use online only, without a POS?
Yes, and the reverse too. Online-only works through the widget or your gateway with no terminal anywhere; POS-only works for retail with no online presence. Most merchants end up using both, but nothing requires it.
Add closed-loop payment to an online checkout
A free 30-day pilot, configured and supported by our team.