Settlement Verification

​

What it is

Settlement Verification answers one question reliably, across many chains: did this payment actually settle — and finalise — on-chain? Most payment tooling helps you initiate a transfer. This verifies that an arbitrary, third-party settlement landed: the transaction is confirmed, it reached the right recipient, for the right amount, in the right asset, with the finality semantics of that specific chain applied. It is the same settlement verification that runs inside the AlgoVoi payment gateway in production — packaged as a standalone product you can embed in your own. It is read-only and infrastructure-independent: it never holds keys, moves funds, or custodies anything. You supply your own RPC endpoints; it makes the calls, applies per-chain verification logic, and returns a verdict.

​

What you get

• Verification-as-a-product. Confirm that an arbitrary settlement finalised — not just the payments you initiated. The scarce capability: trustless confirmation that funds landed, on the chain and in the asset you expected.
• Correct per-chain finality. Each network finalises differently. Settlement Verification encodes the right rules per chain — confirmations, indexer lag handling, asset-id and decimal semantics, trustlines — so a “settled” verdict means the same thing everywhere.
• The long-tail chains, done properly. The differentiator is depth on Algorand, VOI, Hedera, Stellar and Tempo — where generic multi-chain tooling is thin or wrong. EVM and Solana are covered too; the long-tail is the value.
• One thing to integrate. A single, uniform call shape across every chain, with one result type. Add a network by configuration, not by writing another integration.
• Read-only by design. No custody, no signing keys, no fund movement, no bridging — so it carries none of the regulatory and key-management risk that settlement execution does. Easy to adopt, easy to put through review.
• Optionally compliance-bound. Pair a verified settlement with a Substrate 2 receipt to turn “it settled” into a signed, offline-verifiable, audit-ready attestation.

​

Chains covered

Mainnet and testnet variants for each.

​

Cryptography

• Verification reads each chain’s native signatures (Ed25519, secp256k1, …) — classical cryptography inherent to the chains, not something this SDK supplies or replaces.
• The receipt it binds into Substrate 2 is post-quantum signed (Falcon-1024, NIST Level 5) and offline-verifiable — so a verified settlement becomes evidence that stays unforgeable after the migration to post-quantum cryptography.

​

Why commercial

The verification layer was never published as open source — there is no free tier to fall back on. It is offered as a commercial product because the value is in the maintained, correct, long-tail coverage:

• Chains move. RPC shapes, forks, asset registries and finality rules change constantly. Keeping verification correct across 8 networks is ongoing work — bundled into the licence, not something you inherit and maintain yourself.
• Embed without attribution overhead. A commercial OEM licence lets you ship it inside your own product with no open-source notice obligations to carry through distribution.
• Enterprise terms. Support, warranty, and a defined relationship — the terms procurement and risk teams expect for a payments-critical dependency.

​

Who it’s for

• Payment platforms and PSPs that accept stablecoins across multiple chains and need to confirm settlement before releasing goods, funds, or access.
• Agentic and x402 systems that must verify a counterparty’s payment finalised on-chain.
• Marketplaces and treasuries reconciling inbound settlements across heterogeneous networks.
• Anyone who needs trustworthy multi-chain settlement confirmation without building and maintaining eight separate chain integrations.

​

Get Settlement Verification

Settlement Verification is an additional, separately-licensed package — an add-on that binds to Substrate 2, not part of Substrate 2 itself. It is available self-serve as a Starter licence (see below) and as a commercial OEM SDK and is included in the AlgoVoi Enterprise and On-premise plans. It is not distributed on public package registries.