Architecture
Exactly one authoritative commercial layer.
The design constraint behind VOLTARI PAYMENTS™ is deliberately narrow: money is handled in one place, and every product consuming it does so through defined interfaces. That single constraint is what makes attribution, entitlements, metering and reconciliation coherent instead of approximate.
One authoritative core
A single core owns money movement and commercial state. Products do not keep private copies of balances, entitlements or payout logic.
Defined interfaces
Integration happens through stable contracts and events. Internals stay internal, so the core can evolve without breaking consumers.
Derived, not duplicated
Entitlements, credits and commissions are computed from settled commercial state rather than mirrored into each product's database.
Deterministic transitions
Grant, revoke, retry, refund and cancel are explicit state transitions with predictable downstream events.
Reconciliation as a property
Because one record holds the sequence of commercial events, reconciliation is a read of the system rather than a monthly reconstruction.
Rail-agnostic by design
Fiat settlement is the mature path today. The ledger model is designed so additional rails, including crypto, can be admitted as settlement inputs rather than as a second accounting system.
Consumption model
Products consume commerce; they don't reimplement it.
A product asks the core to charge, meter or allocate, and reacts to the events it emits. It never becomes a second source of commercial truth.
Request
A product initiates checkout, records usage, or submits a marketplace order through a defined interface.
Resolve
The core applies attribution, pricing, balances and allocation rules against one authoritative record.
React
Deterministic events tell products what to grant, revoke, provision or retry.
This page describes architectural intent at a level appropriate for evaluation, not the current production state of every capability.
Talk to us