1. Confirm Who Is Sending
If a founder approved but someone else handles the wallet, name the exact payer so the next message reaches the right person.
Open Approval To PaymentPost-agreement follow-up page
When the buyer says yes but the transfer still has not happened, shorten the follow-up path.
This page is for the gap between agreement and payment. The goal is not to restart the sale. The goal is to confirm who is sending the deposit, remove the last blocker, resend the cleanest payment path, and collect the tx hash before momentum leaks out.
- 1 payer owner confirmed
- 1 last blocker isolated
- 1 tx hash collected
Payment Follow-Up Map
Use the shortest sequence that turns agreement into transfer.
2. Confirm The Deposit And Network
Keep the follow-up concrete: amount, asset, network, wallet, and what the deposit secures right now.
Open Deposit Lock3. Remove Wallet Friction
If the payer is hesitating because of wallet steps, route them to the short payment guide instead of writing a custom explanation.
Open Payment Guide4. Resend The Payment Route
Once the blocker is gone, send the payment page again and keep the ask limited to one action.
Open Payment Page5. Collect The Hash And Start
After funds move, ask for the tx hash immediately so the deal turns into kickoff instead of another silent gap.
Open Kickoff BoardCommon Follow-Up Leaks
Most pending payments stall for one of these reasons.
No Named Payer
A deal can be approved but still stall if no one 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 the payment slip because the follow-up message never reconnects the transfer to the current build window.
Best Next Routes
Match the blocker to one narrow page.
Need Payer Alignment
If the deal is approved but you still need the exact payer or approver path, return to approval-to-payment first.
Open Approval To PaymentNeed Written No-Call Follow-Up
If the buyer wants to keep everything in writing, use the async close path and fold the follow-up into that thread.
Open Async CloseNeed Payment Confidence
If the payer is ready but cautious, the payment guide is still the shortest way to remove wallet friction.
Open Payment GuideReady To Send
If the payer is confirmed and the route is clear, send them to the payment page now and ask only for the tx hash after transfer.
Open Payment PageWallet
Preferred route: USDC on Base, then tx hash back into kickoff.
Keep the follow-up simple. Confirm the network, copy the wallet, send the transfer, and share the hash so the work can move from pending to active.
0xB3e9568A9cbB624403743340358c85CCce130893
Open Payment Page
Short Follow-Up Lines
Use calm lines that advance the payment without sounding needy.
Owner Line
Since the scope is already agreed, the only thing I want to confirm is who is sending the deposit so I can route the payment page to the right person.
Friction Line
If the blocker is just the wallet step, I can keep it to one short route: network, address, transfer, tx hash.
Timing Line
If you still want the current slot, the next useful move is the deposit and hash so I can move it into kickoff.