Direct Sends, No More Auto-Forwarding: PayDirect's Latest Update on Base

Hey there, PayDirect developers and crypto enthusiasts! We've got a spicy update that just dropped into the main branch that’s going to change the way you handle your transactions on our platform. If you’ve ever found yourself grumbling about auto-forwarding direct sends, this one's for you.

What’s the Buzz About?

Our PayDirect crypto settlement platform just became a little more hands-off and a lot more streamlined. The latest change, courtesy of commit 4d332c8, halts the automatic forwarding of direct sends to settlement. That’s right—you send it, they keep it. We’re putting the control back into your hands (or rather, your code).

Before this update, if you sent crypto directly to a PayDirect workspace wallet, the system tried to be too helpful. It automatically forwarded those funds to settlement, even when you didn’t want it to. It was like that overzealous friend who insists on forwarding every meme you send to your group chat. Useful? Sometimes. Annoying? Often.

The Code Behind The Change

Let’s dive into the code to see what’s new. In the file app/api/v1/payouts/route.ts, the mechanism that auto-forwarded payments was stripped out like bad CSS. Here’s a look at the magic:

// Log the payout for the receiving wallet but do NOT create a forwarding
// payment record. Direct sends (payouts) should stay in the destination
// wallet. Only payments created through the Payment API get forwarded.
console.log(`[PAYOUT] ${body.amount} ${tokenSymbol} sent to ${body.destinationAddress} — no auto-forward (direct send)`)

The focus here is on making sure your direct sends stay direct. The new logic logs the payout but avoids creating any forwarding record. You get to keep your ETH right where you sent it. Déjà vu, am I right?

Meanwhile, over in lib/sweep-service.ts, we’ve made sure your wallets are still closely monitored, but without the extra baggage. Now, the SweepService is solely about detection, not direction. Take a peek:

// IMPORTANT: Direct sends are NOT auto-forwarded to settlement.
// Only payments created through the Payment API get forwarded.
// This service only logs balance discrepancies for monitoring.

const balance = await CdpWorkspaceWalletService.getBalance(
    row.address,
    row.environment === "live" ? "live" : "sandbox"
);

const usdc = parseFloat(balance.usdc) || 0;
const adao = parseFloat(balance.adao) || 0;
const eth = parseFloat(balance.eth) || 0;

if (usdc > DUST_THRESHOLD_USDC || adao > DUST_THRESHOLD_ADAO) {
    console.log(
        `[SWEEP] ${row.workspace_name} (${row.address.slice(0, 10)}...) ` +
        `[${row.wallet_type}] balances: ${eth.toFixed(6)} ETH, ${usdc.toFixed(2)} USDC, ${adao.toFixed(2)} ADAO`
    );
}

Notice how we are updating wallet checks? It’s all about keeping our eyes on balances without the interference of auto-sweeping. Smart wallets, free at last!

Why This Matters

So, why should you care? Well, developers and users alike get more autonomy with this change. The funds remain accessible exactly where you intended them to be—no more phantom transactions vanishing into the settlement ether. This change isn’t just about cutting out the middleman; it’s about optimizing your workflow and limiting surprises.

You’ll also save on gas fees that cropped up from unwanted forwarding maneuvers. Less forwarding means more crypto staying put, exactly as you planned. Plus, this update aligns with our vision to keep things simple and transparent.

Get Your Hands on It

Ready to embrace this newfound freedom? Pull the latest changes into your environment, and see the difference first-hand. For those keen to dive deeper, check our updated docs and always feel free to explore the code on GitHub.

Your feedback drives us, so keep those ideas and suggestions coming. We’re all about making PayDirect the best it can be, and that happens with developers like you at the helm. Let’s keep pushing boundaries, one line of code at a time.

Stay tuned for more updates, and as always, happy coding! 🔥

---

P.S. For more on how this impacts you and your projects, jump into the docs, and don’t hesitate to reach out with questions, suggestions, or a simple 'hello'. 🤓