Start free
English

Reconcile on-chain crypto payments automatically

Matching a payment on a public blockchain to the order that caused it is the part that manual crypto acceptance gets wrong.

Publish one wallet address and every payment into it looks alike. Two customers who owe the same amount are indistinguishable, a payer who sends late collides with the next order, and the only way back is a human reading a block explorer.

Locking a fresh receive address to each invoice removes the ambiguity at the source: the address a payment arrived at IS the order it belongs to. Signed webhooks then push the state change into your system, so reconciliation happens without anyone opening an explorer.

Common questions

How do you know which order a crypto payment belongs to?

The address the payment arrived at is the order it belongs to, because a fresh receive address is locked to each invoice. Attribution is a property of the address rather than a guess made afterwards.

Why is one shared wallet address a problem?

Every payment into it looks alike, so two customers who owe the same amount are indistinguishable and a late payer collides with the next order. The only way back is a human reading a block explorer.

Do you have to check a block explorer to match payments manually?

No — signed webhooks tell your system which invoice was paid, so matching happens in your own order records. Reconciliation becomes structural rather than a task somebody has to remember.

Next

Developers

Start free