Partner programme

Deliver it to your clients, with the platform behind you

Most closed-loop projects need somebody local who understands the client's tills, their accounting and their people. That is implementation work, and it is work we would rather buy from partners than staff for every market we operate in.

  • Sandbox access
  • Engineering support
  • Commercial model for the work

Updated

At a glance

Who this suits
Systems integrators, POS resellers, agencies
Access
Sandbox, documentation and API keys
Support
Direct engineering contact during a build
Commercials
Implementation fees plus recurring share

Updated

What an implementation partner actually does

Maps the client's existing tills, accounting and HR systems onto a programme: what a balance is for, who funds it, what it may be spent on and how it reconciles.

Builds the integrations the client needs on top of the API — issuance from an HR system, top-ups on payday, a nightly export into the general ledger.

Trains the staff and stays through the first period, which is the part that decides whether a programme survives past its pilot.

  • The platform, the ledger and the wallet certifications stay ours to operate.
  • The client relationship and the implementation revenue stay yours.
  • Sandbox access does not require a signed client, so scoping is possible before a sale.

Becoming a partner

  1. 01

    Get sandbox access

    Documentation and keys, before any commercial commitment.

  2. 02

    Build something small

    A card issued from a client's own system is usually the right first proof.

  3. 03

    Bring a first client

    We work alongside you on the first deployment, engineer to engineer.

  4. 04

    Take the rest yourself

    With support available, but not in the way.

Details

Sandbox
Free, with documentation
Training
Technical onboarding for your engineers
Support during builds
Direct contact, not a ticket queue
Client contracts
Yours, or ours, depending on the market
Recurring share
On the platform fees of clients you bring
White-label
Available where a partner wants their own brand on it

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.

Get a sandbox key and scope a project

A free 30-day pilot, configured and supported by our team.

We use analytics cookies to see how the site is used. Nothing is set until you choose, and rejecting changes nothing about how the site works. Read the cookie policy