> ## 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 seven live networks (Arc from 16 Sep 2026) with one call. The verification that runs in the AlgoVoi gateway.

<Note>
  **Included in the [Payment Rails bundle](/payment-rails-sqlite).** One commercial licence installs this component together with the whole self-hosted payment-rails estate. It ships inside the bundle, not as a standalone product.
</Note>

## What it is

**Settlement Verification** answers one question reliably, across many chains: *did this payment
actually settle — and finalise — on-chain?*

*Last updated: 21 August 2026.*

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.

<CardGroup cols={2}>
  <Card title="8 chains, one call" icon="link">
    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.
  </Card>

  <Card title="Settlement and finality" icon="circle-check">
    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".
  </Card>

  <Card title="Long-tail depth" icon="layer-group">
    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.
  </Card>

  <Card title="No infrastructure lock-in" icon="plug">
    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.
  </Card>
</CardGroup>

## 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 seven separate chain integrations.

## Frequently asked questions

### What does Settlement Verification do?

It answers one question reliably across many chains: did this payment actually settle and finalise on-chain? Where most payment tooling helps you initiate a transfer, this verifies that an arbitrary third-party settlement landed, confirming the transaction 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 verification that runs inside the AlgoVoi payment gateway in production.

### Which chains does it cover?

Seven live networks behind a single verification call: Algorand, VOI, Base and EVM, Solana, Hedera, Stellar, and Tempo, plus Arc from 16 Sep 2026, with mainnet and testnet variants for each. The depth is in the long-tail chains, handling Algorand ASA decimals, Hedera HTS tokens, Stellar trustlines and `CODE:ISSUER` assets, and EVM token-transfer logs, so a settled verdict means the same thing on every chain.

### Does it hold funds or private keys?

No. It is read-only and infrastructure-independent, so 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. That keeps it free of the regulatory and key-management risk that settlement execution carries, so it is easy to adopt and to put through review.

### How is Settlement Verification delivered?

It ships inside the Payment Rails bundle, where one commercial licence installs the whole self-hosted payment-rails estate. It binds to Substrate 2 (it is not part of Substrate 2 itself), is included in the Enterprise and On-premise plans, and is not distributed on public package registries. Install is token-gated from the AlgoVoi private index, and you set `ALGOVOI_LICENSE_KEY` to run.

## Get Settlement Verification

Settlement Verification ships inside the [Payment Rails bundle](/payment-rails-sqlite). One commercial
licence installs the whole self-hosted payment-rails estate. It binds to Substrate 2 (it is not part of
Substrate 2 itself), is included in the AlgoVoi Enterprise and [On-premise](/on-premise) plans, and is
not distributed on public package registries. Install is token-gated from the AlgoVoi private index; set
`ALGOVOI_LICENSE_KEY` to run. See the [Payment Rails bundle](/payment-rails-sqlite) for licensing, or
[email us](mailto:hello@algovoi.co.uk) for Enterprise / OEM.