Amdocs integration for card issuance.
Coreal connects card issuance 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.
What this integration does.
Virtual Visa / Mastercard issuance, instant tokenisation for Apple Pay / Google Pay, 3DS authentication. Card-on-file works directly against the operator's recurring billing.
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.
- ›Subscriber identity
- ›Address verification
- ›KYC tier
- ›Plan change
Market share: ≈40% of EU/CIS tier-1 operators.
- ▲Older R-series (pre-R15) may require a topic-translation adapter
- ▲Multi-region Amdocs deployments need a per-region consumer group
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 + card?
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.
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.