Netcracker integration for IBAN issuance.
Coreal connects IBAN issuance to Netcracker BSS via rest event webhook, read-only. Standard timeline is 4–6 working days; the BSS write-path is never touched. Reverts in a single config change.
What this integration does.
Per-subscriber IBAN issuance via partner EMI passport. Subscribers can receive salary, transfers and direct debits — but the issuance ledger lives in Coreal, not the BSS.
Netcracker 10+ ships a configurable REST event webhook — the fastest BSS surface to integrate with. No adapter required: Coreal registers the webhook endpoint and starts receiving events on day one of go-live.
- ›Subscriber identity
- ›KYC tier signal
- ›Address verification
Market share: ≈20% of EU/Asia tier-1 operators.
- ▲Older 10.x release require manual webhook configuration in BSS-side admin UI
- ▲No native idempotency on webhook delivery — Coreal handles dedupe with idempotency keys
Does this require write access to Netcracker?
No. Coreal subscribes read-only to the operator's REST event webhook. The OCS, HLR and subscriber records are never written to. The connector reverts in a single config change.
What's the typical integration timeline for Netcracker + IBAN?
4–6 working days for a clean deployment with standard connector. The bottleneck is usually the operator's network change request to allow outbound events, not the connector itself.
Which Netcracker versions are supported?
Coreal has connectors verified against 10.x, 11.x, 2023.x. Earlier versions may need a translation adapter — typically +3–5 days.
Bring the perimeter,
leave with a brief.
Read the Wave-1 runbook first.
The full 90-day launch sequence — phases, partner-bank gates, who signs off when. No form to read it.
Read the runbook →INDICATIVE DATA · Numbers and timelines reflect public regulator filings, vendor documentation and our own delivery experience. Per-engagement values vary with operator profile, BSS vintage and regulatory perimeter. Engage early for a fitted estimate under NDA.