> ## Documentation Index
> Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.
# Settlement Verification
> Confirm a stablecoin payment settled and finalised on chain across eight networks with one call. The verification that runs in the AlgoVoi gateway.
## 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.
Algorand, VOI, Base / EVM, Solana, Hedera, Stellar, Tempo and Arc — mainnet and testnet —
behind a single verification call. No per-chain integration to build and maintain yourself.
Confirms the payment is included, succeeded, and reached the correct recipient and amount —
with each chain's distinct finality model handled, not a one-size-fits-all "is it mined".
The hard parts done right: Algorand ASA decimals, Hedera HTS tokens, Stellar trustlines and
`CODE:ISSUER` assets, EVM token-transfer logs. The chains generic SDKs verify poorly.
Bring your own nodes — RPC endpoints are injected, with sane public defaults. Featherweight
and dependency-light, so it drops into any backend without pulling in a chain SDK per network.
## 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](/substrate-2)
receipt to turn "it settled" into a signed, offline-verifiable, audit-ready attestation.
## Chains covered
| Network | Settlement verification |
| -------------- | ---------------------------------------------------------- |
| **Algorand** | Native ALGO + ASA transfers, decimals, asset-id binding |
| **VOI** | Native + ARC-200 smart-contract tokens |
| **Base / EVM** | ERC-20 token-transfer log verification |
| **Solana** | SPL token settlement |
| **Hedera** | HTS token transfers via mirror node |
| **Stellar** | Payments + path-payments, trustlines, `CODE:ISSUER` assets |
| **Tempo** | EVM settlement |
| **Arc** | EVM L1 settlement |
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 (perpetual one-time or annual)** (see below) and as a **commercial OEM SDK** and is
included in the AlgoVoi Enterprise and [On-premise](/on-premise) plans. It is not distributed on
public package registries.
Starter licence — **perpetual (one-time) or annual subscription**, self-hosted, paid in **USDC** on mainnet; the [store](https://api.algovoi.co.uk/suite-store) shows current pricing for both and issues your licence key + install command on settlement; install from the private index and set `ALGOVOI_LICENSE_KEY` to run. Enterprise / OEM (warranty, indemnity, SLA, multi-deployment, Substrate 2 binding): [email us](mailto:hello@algovoi.co.uk).