Learn the payment flow on regtest

A chain we can control locally

Litecoin regtest runs separately from the public Litecoin network. Test blocks and test coins can be created locally. This makes it possible to exercise specific situations without risking customer funds or waiting for public network activity.

What the regtest tests check

Tests prepare accounts and public keysets, compare derived addresses with Core, and verify the Signer's transactions with multiple account-owned inputs on a disposable node with wallets disabled. They exercise the Transfer API, mempool and block observations, verified balances, callback retries, reorgs, repeated payment requests and controlled failures. Restore scenarios check a defined database and Signer-source snapshot. Only the harness mines, broadcasts and invalidates its own blocks; it does not use the developer's running node or wallets.

What it does not check for us

Passing scenarios do not prove unlimited capacity, every recovery interleaving or production readiness. The reviewed capacity and recovery defects are fixed, but evidence-size, address and deadline budgets still apply. Restoring an old database and seed cannot recover merchant attribution that was never included in that backup. Invoices, automated forwarding, Wallet API and JWT Authorization remain deferred; mainnet code has not passed live acceptance. Unknown chain evidence must remain unavailable, never a guessed balance or permission to spend.

Keep the environment separate

• Only use test keys and test coins in the development environment.
• Never paste a mainnet seed or Transfer Key into a public example.
• Check the selected network before testing RPC operations.
• Treat public widgets as previews until their own checkout integration is implemented.