1. Configure the network
A platform operator creates the sponsor, campaign, host location, placement, and enrolled tablet in the Control Center.
Real north-star journey · TEST mode
Test CrossGage from scan to sponsor reveal
This page does not invent lead arrivals. The customer button opens the real demo placement, where identity, dual OTP, wallet reservation, enrolled-device redemption, cooldown, and lead reveal use the same application contracts as the Control Center.
Sending OTP messages and moving Stripe TEST funds are deliberate operator actions.
2. Fund the sponsor wallet
A versioned one-time TEST price creates one canonical Stripe Customer and credits the exact paid principal to the wallet.
3. Scan concurrently
Two customers can open independent placement-scoped sessions at the same time without sharing identity or checkout state.
4. Verify both channels
Each customer provides sponsor-specific consent, then verifies both phone and email before a checkout code is issued.
5. Redeem on the enrolled device
The host approves the code on its signed tablet. CrossGage debits the wallet exactly once and creates the host payable.
6. Reveal after cooldown
The sponsor sees a redacted lead during cooldown and the verified contact automatically appears when release becomes due.
What counts as a successful test
Run two customer tabs, verify both channels for both people, redeem both codes from the signed host tablet, then watch the sponsor Lead List. Contact details must remain hidden until each cooldown releases; the wallet, payable, Stripe Transfer, and bank Payout states must remain distinct throughout.