Coreal.
Book a working session →
·Integration · Amdocs

Amdocs integration for embedded finance wallet.

Coreal connects embedded finance wallet to Amdocs BSS via documented kafka topic, read-only. Standard timeline is 5–7 working days; the BSS write-path is never touched. Reverts in a single config change.

Vendor
Amdocs
Surface
Documented Kafka topic
Effort
Standard connector
Timeline
5–7 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.

Amdocs has the largest BSS footprint in EU and CIS tier-1 telco markets. Top-up, plan-tier and roaming events all surface on a documented Kafka topic. Our standard connector subscribes read-only and posts to the Coreal ledger; the BSS write-path is never touched.

● BSS EVENTS COREAL CONSUMES
  • ›Top-up event
  • ›SIM activation
  • ›Plan-tier change
  • ›Roaming entry
● VERSION COMPATIBILITY
Connectors verified against R11 · R12 · R15 · R22

Market share: ≈40% of EU/CIS tier-1 operators.

● KNOWN LIMITATIONS
  • ▲Older R-series (pre-R15) may require a topic-translation adapter
  • ▲Multi-region Amdocs deployments need a per-region consumer group
● 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 Amdocs?

No. Coreal subscribes read-only to the operator's Documented Kafka topic. 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 Amdocs + wallet?

5–7 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 Amdocs versions are supported?

Coreal has connectors verified against R11, R12, R15, R22. 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.