Guide · updated November 18, 2026
One deposit address per invoice: how it works
One invoice, one address. It sounds like a technical detail and it decides whether your month-end close takes twenty minutes or two hours. Here is exactly what that address does, where it comes from and what breaks it.
What “one per invoice” actually means
The deposit address belongs to a single invoice and is never reused. The payment is identified by its destination: it does not matter who sent it, which exchange they used, or what the client wrote in the email. A USDC transfer carries an amount, a destination and a hash; there is no memo field that reaches the chain. When the destination belongs to one invoice only, the destination is the invoice number.
Where each address comes from
From your extended public key (xpub), not from an account we opened. Each invoice takes the next index (1, 2, 3…) and its address is derived from it; the index is stored on the invoice. Two consequences:
- It is watch-only. The server holds the public half of the key: it reads balances and transfers, it does not sign or move a cent.
- The money lands in your wallet. The addresses are children of your xpub; the private key that controls them is yours.
On Base and Ethereum the same derived address is used and the token is distinguished by contract. Tron is derived separately, on m/44'/195'/0'/0, because it has its own address format and its own USDT contract.
How the payment is detected
- Base and Ethereum: the
Transferevent of the USDC contract with that address as destination is read; for native ETH, the address balance. - Tron: TRC20 transfers to that address are listed and 19 blocks (one solid block, ~57 s) are awaited before the payment counts as final.
- Polling every 15 seconds: the status flips on its own and the invoice page updates without anyone clicking.
The thresholds are explicit: 99% of the expected amount or more, paid; above 105%, overpaid; below 99%, partial. The tolerance exists so an exchange rounding does not leave an invoice open for two cents.
What this address does not do
- It does not custody: no private key on the server, no Cuadre balance, no withdrawal to approve.
- It is not a gateway or an exchange: it does not convert to fiat and does not wire money to your bank.
- It does not see what is not on its list: another token or another network falls outside the match. The funds arrive, the invoice does not move. The network notice on the page is not decoration.
The three mistakes that break the match
- Reusing the address across two invoices: two payments to one destination and a guess based on amount and date.
- Collecting a balance on the old address: the payment lands on an invoice that is already closed. Issue an invoice for the balance, with a fresh address.
- Paying on another network: the same key yields the same address on several EVM networks, so you can recover it from your wallet, but it will not show on the invoice.
What the client sees
The public link (/i/<id>) with the amount in dollars, the token equivalent, the network, an address with its QR code, the live status and the due date (seven days by default). When the payment arrives the PDF receipt appears right there with hash, network and dollar value at arrival. No account and no app needed.
Checklist before you send the invoice
- Right amount: the address is bound to that expected amount, and the payment state comes from it.
- Network stated in the message, not only on the page. For USDC, Base is the cheap option.
- Due date that fits the client: if they pay in three weeks, do not give them seven days.
Frequently asked questions
Can I reuse the same address for two invoices from the same client?
Don't. With two invoices on one address, payments are matched by amount and date again, which is what breaks when a client pays in instalments. Each new invoice takes the next index from the xpub.
Where are the private keys for those addresses?
Not on the server. Cuadre receives only the extended public key (xpub): it can read the chain, not sign. The private key stays in your wallet and the money lands in addresses you control.
What if the client pays from an exchange?
It works the same. The transaction comes from the exchange's address, not the client's wallet; because the destination belongs to that invoice only, matching does not depend on who signed.
What if they pay on another network or with another token?
The same key yields the same address on several EVM networks, so funds can land where the engine does not read: you recover them from your wallet, but the invoice will not flip by itself.
If you want the system to do this
Cuadre derives the unique address, matches the payment, produces the receipt and exports the Excel: US$29/month, US$24/month for life for the first 10 founding accounts.
Reserve a founding seat · US$24 See the pricing in detail
Keep reading: how to reconcile USDC payments against your invoices · which USD rate applies when a client pays in crypto · the crypto payment Excel your accountant accepts · how Cuadre works in five steps · what the plan includes and what it does not.