Coreal.
Book a working session →
·Integration · Optiva

Optiva integration for card issuance.

Coreal connects card issuance to Optiva BSS via csv batch + near-real-time api, read-only. Standard timeline is 7–10 working days; the BSS write-path is never touched. Reverts in a single config change.

Vendor
Optiva
Surface
CSV batch + near-real-time API
Effort
Batch adapter
Timeline
7–10 days

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.

Optiva is the BSS of choice for tier-2 and cloud-first operators. The event surface is split: CSV batches sufficient for end-of-day reconciliation, with a near-real-time API for top-up and SIM activation events. Our batch adapter handles both.

● BSS EVENTS COREAL CONSUMES
  • ›Subscriber identity
  • ›Address verification
  • ›KYC tier
  • ›Plan change
● VERSION COMPATIBILITY
Connectors verified against 10.x · Optiva CSM

Market share: ≈10% — tier-2/3 cloud-first operators.

● KNOWN LIMITATIONS
  • ▲Real-time events have a ≈30s delivery delay (not suitable for sub-second risk decisions)
  • ▲CSV batch reconciliation runs on a T+1 cadence by default
● 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 →Read: telco billing rails → embedded finance/insights/telco-billing-rails-embedded-finance →
·Questions we hear

Does this require write access to Optiva?

No. Coreal subscribes read-only to the operator's CSV batch + near-real-time API. 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 Optiva + card?

7–10 working days for a clean deployment with batch adapter. The bottleneck is usually the operator's network change request to allow outbound events, not the connector itself.

Which Optiva versions are supported?

Coreal has connectors verified against 10.x, Optiva CSM. 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.