Glossary · Infrastructure

What is Testnet?

A testnet is the dress rehearsal: the same rules, the same tooling, tokens worth nothing, so the mistakes cost nothing either. Every serious integration runs its webhook wiring, its confirmation policies, and its edge cases on testnet before touching mainnet money.

Testnets stay honest by being boring: faucets drip worthless tokens, resets happen, and nothing carries over. The discipline they enforce is the point, verify the flow end to end where failure is free.

Testnet on U.CASH

Integration testing runs the checkout, webhook, and settlement flows against safe networks before a store goes live, the same paths, none of the stakes.

See also

Confirmation policyCheckout embed

Testnet: FAQ

Are testnet transactions the same code path?
On the chain side, yes, that is the value: same transaction shape, same confirmation semantics. What differs is the money, which is the part you want absent during rehearsal.
Why do testnets reset?
Maintenance and spam control: worthless tokens still cost real infrastructure. Resets keep the rehearsal stage cheap for everyone.
Keep reading

The glossary, A to Z

Every term behind the rails, the assets, and the settlement.