SF

Signal Foundry

Revenue Partner Intro Referral Payment Guide Board
Command Center Partner Intro Referral Approval To Payment Partner Intro Referral Payment Guide Partner Intro Referral Deposit Lock Partner Intro Referral Payment Follow-Up Partner Intro Referral Payment Proof Partner Intro Referral Activation Partner Intro Referral Kickoff Payment

Client-referral wallet guide

If the referred 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 client-referred first step but needs a clean operational path. 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 without pulling the original referrer back into wallet ops.

Open Referral Payment Guide Open Payment Page
  • USDC preferred asset
  • Base preferred network
  • Hash required in the same thread

Referral Payment Guide Map

Use the same short sequence every time a client-referred 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 Page

5. 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.

Wallet

Preferred route: USDC on Base for the approved first step.

Keep the payment tied to the current referred 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 referral payment friction comes from a few repeated errors.

Wrong Network

Sending on the wrong network creates avoidable recovery risk and slows down the exact referred 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.

Referrer Dragged Into Wallet Support

The original buyer should not become the default help desk once the direct payer has the route.

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.

Boundary Line

The original referrer does not need to stay inside wallet questions if the payer and operator route is already clear.

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.