Blog
Every crypto payment system has to answer one question on day one: how do you know when a customer paid? The webhook approach is faster and cheaper. We picked the slower, more expensive one - generating a deterministic address per invoice and watching the chain directly. Here's the architectural reasoning behind that call, and what we give up to make it work.
There's a question every crypto payment system has to answer on day one: how do you know when a customer has paid? It sounds trivial. The customer sends funds, the chain confirms, the merchant gets credit. But underneath that one-line description is a real architectural fork, and the choice you make there propagates into everything else: your reliability story, your failure modes, your dependence on third parties, and ultimately how much your merchants can trust the system. We picked the path that fewer crypto payment platforms pick, and we picked it deliberately. This post is about why. The two ways to detect a payment Broadly, there are two approaches. Webhook-based detection. You partner with a service (a blockchain indexer, a node provider, a wallet API) and you tell them "let me know …