Pre-execution simulation
Each run simulates the conversion and transfer before executing, so the expected outcome is visible first.
Module 3: Settlement & Reconciliation
Available
One operational record, from authorisation to receipt.
The settlement module follows every instruction through its whole life (authorisation, execution, settlement, exception handling, reconciliation, and receipt) as a single record your finance team can audit. No more stitching provider exports together by hand. Today the proof rail is stablecoin settlement via SEPA-connected EMI rails, with settlement near-real-time where the selected provider, destination institution, and jurisdiction support it.
Every instruction, the whole way through.
One record. Six stages. Auditable end to end.
Authorisation
Execution
Settlement
Exception handling
Reconciliation
Receipt
- Authorisation. The instruction is captured against the account and checked against your policy before anything moves.
- Execution. A pre-execution simulation runs (checks on liquidity, slippage bounds, and current rail status), then the action executes.
- Settlement. The conversion happens where needed and the rail settles to the destination. Near-real-time where the provider, destination institution, and jurisdiction support it.
- Exception handling. A failed or paused instruction stays in the same record with its reason, ready to retry, reconcile, or escalate.
- Reconciliation. The platform record is matched against provider confirmations, so your finance ops review one view, not many.
- Receipt. A signed webhook event closes the record; the end-user gets a partner-branded notification.
The proof rail: stablecoin settlement on SEPA-connected EMI rails.
Reconciliation is the module, one of several across the OVAAL platform. Stablecoin settlement is the rail that proves it end to end.
A common pattern: a recurring payout (rent, a subscription, a supplier bill) funded from a USDC or EURC balance. OVAAL handles the conversion and routing where needed, an EMI/SEPA rails partner settles to the destination IBAN, and the whole flow lands in one operational record. The partner holds the license and operates the regulated rail under its own authorisation. OVAAL runs the orchestration and the record, and does not custody funds.
- EU stablecoin frameworks. Under MiCA, e-money tokens such as USDC and EURC have a defined basis for routine use through authorised EU rails.
- SEPA Instant. The receive mandate took effect in January 2025 and the send mandate in October 2025, enabling near-real-time euro settlement where the destination institution supports it.
- EU Transfer of Funds Regulation. Travel Rule data exchange runs through an integration the partner operates, and is referenced in the record.
- EMI/SEPA rails partners. The partner selects an authorised EMI/SEPA rails provider; OVAAL routes and reconciles against it.
Controls on every instruction.
Slippage caps
Configure a per-instruction maximum. Above the threshold, the instruction pauses and notifies instead of auto-executing.
Exception capture
Failures and pauses are recorded with their reason in the same operational record, ready to retry or escalate.
Idempotent execution
Re-running on a webhook failure is safe; duplicate detection is handled server-side.
Travel Rule reference
Outbound transfers to counterparty providers trigger a Travel Rule integration the partner operates, recorded against the instruction.
Kill switch
Revoke the relevant session or delegated key in one API call; in-flight rules halt immediately.
The record exports as signed JSON or CSV, queryable by instruction, user, rule, or time, for your auditor or regulator.