1. Confirm The Transfer Route
Start with the asset, network, and wallet path that was supposed to be used so the hash is checked against the right route.
Open Payment Page Open Partner Intro Referral Payment GuideClient-referral payment confirmation page
When the referred payer says funds moved, turn that into confirmed proof and an immediate activation path.
This page is for the stage after a client-referred buyer, operator, or finance owner says the deposit was sent. The job here is not more selling. It is to freeze commercial ambiguity fast: confirm network, amount, sender, tx hash, and the approved first step, then move directly into activation while keeping the original referrer out of post-payment ops.
- 1 tx hash confirmed
- 1 sender and network checked
- 1 clean route to activation
Referral Payment Proof Map
Use one sequence from sent transfer to commercially confirmed start.
2. Check Sender, Amount, And Scope Tag
Tie the transfer to the exact approved first step. The proof should make it obvious what this payment belongs to.
Open Partner Intro Referral Deposit Lock Open Partner Intro Referral Approval Pack3. Keep The Referrer Out Of Proof Ops
The original buyer should not become the default relay for hash confirmation, receipt checking, or kickoff routing.
Open Partner Intro Referral Close Pack Open Partner Intro Referral Conversion4. Collect The Tx Hash Immediately
Ask for the hash as soon as the payer says funds moved. Do not let payment confirmation stay as a vague chat claim.
Open Partner Intro Referral Approval To Payment Open Partner Intro Referral Payment Follow-Up5. Confirm Receipt Into The Same Thread
Once the transfer is verifiable, acknowledge it in the same thread so commercial certainty does not split from delivery.
Open Partner Intro Referral Payment Follow-Up6. Move Into Activation And Handoff
After payment proof is attached, the next moves are activation, handoff packet, and kickoff, not more money talk.
Open Partner Intro Referral Activation Open Partner Intro Referral Intake Open Partner Intro Referral HandoffWhat To Confirm
These are the minimum proof details that keep the referred deal commercially clean.
Network
Make sure the proof matches the network that was agreed so nobody has to reconstruct the transfer path later.
Amount
Confirm the deposit amount against the approved first step rather than assuming the commercial number is obvious.
Sender
Name who sent the funds if the buyer, operator, and finance owner are different people.
Scope Reference
Tie the payment proof to the narrow first step so activation does not restart scope confusion.
Next Owner
Once proof is in, the thread should already know whether the next owner is activation, handoff, or kickoff.
Short Confirmation Lines
Use concise lines that turn referral payment proof into operational clarity.
Hash Line
Once the transfer is sent, the fastest next move is the tx hash so I can confirm it and move this into activation.
Scope Line
I want to attach the payment proof to the approved first step so the commercial side is fully closed before activation.
Receipt Line
As soon as the transfer is visible, I will confirm receipt and route the deal into the next operating step.
Boundary Line
The original referrer does not need to mediate proof or kickoff unless they explicitly want to stay visible.
Move Line
After the hash is attached, the next job is activation and handoff, not more payment discussion.
Do Not Do This
Most referral payment-proof issues come from leaving commercial proof too loose.
Do Not Treat Sent As Enough
A text claim without a verifiable transfer path still leaves the deal commercially fuzzy.
Do Not Detach Proof From Scope
Payment confirmation should stay attached to the exact approved first step, not float as a generic payment event.
Do Not Pull The Referrer Back In
The original buyer should not become the default relay between payment proof and operational start.
Do Not Keep Activation Waiting
Once proof is in, move into activation quickly so the thread does not cool again.
Do Not Reopen Wallet Explanations Late
If the transfer already moved, the job is proof and routing, not another full education loop about how to pay.
Best Next Routes
Route to the page that resolves the last remaining blocker fastest.
Need Deposit Lock First
If the deal is warm but the deposit has not actually been pushed yet, route back to the deposit-lock page first.
Open Partner Intro Referral Deposit LockNeed Payment Route Check
If there is still uncertainty around payer, network, or wallet steps, use referral approval-to-payment or the guide first.
Open Partner Intro Referral Approval To Payment Open Partner Intro Referral Payment GuideNeed Pending Transfer Nudge
If the payer has not actually sent the funds yet, switch to referral payment follow-up instead of asking for proof too early.
Open Partner Intro Referral Payment Follow-UpNeed Activation
If the proof is attached and the next move is launching the live cycle, route into partner activation.
Open Partner Intro Referral ActivationNeed Handoff Packet
If payment is confirmed and the only remaining job is context, owner, links, and kickoff clarity, route to the intro handoff page.
Open Partner Intro Referral HandoffNeed Minimal Startup Packet
If the proof is clean and the next job is compressing owner, brief, and links into one warm-intro start path, route here next.
Open Partner Intro Referral IntakeReady To Move
If the payment proof is clean and context is minimal, move into the kickoff route now.
Open Partner Intro Referral KickoffWallet
Preferred route: transfer sent, hash shared, activation started.
Use the same wallet-backed route. Confirm the payment proof fast, then move the referred deal into activation and handoff while the commercial context is still fresh.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page