Hey PH! 👋 Maximo here, builder of txpay.app. I built this because every time I wanted to receive USDC on Base, it turned into a 10-minute ordeal, the sender on the wrong chain, opening bridge UIs, swapping tokens, waiting for confirmations, checking if it arrived. Just to get paid. The fix seemed obvious: a link that encodes the full intent. Token, amount, chain. The payer just clicks and pays with whatever they have. Li.Fi handles the routing if anything needs bridging or swapping. "Why not just share your wallet address?" fair question. The address tells the payer where to send. It doesn't tell them what token, what chain, or how much. So they guess, or you go back and forth, or they send ETH when you wanted USDC, or they're on Arbitrum and you're on Base. Every one of those gaps is a reason the payment doesn't happen. A link removes all of them, the payer sends whatever token they hold on whatever chain, and you receive exactly what you asked for. No bridging on their end, no swapping, no decisions. And no middleman touches the funds, the payment goes wallet to wallet, fully self-custodied. The part I'm most proud of: every link is HMAC-signed, so even a compromised database can't silently redirect a payment. The trust anchor is a secret key, not DB integrity. Would love to hear from anyone who's dealt with this, freelancers, DAO contributors, open source maintainers. What's your current workaround? And what would make this actually fit into your workflow? Try creating a link, takes 30 seconds

txpay.app

Shareable Crypto payment links that work across every chain

Shareable Crypto payment links that work across every chain