1. Restate The Approved First Step
Before the payer opens a wallet, make sure they know exactly what the deposit is securing right now.
Open Partner Intro Approval To Payment Open Partner Intro Deposit LockWarm intro wallet guide
If the warm-intro payer is aligned but cautious, give them one safe route instead of a crypto lecture.
This page is for the payer who is already willing to move the deposit for a warm-intro first step but needs a clean operational path. The goal is to keep the instructions brutally simple: confirm the approved first step, confirm the network, copy the exact wallet, send the transfer, and share the tx hash back into the same thread so the deal can move into proof and activation.
- USDC preferred asset
- Base preferred network
- Hash required in the same thread
Intro Payment Guide Map
Use the same short sequence every time a warm-intro payer needs wallet confidence.
2. Confirm The Correct Network
Preferred route is USDC on Base. Fallback is USDC or ETH on Ethereum only if agreed first. The network must match on both sides.
3. Copy The Exact Wallet
Copy the address directly, compare the first and last characters, and do not type it manually.
Open Payment Page4. Send A Test If Needed, Then The Deposit
If the payer is unfamiliar, a tiny test transfer is acceptable. After that, send the full agreed deposit on the same route.
5. Share The Tx Hash In The Same Thread
The transfer is not operationally complete until the tx hash is shared back where the commercial thread already exists.
Open Partner Intro Payment Proof6. Move Into The Live Start Path
Once the hash is attached, the next job is activation and kickoff, not more wallet discussion.
Open Partner Intro Activation Open Partner Intro KickoffWallet
Preferred route: USDC on Base for the approved first step.
Keep the payment tied to the current warm-intro deal, use the same agreed network on both sides, and share the tx hash in the same thread immediately after the transfer.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page
Common Mistakes
Most warm-intro payment friction comes from a few repeated errors.
Wrong Network
Sending on the wrong network creates avoidable recovery risk and slows down the exact deal that is already warm.
Deposit Detached From Scope
The payer needs to know what this transfer secures. If that stays vague, even simple wallet steps start to feel risky.
No Tx Hash Returned
Payment is not operationally real until the hash is attached back to the same thread and proof can begin.
Too Many Optional Routes
One clean route usually closes better than multiple half- explained asset and network options.
Short Lines
Use concise lines when the payer only needs the next safe step.
Network Line
Preferred route is USDC on Base. If you want another network, it needs to be confirmed first so both sides match.
Safety Line
Copy the wallet directly, check the first and last characters, and if useful send a tiny test first.
Scope Line
This transfer is for the approved first step already aligned in the thread, not for a wider undefined engagement.
Proof Line
After the payment lands, send the tx hash in the same thread so I can move this straight into proof and activation.
Best Next Routes
Route to the shortest page that solves the real blocker.
Need Payer Handoff First
If the payer is still not named or the approval handoff is fuzzy, route back to intro approval-to-payment first.
Open Partner Intro Approval To PaymentNeed Slot Pressure
If the transfer needs timing pressure tied to the current window, use the deposit-lock page before repeating wallet steps.
Open Partner Intro Deposit LockNeed Transfer Nudge
If the payer already understands the route but still has not sent funds, move into the payment follow-up page.
Open Partner Intro Payment Follow-UpFunds Already Sent
If the transfer is visible, stop on wallet instructions and attach the proof immediately.
Open Partner Intro Payment ProofReady To Start
If payment and proof are both clean, move into the intro activation lane now.
Open Partner Intro Activation