pay3: Real-Time Multi-Chain Payments on Streams
pay3가 어떻게 지갑 주소를 단일 링크로 대체하고, Quicknode Streams 통해 4개 체인에 걸친 실시간 결제 감지 기능을 구축했는지.
- 4 chainsReal-time monitoring of Ethereum, BNB Smart Chain, Solana, and Tron
- ~2sOnchain confirmation to webhook delivery, under ~2s
- $500K+$500K+ of stablecoin volume processed
For a stablecoin payment to feel like a real payment, the receiver needs to know the instant the money lands. That is the whole point of pay3. A user shares one link, pay3.so/@username. The sender picks a token and sends. The receiver sees a confirmed payment within seconds. No manual checking, no "did it go through?" messages, no refreshing a block explorer. Before pay3, receiving crypto meant sharing a 42-character wallet address that changes per chain and breaks the moment one digit is wrong. pay3 replaces it with one readable link, across the four chains where stablecoin users actually live: Ethereum, BNB Smart Chain, Solana, and Tron. Detecting payments in real-time across all four is the infrastructure problem.
과제
A watchlist that grows with every user, on every chain
When a user signs up, they add wallet addresses across EVM chains, Solana, and Tron. From that moment, pay3 has to know the instant anything lands at any of them. Across the user base, that watchlist grows with every signup, and gets harder to monitor with each new chain.
Polling could not keep the promise
The obvious starting point was polling: querying each chain on a loop for new transactions. It burned RPC requests, introduced unpredictable latency between a payment landing and the user seeing it, and across four chains became both expensive and unreliable. For a product whose entire promise is instant confirmation, polling was not a foundation pay3 could build on.
해결책
pay3 built its detection layer on Quicknode Streams, the real-time data pipeline that watches the addresses, contracts, and events you specify and pushes a webhook the moment something matches.
One registration model, four chains
A user adds their wallet addresses, pay3 registers them with Streams, and Streams watches Ethereum, BNB Smart Chain, Solana, and Tron for any incoming transaction. The moment a payment hits, Streams fires a webhook to pay3's backend, pay3 confirms it, and the receiver sees the confirmation within seconds. Ethereum went live first. BNB Smart Chain, Solana, and Tron followed the same registration model, with no new tooling and no separate pipeline.
Solana and Tron are load-bearing, not add-ons
Tron carries the largest share of pay3's retail USDT transfers, so pay3 needed all four chains from day one, not EVM-first with the rest bolted on later. Streams supports all four in the same product. Adding a chain is a config change, not a rebuild.
"Our users share one link, pay3.so/@username, and their sender just pays. No addresses, no chain confusion, no 'did it go through?' messages. They just see 'payment received.' Quicknode Streams is what makes that real across four chains simultaneously, and it's the same infrastructure we're now extending to merchants without rebuilding a thing."— Varun, Founder & CEOpay3