Coreal.
Book a working session →
·Integration · Netcracker

Netcracker integration for embedded finance wallet.

Coreal connects embedded finance wallet 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.

Vendor
Netcracker
Surface
REST event webhook
Effort
Standard connector
Timeline
4–6 days

What this integration does.

IBAN-backed wallet with subscriber-aware risk and authentication. The wallet is issued by a sponsor EMI; the subscriber identity comes from the operator's BSS via read-only event subscription.

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.

● BSS EVENTS COREAL CONSUMES
  • ›Top-up event
  • ›SIM activation
  • ›Plan-tier change
  • ›Roaming entry
● VERSION COMPATIBILITY
Connectors verified against 10.x · 11.x · 2023.x

Market share: ≈20% of EU/Asia tier-1 operators.

● KNOWN LIMITATIONS
  • ▲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
● READ NEXT
All BSS integrations/integrations →Integration footprint on /platform/platform#integration-footprint →Read the 90-day Wave-1 field note/insights/wave1-corridor-90-day-field-note →See Coreal Super Wallet →/product/p1-super-wallet →
·Questions we hear

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 + wallet?

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.

·Working session

Bring the perimeter,
leave with a brief.

Book a working session →Read field notes →
Not ready to book 4 hours?

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.