Add closed-loop as a native payment method in your checkout
"Pay with 7Konto" appears in your existing gateway checkout alongside cards and wallets. Every merchant on your platform benefits — no code changes on merchant sites. One integration, unlimited merchants.
One integration. Every merchant benefits.
You integrate 7Konto once at the gateway level. Every merchant on your platform gets closed-loop payments automatically — plus optional widget and API paths for merchants who want deeper control.
PSP Checkout Embedding
7Konto appears as a payment method inside your gateway checkout. Every merchant on your platform sees "Pay with 7Konto" auto-appear alongside cards and wallets. Merchants change NOTHING on their sites.
- • Single gateway-level integration
- • Zero merchant integration required
- • Smart B2C vs B2B/B2E routing
- • Revenue share on every transaction
Time to launch
6–8 weeks to pilot across all merchants
Merchant-site Widget
For merchants who want 7Konto directly on their site without going through your PSP checkout. One-line JavaScript embed with four auth methods.
- • Wallet · SMS/Flash-call · Email · Corporate ID
- • Customizable to merchant brand
- • Merchant self-service integration
Best for
Merchants who want direct control of the checkout UX.
REST API
Full REST API for merchants who want to build custom experiences on 7Konto's ledger and issuance engine. Terminal SDK for POS deployments.
- • Card issuance API
- • Terminal SDK (PAX, Verifone, Ingenico)
- • Webhooks + sandbox
Best for
Larger merchants with in-house engineering teams.
Start with Path 1 (PSP embedding). Most PSPs get 80% of the value from a single gateway integration. Paths 2 and 3 are available for specific merchants who need deeper control.
Why PSPs add closed-loop
Your merchants ask for capabilities card rails can't deliver. Fintech competitors are showing up with the answer.
Merchants ask for gift cards, employee accounts, corporate meals
You send them elsewhere. They integrate two providers. Some drop your gateway entirely.
Every new payment method requires per-merchant integration
You end up saying no to smaller merchants. Custom builds don't scale.
Closed-loop is a different regulatory regime
Requires closed-loop expertise most PSPs don't have in-house. Building it is 12+ months.
You're losing revenue on transactions that would fit closed-loop
Gift, corporate allowances, aid disbursement, B2B credit — you can't offer them, so merchants take them elsewhere.
7Konto plugs into your gateway once — and your merchants get closed-loop payments as a native option, without you building the platform or licensing an EMI.
What your merchants get
Four closed-loop products your merchants have been asking for — delivered through your existing gateway.
Digital gift cards & prepaid
Retail chains, restaurants, hospitality. Higher redemption than paper. Sold online or in-store.
B2B fuel & fleet cards
Per-driver limits, fuel reservation before dispensing. Alternative to WEX/FleetOne.
Corporate meals & benefits
B2B2E allowances for employees. MCC-locked, schedule-controlled, merchant-restricted.
Online-first e-commerce
Same closed-loop balance works online through your gateway. Smart B2C/B2B account routing.
100% of data. 0% of interchange.
Closed-loop transactions never leave your ecosystem. All the strategic advantages of stored value — without building it yourself.
Customer data stays with you and the merchant, not the card networks.
Interchange fees. Your economics, your rules.
EMI license required. PSD2 limited-network exemption applies.
Attribution across POS and online in one dataset.
You're not cannibalizing your card processing business. You're adding a parallel product line with better economics — for merchant use cases card rails don't serve well (gift, B2B2E, aid, corporate credit). Same customers, new revenue.
What Revenue Share looks like at scale
Illustrative example based on typical PSP mid-market portfolios.
- Merchants on your gateway using 7Konto 500
- Avg. 7Konto transactions per merchant / month 2,000
- Avg. transaction value $25
- Your revenue share 1.5%
6–8 weeks to live "Pay with 7Konto"
Structured integration from partnership call to full merchant rollout.
Discovery & scope
Week 1Partnership call. We review your merchant portfolio, technical stack, and gateway architecture. Identify pilot merchants and commercial model.
Gateway integration
Weeks 2–4Sandbox integration first. Our engineering team works directly with yours. "Pay with 7Konto" registered as a payment method in your gateway. Optional widget + Terminal SDK for merchants who want deeper control.
Merchant pilot
Weeks 4–65–10 merchants from your portfolio go live with 7Konto in your checkout. We handle their onboarding, training, support. KPIs tracked jointly: card issuance, transactions, adoption rates.
Full portfolio rollout
OngoingStructured rollout to your entire merchant base. Marketing collateral, sales enablement, dedicated support. Every new merchant onboarded to your gateway gets 7Konto by default.
Questions from Payment Providers
Common questions from PSPs, gateways, EMIs, and processors evaluating partnership.
What exactly do we integrate to get "Pay with 7Konto" in our checkout?
A single gateway-level integration on your side. We provide the SDK/REST endpoints, sandbox, and technical support. You add 7Konto as a payment method in your existing payment method catalog — same way you add cards, wallets, or bank transfers. Every merchant on your gateway then sees "Pay with 7Konto" appear at checkout automatically. No per-merchant work.
How is this different from just adding another payment method?
The transaction runs on our closed-loop ledger, not through card rails. 0% interchange, 100% of transaction data stays with you and the merchant. Also, closed-loop enables use cases card rails can't: B2B2E accounts, MCC-locked disbursements, gift cards with breakage, employer-controlled spend. It's a genuinely new revenue category, not a duplicate of what you already offer.
What's the revenue share model?
You get a percentage of every closed-loop transaction fee generated by merchants on your gateway — both online (via 7Konto in your checkout) and offline (via 7Konto POS integrations). Aligned incentives: we grow when you grow. Specific percentages depend on volume and merchant category. Transparent monthly reporting.
How does authentication work in the online widget?
When a customer picks "Pay with 7Konto" at checkout, they authenticate via one of four one-click methods: (1) Wallet card scan — the same card used at POS. (2) Phone — SMS one-time code or Flash-call verification. (3) Email — one-time code. (4) Corporate ID — for B2B/B2E users, no consumer signup. You can enable all four or restrict to a subset in your gateway configuration.
How does smart account routing work?
When the customer authenticates, the platform identifies whether they hold a personal balance (gift card, prepaid, loyalty) or a corporate/employee account (fuel card, meal allowance, benefit line). The right rules, limits, merchant restrictions, and reporting apply automatically. Same widget, same customer flow — different account routing under the hood.
How long from partnership call to live "Pay with 7Konto" in our checkout?
Six to eight weeks end-to-end for typical deployments. Week 1: discovery + technical scope. Weeks 2–4: gateway integration (sandbox first, then production). Weeks 4–6: pilot with 5–10 merchants across POS and online. Full rollout to all your merchants after pilot success. Our team runs most of the technical work.
Do we need to be an EMI, or does 7Konto need an EMI license?
No EMI license required on either side for closed-loop payments. 7Konto operates under PSD2's limited-network exemption, which covers closed-loop programs (gift cards, employee accounts, restricted-use aid, coalition programs). If any specific merchant program approaches the boundary, we advise upfront.
Can merchants also use POS terminals in addition to online?
Yes. The same 7Konto balance works at POS terminals — via the Terminal SDK for deep integrations, or a light QR-code flow for terminals that can display QR on screen. Merchants get one balance, one admin, one reporting stream across offline and online.
Let's discuss what closed-loop looks like on your gateway
30–60 minute partnership call. We walk through your merchant portfolio, discuss integration scope, and propose a pilot with 5–10 merchants across your platform.