SF

Signal Foundry

Public Payment Follow-Up
Offer Page Public Links Hub Public Command Center Public Approval Public Approval To Payment Public Teardown Public Deposit Lock Public Payment Guide Public Payment Type Public Tx Hash Public Kickoff Public Balance Collection Public Retainer Public FAQ Payment

Pending-transfer follow-up page

When the buyer said yes but the transfer still has not happened, keep the follow-up narrow and direct.

This page is for the gap after agreement and before funds arrive. The job is not to restart the sale. The job is to confirm the payer, isolate the last blocker, resend one clean payment route, and collect the tx hash before the thread loses heat, whether the transfer is a sprint deposit or the first retainer month. If the agreement still feels real but the bigger first payment keeps slipping, switch the thread into teardown as the smaller paid start rather than letting the deal go cold.

  • 1 payer owner confirmed
  • 1 last blocker isolated
  • Hash requested in the same thread
  • USDC preferred settlement asset
1. Confirm The Payer Name the person or wallet owner who is actually sending.
2. Remove The Last Blocker Clarify amount, asset, network, or wallet instructions once, or move into teardown if commitment size is the blocker. Open Public Payment Guide Open Payment Page
3. Ask For The Hash Keep the ask to one action: send the transfer, then return the tx hash. Open Public Kickoff

Follow-Up Map

Use the shortest sequence that turns agreement into transfer.

1. Confirm Who Is Actually Sending

If one person approved but someone else handles the wallet, name the exact payer so the next message reaches the right person.

Open Public Approval

3B. Use Teardown If The Deal Is Warm But The Full Deposit Keeps Slipping

If the buyer still wants to move but keeps delaying the bigger first payment, route into teardown: $299 total, $90 deposit, one workflow, same wallet.

Open Public Teardown Open Public Terms

4. Keep The Ask Limited To One Action

Ask only for the transfer and the tx hash in the same thread. Do not widen the message into a fresh negotiation.

Open Public Tx Hash

5. Turn The Hash Into Kickoff Fast

Once the hash lands, move directly into the startup packet so the deal does not fall into another silent gap.

Open Public Kickoff

6. Use This Only When Agreement Already Exists

If the buyer still needs trust, proof, or package choice, solve that blocker first instead of pushing follow-up too early.

Open Public Proof Open Public Pricing

8. Use The Retainer Page When The Monthly Lane Is Already Defined

If the buyer already agreed to a recurring monthly lane, route the thread through the retainer page instead of treating it like a generic first sprint deposit.

Open Public Retainer Open Payment Page

Common Leaks

Most pending payments stall for one of these reasons.

No Named Payer

A deal can be approved but still stall if nobody is clearly responsible for sending the transfer.

Wallet Friction

Some payers are ready in principle but pause when they have to choose a network or confirm the address.

Timing Drift

Others simply let payment slip because the follow-up never reconnects the transfer to the current sprint window.

Commitment Size Drift

Some buyers still want to move, but the first payment amount keeps making the thread stall. Smaller paid starts exist for this exact situation.

Payment Route

Keep the follow-up route concrete, then move straight into kickoff.

Confirm the payer, copy the wallet, send the transfer, and drop the tx hash back into the same thread so the work can move from pending to active. If the delivered sprint is already approved and the only remaining move is final payment, switch to the balance collection page instead of using a deposit-first route. If the recurring lane is already agreed, the same route can also collect the first retainer month. The same wallet can also take the $90 teardown deposit if that is the cleaner close.