Partner public wallet guide

If the payer is aligned but cautious, give them one safe wallet route without reopening the hidden partner system.

This page is for a payer who is already ready to move the transfer but needs a clean operational path. Keep the instructions brutally simple: confirm what this payment secures, confirm the network, copy the exact wallet, send the transfer, and return the tx hash in the same thread so the cycle can move into kickoff.

Open Partner Public Payment Guide Open Partner Public Payment

USDC preferred asset
Base preferred network
Hash required after transfer

Partner Public Payment Guide Map

Use the same short sequence every time a public-safe payer needs wallet confidence.

1. Start Only After The Public Payment Thread Is Already Clear

Use this page only after the payment path already has a clear yes. If the deal still needs proof or scope shaping, stay in the public payment or next-cycle pages first.

Open Partner Public Payment Open Partner Public Next Cycle Open Partner Public Close

2. Restate What This Transfer Secures

Before the payer opens a wallet, confirm whether this transfer secures one next month, one fresh sprint, or one agreed deposit.

Open Partner Public Next Cycle Open Partner Public Payment Open Payment Page

3. Confirm Network, Asset, And Exact Wallet

Preferred route is USDC on Base. If another network is agreed, confirm it first. Copy the exact wallet and compare the first and last characters before sending.

Open Payment Page Open Partner Public Payment

4. Keep The Hidden Layer Out Of Wallet Ops

Source path, margin logic, private screenshots, and off-page negotiation should stay outside the wallet thread unless they are required to complete the transfer safely.

Open Partner Public Boundary Open Partner Public White Label Open Partner Public Payout

5. Share The Tx Hash And Activate Fast

The transfer is not operationally complete until the tx hash is returned. Once it lands, move straight into kickoff or the next activation page instead of lingering in wallet discussion.

Open Partner Public Kickoff Open Partner Public Brief Open Partner Public Payment Follow-Up

6. Shift To Referral Public Payment Guide Only If The Payer Path Becomes Client-Led

If the wallet thread is now being carried by one client-led owner path instead of broader partner demand, move it deliberately into the referral public payment guide lane.

Open Referral Public Payment Guide Open Referral Public Payment

Best Guide Routes

Most partner public wallet-help threads should narrow into one of these pages.

Partner Public Payment

Best when the payer still needs the exact public payment handoff before the wallet opens.

Open Partner Public Payment

Partner Public Next Cycle

Best when the payer still needs clarity on what the next transfer secures.

Open Partner Public Next Cycle

Partner Public Payment Follow-Up

Best when the transfer should already be moving but the hash still has not landed.

Open Partner Public Payment Follow-Up

Partner Public Kickoff

Best when the transfer is done and the next move is starting execution fast.

Open Partner Public Kickoff

Referral Public Payment Guide

Best when the wallet thread shifts into one client-led referred payer path.

Open Referral Public Payment Guide

Guide Snapshot

Freeze the transfer scope, hidden layer, and confirmation step before funds move.

Guide Layer	Public Job	Keep Hidden	Main Destination	Review Trigger
Scope recap	Confirm what this transfer secures	Internal pricing logic	Partner Public Next Cycle	If the payment job is still vague
Wallet route	Remove network and asset friction	Off-page negotiation history	Partner Public Payment Guide	If the payer still wants a walkthrough
Hash proof	Collect the tx hash in the same thread	Hidden settlement detail	Partner Public Kickoff	If payment lands but the cycle has not started
Follow-up route	Chase the transfer without reopening the sale	Broader proof stack	Partner Public Payment Follow-Up	If agreement exists but no tx hash arrives
Transfer rule	Move only with an explicit family change	Ownership source and partner margin history	Referral Public Payment Guide	When the payment thread is no longer partner-led

Pasteable Lines

Use concise lines when the payer only needs the next safe step.

Network Line

Preferred route is USDC on Base. If another network is useful, let us confirm it first so both sides match.

Open Payment Page

Safety Line

Copy the wallet directly, check the first and last characters, and if useful send a tiny test first.

Open Partner Public Payment Guide

Scope Line

This transfer is for the approved next step already aligned in the thread, not for a wider undefined engagement.

Open Partner Public Next Cycle

Hash Line

After the payment lands, send the tx hash in the same thread so I can move this straight into kickoff.

Open Partner Public Kickoff

Transfer Line

If the wallet thread becomes client-led instead of partner-led, I should move it into the referral public payment guide lane deliberately.

Open Referral Public Payment Guide

Wallet

Preferred route: USDC on Base.

Fallback route is USDC or ETH on Ethereum if agreed first. Keep the same network on both sides and send the tx hash immediately after the transfer.

0xB3e9568A9cbB624403743340358c85CCce130893 Open Payment Page