Issuance
Create a card for an identity your own system already holds, and deliver it by SMS, email or QR.
Capability
Everything the panel does, the API does
Card issuance, transactions, balance queries, reporting and administration are all available over a REST API, with webhooks for the events you want to react to and a Terminal SDK where a POS vendor wants a deeper integration than the QR flow.
Updated
At a glance
- Protocol
- REST over HTTPS, JSON
- Events
- Transactions, issuance, balance changes, admin actions
- Sandbox
- Provided with documentation
- Availability
- From the Network plan
Updated
Working with it
- 01
Get sandbox credentials
Issued with the documentation, before any commercial commitment.
- 02
Issue a test card
The same call that will run in production, against test balances.
- 03
Subscribe to webhooks
Point an endpoint at us and receive events as they happen, with retries.
- 04
Go live
Swap the keys. Nothing else about the integration changes.
What you would automate first
Most integrations start in the same place: issuing cards from a system that already knows who the customers are — an HR system for employee allowances, a CRM for gift programmes, a fleet system for drivers. After that come balance top-ups on a schedule, and reconciliation into a finance system.
Top-up
Load balance on a schedule or on an event — payday, an order, a booking, a shift.
Reconciliation
Pull the transaction stream and match it against your own ledger, POS and online together.
Surface area
- Cards
- Create, update, suspend, reissue and look up
- Balances
- Top up, debit, refund, query and hold
- Accounts
- Personal and corporate, with limits and merchant rules
- Merchants
- Locations, workstations and permissions
- Reporting
- Transaction export, filtered by channel, merchant or period
- Terminal SDK
- For vendors integrating beyond the QR flow
Questions about this
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.
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.
Do you support webhooks?
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.
Start with a sandbox key
A free 30-day pilot, configured and supported by our team.