ZYNC
Beta · testnet

Your Wallet and cashout

Understand what the Member Wallet should show before, during, and after a cashout request.

Your Wallet should make each balance and its status understandable. It should separate funded rewards, local Points, Credits, ZYNC balance, and contribution history. The current Beta uses test Credits with no real-world value; cash backing describes the production model.

One logical ZYNC Wallet owns independent TON and Base chain accounts, but the current Member cash-out form uses Base testnet only. TON cash-out and production destinations are not available through this form. A reward or cash-out request selects one chain and is never paid once on each chain.

For a funded reward, the Wallet should show:

  • the source Mission or campaign;
  • the amount and unit;
  • whether it is pending, held, available, or completed;
  • fees and limits that apply;
  • a dated activity history.

During cashout

A cashout request may need safety checks before it completes. The request should have one visible state and an explanation of what happens next. Repeated taps must not create repeated withdrawals.

High-value or unusual activity can require additional review. If that happens, ZYNC should say that the request is held rather than pretending it failed or disappeared.

The testnet Beta includes cash-out controls and visible request states. Production destinations, timing commitments, fees, limits, and recovery support remain subject to production release policy.

On this page