Integration Gateway

Connect every customer and member channel to the core.

Extend CoreVista's ledger and controls to mobile banking, agency banking, switches and ATMs through one controlled gateway.

Planned — in design

Available today

Current payment rails already work.

CoreVista supports internal, mobile-money and bank payments today, with funds held in suspense until the rail confirms clearing.

Payments & settlement
  • Internal transfers

    Book transfers between two accounts that settle synchronously.

  • Mobile money

    Outbound mobile-money payments with funds held in suspense until the rail confirms.

  • Bank payments

    Outbound bank payments with signed callbacks for settlement or failure.

  • Settlement

    Settlement batches reconciled against the rail's advice with differences posted to a control account.

Planned channels

The channel matrix.

The gateway is planned to cover customer-facing and agent channels over REST/JSON and SOAP/XML web services.

Planned and available channel coverage
Channel Use case Protocols Status
Mobile banking Customer apps, balance inquiry, transfers and statements REST/JSON, SOAP/XML Planned
Agency banking Agent onboarding, cash-in and cash-out at agent networks REST/JSON, SOAP/XML Planned
Core switch Card and real-time payment switch connectivity Switch web services Planned
ATM & POS Withdrawal, balance inquiry and terminal integration REST/JSON, SOAP/XML Planned
Existing rails Internal, mobile-money and bank payments REST + signed callbacks Available

The Integration Gateway is planned, not available. The current payment rails are available today and are documented in the payments module.

Architecture

Where the gateway fits.

Every channel request passes through the same controls before it reaches the core and the ledger.

  1. Channel request

    A mobile app, agent terminal, switch or ATM sends a request to the gateway.

  2. Gateway controls

    Authentication, request signing, idempotency and rate limits are applied before routing.

  3. CoreVista service

    The request is routed to accounts, payments or another core service with the right policy.

  4. Posting and ledger

    The business transaction is posted, audited and emitted to the outbox for downstream consumers.

Integration channel flow Step 1: Channel request; Step 2: Gateway controls; Step 3: CoreVista service; Step 4: Posting and ledger. CHANNEL FLOW 1 Channel request Mobile, agency, switch or ATM 2 Gateway controls Authentication, signing and idempotency 3 CoreVista service Accounts, payments or another module 4 Posting and ledger Audit, outbox and reconciliation
Illustrative channel flow. Every request passes through the same controls before the core and ledger.

Designed controls

Security and evidence from the first request.

The gateway is being designed around the same principles as the core: explicit identity, safe retries, limits and reconciliation.

  • Authentication and authorization for every channel client.
  • Request signing, replay protection and timestamp validation.
  • Idempotency keys for safe retries across channel requests.
  • Channel and customer limits enforced before funds move.
  • Structured logging, metrics and alerting for gateway traffic.
  • Reconciliation against channel advice and settlement files.

Questions

Integration questions.

For a specific channel or protocol, contact sales@adricore.co.ug.

Is the Integration Gateway available today?

No. It is planned and in design. Current payment integrations support internal transfers, mobile-money payments and bank payments with signed callbacks.

Which protocols will the gateway support?

REST/JSON and SOAP/XML web services, with switch-specific adapters where a channel requires them.

How are current integrations secured?

Current payment callbacks are signed with HMAC-SHA256 using a timestamp and signature header, and payment initiation is idempotent by key.

Plan your channel integration.

Tell us which channels you need, and we will map the gateway scope, protocols and controls to your operations.