03 — Bank Integration Plan — PSD2 / Tok / QWAC
Bilko HR — Bank Integration Plan — PSD2 / Tok / QWAC
MC Task: #102423
Owner: Finverge (Markos Zachariadis)
Status: OPEN — drafting in progress
Expected: 50917 bytes, 49368 chars, 31 sources
cited
Placeholder Notice
This page is a placeholder for the Finverge banking memo commissioned on 2026-05-28. The memo will cover:
Scope
- PSD2 NextGenPSD2 (Berlin Group) endpoint readiness status
for top HR banks:
- Privredna banka Zagreb (PBZ)
- Zagrebačka banka (Zaba)
- Erste banka
- OTP banka
- Addiko Bank
- Raiffeisenbank Austria (RBA)
- Hrvatska poštanska banka (HPB)
- eIDAS QWAC/QSeal certificate requirements:
- Procurement via DigiCert (or other QTSP)
- Can ALAI Holding AS (NO) obtain QWAC without HR entity?
- Timeline (8–12 weeks typical)
- Cost estimate
- SEPA Instant support:
- Which HR banks support SEPA Instant Credit Transfer (SCT Inst)?
- Bilko bank feed real-time reconciliation feasibility
- ISO 20022 integration plan:
- CAMT.053 (bank statement format) availability
- pain.001 (payment initiation format) acceptance
- Bilko backend parsing/generation readiness
- Tok platform coverage for HR:
- What does Tok (
~/ALAI/products/Tok/) already support for Croatian banks? - Gap analysis: what must be built for Bilko HR launch?
- Can Tok be extended for HR, or must Bilko implement separate bank integration?
- What does Tok (
- TPP (Third-Party Provider) regulatory registration:
- Option A: EEA passporting from NO via Finanstilsynet → HANFA (Croatian regulator)
- Option B: Separate HR AISP/PISP authorization via HANFA
- Timeline and cost comparison
- Recommended path
- Critical path timeline:
- Expected: 28–33 week critical path (QWAC + TPP + per-bank integration)
Per-Bank Readiness Matrix (TBD)
Once the Finverge memo is delivered, this section will contain a matrix with:
| Bank | PSD2 API Status | Berlin Group Version | SEPA Instant | CAMT.053 | pain.001 | Sandbox Available | Notes |
|---|---|---|---|---|---|---|---|
| PBZ | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
| Zaba | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
| Erste | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
| OTP | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
| Addiko | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
| RBA | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
| HPB | TBD | TBD | TBD | TBD | TBD | TBD | TBD |
Tok Gap Analysis (TBD)
Tok is ALAI’s independent Open Banking platform. Expected analysis:
- Current Tok coverage: Which HR banks are already integrated in Tok?
- Tok API availability: Can Bilko consume Tok API for HR bank feeds?
- Missing features: What must be added to Tok for HR launch?
- Bilko-specific integration: Does Bilko need separate QWAC/TPP, or can Tok act as proxy?
TPP Regulatory Decision (TBD)
Expected decision matrix:
Option A: EEA Passporting from NO
- Process: Register with Finanstilsynet (NO) → passport to HANFA (HR)
- Timeline: 4–6 weeks (assuming NO registration already exists or fast-tracked)
- Cost: Lower (one-time passporting fee)
- Risk: Regulatory uncertainty for non-EU EEA passporting post-Brexit precedent
Option B: Direct HR AISP/PISP Authorization
- Process: Apply directly to HANFA (Croatian Financial Services Supervisory Agency)
- Timeline: 8–12 weeks
- Cost: Higher (separate application + local legal counsel)
- Risk: Lower regulatory risk, but slower and more expensive
Recommended path: TBD by Finverge.
QWAC/QSeal Procurement Timeline (TBD)
Expected steps:
- Select QTSP (Qualified Trust Service Provider): DigiCert, GlobalSign, or other
- Submit application: Company registration documents + authorized signer identity verification
- eIDAS validation: QTSP validates legal entity with national registry
- Certificate issuance: QWAC (for API calls) + QSeal (for payment signing)
- Integration: Load certificates into Bilko backend / Tok platform
- Testing: Per-bank sandbox testing with QWAC
Timeline: 8–12 weeks (if no HR entity required) or 12–16 weeks (if d.o.o. formation first)
Critical Path Summary (TBD)
Expected phases:
- QWAC procurement: 8–12 weeks
- TPP regulatory: 4–12 weeks (depends on passporting vs direct)
- Tok extension (if applicable): 4–6 weeks
- Per-bank integration: 2–4 weeks per bank (7 banks = 14–28 weeks if sequential, 4–6 weeks if parallel with Tok)
- Bilko backend integration: 2–3 weeks
- E2E testing: 1–2 weeks
Critical path: 28–33 weeks (optimistic with EEA passporting and Tok extension)
Open Questions for Finverge
- Can ALAI Holding AS obtain QWAC without HR entity?
- Which HR banks have stable production PSD2 APIs (not just sandbox)?
- Does Tok already cover any HR banks?
- EEA passporting feasibility for NO → HR (post-Brexit regulatory precedent)?
- Can Bilko act as PISP (payment initiation) or only AISP (account information)?
- SEPA Instant adoption rate among HR SMBs (is it default, or must customers opt in)?
Next Steps
- Finverge: Deliver memo to
/Users/makinja/business/ALAI-Holding-AS/products/Bilko/docs/integrations/hr-bank-integration-plan.md - Skillforge: Update this BookStack page with full Finverge memo content (replace placeholder)
- CEO: Review critical path timeline and decide if HR launch is feasible within 6-month target
- John: Create MC tasks for QWAC procurement + TPP registration (after Finverge recommendation)
Local Source (Expected)
/Users/makinja/business/ALAI-Holding-AS/products/Bilko/docs/integrations/hr-bank-integration-plan.md
Status: NOT YET CREATED — MC #102423 is open.
BookStack Canonical URL: https://docs.alai.no/books/bilko-hr-market-entry/page/03-bank-integration