Overview & Strategy
Tok product vision, Balkan Open Banking strategy, B2B2B model, relationship to Bilko and Drop
Product Overview
Product Overview
What is Tok?
Tok is an Open Banking aggregator for Balkan markets (Croatia, Serbia, BiH).
Tagline: "Tok podataka iz banke u vaš softver" English: "Bank data flows into your software"
Tok = Serbian/Bosnian/Croatian for "flow", "current", "stream". Represents:
- Data flow (bank data → your software)
- Money flow (payment initiation, remittance)
- Current (electricity metaphor — infrastructure that powers things)
Domains
| Domain | Purpose |
|---|---|
tokapi.io |
Primary domain (registered) |
tokapi.one |
Backup domain (registered) |
api.tokapi.io |
API endpoint |
developer.tokapi.io |
Developer portal |
Business Model — B2B2B
Tok is infrastructure, not a consumer product. It connects three layers:
Banks (PSD2/bilateral APIs)
↓
Tok Platform (AISP/PISP aggregation layer)
↓
B2B Clients (fintechs, accounting software, developers)
↓
End Users (SMBs, accountants)
Tok targets developers and businesses — not end consumers directly.
Ecosystem Relationships
| Product | Role | Tok Scope |
|---|---|---|
| Bilko (Accounting SaaS) | Consumer of Tok AISP API | Automatic bank feed for Bilko users |
| Drop (Payment App) | Consumer of Tok PISP + AISP | Payments + balance display for Drop users |
| Third Parties | External API consumers | B2B2B — fintechs, accounting software, developers |
One Platform, Three Revenue Streams
AISP/PISP Licence (Finanstilsynet, ALAI Holding AS)
│
├── AISP scope ──► Tok Platform (central Open Banking layer)
│ ├── Bilko bank feed (automatic transaction sync)
│ └── Tok API (B2B bank data for third parties)
│
└── PISP scope ──► Drop Balkan (payment initiation)
Bilko pay-from-app (invoice payment from accounting)
Key insight: The PI licence required for Drop Norway covers Tok and Bilko at marginal cost — regulatory overhead shared across three revenue streams.
Market Position
There is no Open Banking aggregator for the Balkans.
| Provider | Balkan coverage |
|---|---|
| Plaid | No coverage |
| TrueLayer | No coverage |
| Tink (Visa) | No confirmed coverage |
| Yapily | "No connections in Eastern Europe" |
| GoCardless/Nordigen | Possibly HR only |
| Salt Edge | Bank-side compliance in RS, not aggregation |
| Local providers | None exist |
Tok is building the first Open Banking aggregator for the Balkan region — full first-mover advantage.
Countries
| Country | Standard | Status |
|---|---|---|
| 🇭🇷 Croatia | PSD2 / Berlin Group NextGenPSD2 | Architecture ready — Q3 2026 |
| 🇷🇸 Serbia | NBS bilateral (PSD2-equivalent law Aug 2024) | Architecture ready — Q4 2026 |
| 🇧🇦 BiH | Bilateral agreements (no PSD2 mandate) | Planned — Q1 2027 |
Brand
- Feel: Minimal, tech-forward, trustworthy — think Stripe, Plaid, Twilio
- Font: Inter (headings/body) + JetBrains Mono (code/API)
- Voice: Technical, direct, honest, developer-first
- Parent: ALAI Holding AS — small "An ALAI product" footer
Related Documents
- Implementation Status — current build state and timeline
- Architecture — Tech Stack
- Regulatory — Licensing Strategy
Implementation Status
Implementation Status
Current build state as of Q1 2026.
Component Status Table
| Component | Status | Target |
|---|---|---|
| API server (Kotlin/Ktor) | Foundation built | Q2 2026 |
| Croatian bank integration (Berlin Group) | Architecture ready, sandbox pending | Q3 2026 |
| Serbian bank integration — EU groups (UniCredit, Raiffeisen, NLB) | Architecture ready | Q4 2026 |
| Serbian domestic banks (NBS bilateral) | Stub — awaiting NBS registration | Q4 2026 |
| BiH bilateral banks | Planned | Q1 2027 |
Node.js SDK (@tokapi/sdk) |
Built | Q2 2026 |
Python SDK (tokapi-sdk) |
Built | Q2 2026 |
Kotlin SDK (io.tokapi:sdk-kotlin) |
Built | Q2 2026 |
| Webhooks | Designed | Q3 2026 |
| Payment initiation (PISP) | Planned | Q3 2026 |
Phase Timeline
Phase 1 — Foundation (Q2 2026)
- Ktor API server with core endpoints (
/accounts,/transactions,/consents) - Bank adapter interface (
BankAdapter) BerlinGroupAdapterskeleton- Node.js + Python + Kotlin SDKs (built)
- AISP registration at Finanstilsynet (Norway) — target: approved by Q2 2026
Phase 2 — Croatia Live (Q3 2026)
BerlinGroupAdapterproduction-ready for Croatian banks- QWAC certificate (DigiCert or GlobalSign) for PSD2 mTLS
- 3+ Croatian banks connected (Erste, OTP, Raiffeisen)
- 90-day consent expiry flow + email notifications
- Webhooks for transaction notifications
- PISP planning begins
- EEA passporting: Norway → Croatia (HNB)
Phase 3 — Serbia Live (Q4 2026)
- NBS AISP registration complete
BilateralAdapterfor domestic Serbian banks- EU bank groups in Serbia via
BerlinGroupAdapter(UniCredit, Raiffeisen, NLB) - 3+ Serbian banks connected
Phase 4 — BiH (Q1 2027)
- Bilateral agreements with EU bank groups in BiH (UniCredit, Raiffeisen, NLB)
- First BiH bank connected
Regulatory Timeline
| Milestone | Target | Status |
|---|---|---|
| Email to Finanstilsynet (NO) | Feb 2026 | Done ✓ |
| AISP application submitted (NO) | Apr 2026 | Pending |
| AISP approved (NO) | Jun 2026 | Pending |
| Passport notification to HNB (HR) | Jun 2026 | Pending |
| NBS pre-application inquiry (RS) | Q2 2026 | Pending |
| ALAI Tech d.o.o. APR registration (RS) | Mar 2026 | Pending |
| NBS AISP registration submitted (RS) | Jul 2026 | Pending |
| NBS AISP approved (RS) | Q4 2026 | Pending |
SDK Status
| SDK | Package | Status |
|---|---|---|
| Node.js / TypeScript | @tokapi/sdk |
Built — Q2 2026 |
| Python 3.10+ | tokapi-sdk |
Built — Q2 2026 |
| Kotlin | io.tokapi:sdk-kotlin |
Built — Q2 2026 |
MC Tasks (Open Banking)
Tasks #1934–#1943 track all Open Banking / Tok regulatory and development work.
| Task | Description | Priority |
|---|---|---|
| #1934 | AISP registration HR (HNB passporting) | High |
| #1935 | AISP registration RS (NBS) | High |
| #1936 | Research HNB AISP process | High |
| #1937 | Research NBS AISP process | High |
| #1938 | Croatian bank API sandbox testing | Medium |
| #1939 | Serbian bank API mapping (bilateral) | Medium |
| #1940 | BiH bilateral approach | Medium |
| #1941 | PISP authorisation RS | Low |
| #1942 | Bank feed architecture | Medium |
| #1943 | Professional Indemnity Insurance | High |