Forty-six questions, answered

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.

• How it works

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.

• Cards in Apple & Google Wallet

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.

• Payment at the POS terminal

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.

• Online checkout widget

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.

• Embedding in a PSP gateway

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.

• Closed-loop vs open-loop

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.

• Security and compliance

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.

• Pricing and the pilot

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.

• Full pricing

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.

• 7Konto vs PassKit

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.

• All solutions

Businesses that want to accept internal balances, gift cards, coupons or B2B2E accounts: retail chains, restaurants, hotels, corporate meal programmes, benefits providers, event organisers, coalition loyalty operators, property managers and campuses — plus the banks, PSPs and acquirers who want to offer all of that to their merchants.

A regular terminal moves card payments over the Visa or Mastercard networks. 7Konto moves closed-loop payments — internal balances held on the platform and spent inside your ecosystem. It runs alongside your card acceptance and adds payment types rather than replacing any.

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.

They scan a QR code — on a poster, a receipt, an email, an SMS or a screen — tap “Add to Apple Wallet” or “Add to Google Wallet”, and the card appears. About ten seconds, no form to fill in.

Both. iPhone users get the card in Apple Wallet, Android users in Google Wallet. Same design, same behaviour, same balance.

About five seconds end to end, from the cashier entering the amount to the customer seeing the new balance. The ledger itself settles the transaction in under 200 milliseconds; the rest is interface and QR scanning.

The card and the balance live on the server, not only on the phone. The customer can reach the card in a browser, or staff can look it up in the admin panel. A merchant who wants one can also issue a physical backup card.

No — a payment needs the balance verified in real time. Viewing the card, checking the balance and reading the transaction history all work offline from the last synced state.

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.

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.

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.

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.

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.

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.

Top-ups, debits (POS, staff phone or checkout widget), refunds and coupon redemptions. Issuing a card to a Wallet is free — create as many as you need. Balance checks, failed transactions and API read queries do not count.

Network adds the gift card module, the online checkout widget, the REST API and webhooks, up to five locations and ten terminals, multi-currency, priority chat support, 10,000 included transactions and $0.12 overage. Scale adds the commercial (B2B2E) accounts portal, Smart Account Detection, a custom admin domain, advanced analytics, up to twenty locations and forty terminals, phone support, 30,000 included transactions and $0.08 overage.

None on Solo, Network or Scale. An Enterprise deployment may carry an onboarding fee depending on scope, always quoted before anything is signed.

At any time, up or down, prorated. No lock-in, no cancellation fee, no long-term contract.

Public pricing is in USD. Invoices can be issued in EUR, UAH or another currency for Scale and Enterprise customers on request. Annual billing is available on the higher tiers, typically 15–20% below the monthly rate.

We get in touch to talk about continuing. Reaching 10,000 operations inside thirty days means the platform is already earning its place, and we move you onto a paid plan without interrupting anything.

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.

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.

A percentage of every transaction fee generated by merchants in your portfolio, applied uniformly across POS and online. The exact rate depends on volume, merchant category and deployment model. Monthly reporting separates offline and online volume so channel performance is visible.

Six to eight weeks to a live pilot. Week one is discovery, weeks two to four the integration — API, Terminal SDK, checkout widget and optional PSP embedding — and weeks four to six a pilot with five to ten merchants across POS and online. Sandbox environments are available throughout.

Yes: custom domain, your logo and colours on the admin panels and the Wallet cards, your brand on merchant-facing material, and the checkout widget in your palette. Merchants and their customers see you, not us.

No. Closed-loop stored value is a different product from open-loop acquiring and from a points programme. It adds a parallel line with better economics for the merchant categories card rails serve poorly — gift cards, employee allowances, restricted-use budgets, B2B2E — without touching the card volume you already have.

All the major vendors — PAX, Verifone, Ingenico and others. The QR flow works on any terminal that can display a QR code; a Terminal SDK is available where a deeper integration is wanted.

Yes — transaction events, card issuance, balance changes and administrative events, with endpoints configured in the admin panel. Available from the Network tier, alongside the REST API.

Yes, and it is built in rather than bolted on: data minimisation, right to deletion, right to access, portability and consent management. EU data centres by default, with Data Processing Agreements available.

EU data centres by default, which keeps GDPR straightforward and latency low for European merchants. Other regions are available where a customer needs them. Data is never sold, shared with third parties or used for advertising.

Closed-loop programmes run under PSD2's limited-network exemption, and we help partners structure deployments to stay inside it. PSD3 is expected to tighten the rules while grandfathering existing compliant programmes; we track it and will give partners notice well ahead of any structural change.

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.

Solo gets email support inside one business day. Network adds priority email and chat. Scale adds phone support and a two-hour ticket response. Enterprise gets a dedicated account manager and an SLA. The free pilot always includes hands-on help from our team.

Our team works in English, Ukrainian, Slovak and Russian, and support is given in whichever of those suits you. The language switcher lists every language this site is published in.

PayForSay s. r. o. is registered in Bratislava, Slovakia (company ID 54 455 073). The team works across several countries, and support covers EU business hours by default, extended on Enterprise.