XKOVA Docs
Core Banking
Core banking is where an institution's members, accounts, and ledger live. XKOVA connects to that core through the integration gateway, a small service that speaks one stable contract to XKOVA and a core specific adapter to the bank. The core is swappable: the gateway presents the same shape whether the core is Symitar, Corelation, or Fiserv.
What the gateway connects
The integration gateway is a deployable unit that sits between XKOVA and an institution's core banking system. XKOVA calls a fixed set of operations on the gateway, and the gateway translates each one into the core's own protocol through a banking provider adapter. The product code above the gateway does not change when the core does, which is what keeps the integration open. This is the orchestration model from Integrations and Orchestration applied to the bank ledger.
The operations it exposes
The gateway exposes a compact contract for the actions a money movement flow needs against the core ledger. At a high level:
| Operation | What it does |
|---|---|
| Resolve member | Look up a member or account in the core from a reference. |
| Check funds available | Confirm an account can cover an amount before acting. |
| Place hold | Reserve funds against an account. |
| Release hold | Free a previously placed hold. |
| Capture hold | Settle a hold into a debit. |
| Credit member | Credit funds to an account. |
| List operations | Read the gateway's operation stream for reconciliation. The gateway keeps at least 30 days of history, so an integrator can reconcile its own ledger against the core's state. |
| Notify member | Optional member notification hook. |
Errors from the gateway carry a code, a message, and a correlation id. A code from the gateway maps to an HTTP status; a failure reaching the core is passed through so the caller can tell the two apart. See Errors and Correlation IDs for the envelope and how to trace a request.
Example cores
The adapter behind the gateway is interchangeable. Examples of the kind of core that plugs in here include Symitar, Corelation, and Fiserv. An institution runs one core, and moving from one to another is an adapter change rather than a change to how XKOVA orchestrates the flow above it.
How it fits the rails
The gateway is how the rails touch fiat at the institution. It backs the hold, capture, and credit steps that funding and off-ramp depend on, so a member crediting a savings account or an off-ramp paying fiat out resolves against the real core ledger. See Funding and Off-ramp for the request side of those flows and Conversion and Ramps for how fiat and stablecoin convert.