Skip to main content
Invoice Bot never implies a payment method is confirmed automatically when it isn’t. Every method is labeled with what actually happens once someone pays — shown on /payment_methods and on each invoice’s own payment details.

​
Capability labels

​
The methods

Every non-link method still gets a Copy button on the invoice panel so the customer (or an admin) can grab the exact configured value without retyping it.

​
How crypto verification works

Bitcoin and Litecoin are the only methods verified without a human eyeballing a screenshot.
1

A quote is locked in

When BTC or LTC is attached to an invoice (through the builder, /invoice payment, or /payment), the bot converts the invoice’s total into a crypto amount using a live rate and locks that quote for a limited time (15 minutes by default). Even if the market moves before the customer pays, the quoted amount doesn’t change out from under them.
2

The customer pays the quoted amount

They send exactly that amount of BTC or LTC to the address shown on the invoice — as text, or scanned from a QR code if this bot instance has that optional feature installed.
3

An admin submits the transaction hash

Via /invoice verify or the Verify Payment button on the invoice’s Manage panel. The bot looks the transaction up on-chain and checks, in order: that it exists, that the configured address actually received funds, that the amount matches the quoted amount within a small tolerance (absorbing network fees and dust — Bitcoin and Litecoin each have their own tolerance), and that there are enough confirmations (2 for Bitcoin, 6 for Litecoin by default — roughly a 15–20 minute settlement window either way). A quote that’s already expired is rejected; refresh it first.
4

The invoice completes — or doesn't

An exact or overpaid amount both mark the invoice paid (any excess is recorded on the payment, never silently dropped). Underpaid leaves the invoice exactly as it was so you can follow up with the customer.
A given blockchain transaction can never pay two different invoices on the same asset — trying to reuse one is rejected outright. Re-verifying the same transaction against the same invoice is safe to repeat and just returns the same result instead of erroring.
/crypto_lookup runs the same on-chain lookup for ad-hoc inspection when a transaction isn’t tied to any invoice — see Crypto commands.

​
QR codes and PDF export

Where this bot instance has the optional QR feature available, crypto payment panels include a locally-generated, scannable QR code for the address and amount — nothing is sent to a third-party image service to produce it. Where it isn’t available, the panel still works, just as text only. The Export PDF button on an invoice’s Manage panel produces a PDF copy of the invoice for offline records, when this bot instance has that optional feature available.