BTC invoicing fails when you put one bech32 on every PDF and hope memos exist. They do not, in any way AP will use.
Quote dollars
Your contract is $8,000. The invoice should say $8,000, lock a sats amount for a window, and expire the lock. Quoting 0.12 BTC trains the client to wait for a dip.
One address per invoice
BIP-84 (bc1q…) from your account xpub, unique index per invoice, is the non-custodial pattern. The platform watches; it does not hold the keys. If the platform gives you an address from their wallet and later batches BTC to you, that is a processor.
Confirmations
Bitcoin finality is not Polygon finality. Pick a confirmation policy and do not mark paid at 0-conf because you are impatient. Underpays from fee-bumps and change-avoidance are normal; your status machine needs underpaid.
Lightning
If you need Lightning, that is a different product (and usually a different custody story). Do not assume an on-chain invoicer is a Lightning service.
Settlematic Collect supports BTC via invoice-scoped BIP-84 derivation. We are not a custodial exchange. Canonical: bitcoin invoice how to bill clients in BTC. settlematic.com
Top comments (0)