Wallet card
The same card used at the counter, scanned or selected — the shortest path for an existing customer.
Capability
The same balance, in the merchant's own checkout
A ready widget that adds “Pay with 7Konto” to any checkout page with a single line of JavaScript. The customer authenticates in one click — their Wallet card, their phone, an email code, or a corporate ID — and the balance they use in store is debited online.
Updated
At a glance
- Integration
- One-line JavaScript embed
- Authentication
- Wallet card, phone, email code, corporate ID
- Styling
- Style tokens, or full API control
- Availability
- From the Network plan
Updated
Adding it to a checkout
- 01
Paste one line
A script tag on the checkout page, with the merchant's key.
- 02
Pick the auth methods
Enable the ones that suit the merchant's customers; the widget chooses among them at runtime.
- 03
Match the brand
Style tokens set colours, fonts, corner radius and button styles to the merchant's palette or yours.
- 04
Take payments
The balance is debited and the result returns to the merchant's order flow like any other method.
Four ways in, no account to create
The hardest part of an online closed-loop payment is proving who is paying without making them register. The widget offers four routes and picks the sensible default from the account type, so a consumer and a corporate user each get the shortest path that works for them.
Phone or email
An SMS one-time code, an instant Flash-call, or a code by email. No password, nothing to remember.
Corporate ID
For B2B and B2E users, who should never be asked to create a consumer account to spend an allowance.
What it does and does not touch
- Card data
- None — it moves closed-loop balance, so PCI DSS scope is unchanged
- Order flow
- Returns success or failure like any payment method
- Refunds
- Issued back to the same balance from the admin panel or API
- B2B routing
- Corporate accounts carry their own limits and merchant rules
- Reporting
- Online volume lands in the same ledger as POS
- Deep control
- The widget can be replaced with direct API calls
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.
What authentication methods does the widget support?
Four, all one click: the Wallet card itself, a phone number by SMS code or instant Flash-call, an email one-time code, and a corporate ID for B2B and B2E users who should never see a consumer signup. A merchant or PSP chooses which to enable, and the widget selects by account type when checkout starts.
Can the widget be styled to our brand?
Yes. It accepts style tokens — colours, fonts, corner radius, button styles — so it can carry your palette or the merchant's. For full control the widget can be replaced with direct API calls into your own checkout interface.
What about PCI DSS on the online flow?
The online flow never touches card numbers — it moves balance between closed-loop accounts, which is a different regulatory regime from open-loop card processing. PCI DSS applies to card data, which stays your PSP's responsibility; 7Konto sits beside it as a separate payment method.
Add closed-loop payment to a checkout
A free 30-day pilot, configured and supported by our team.