Reference
Unique invoice number, order or project reference, issue date, and due date.
Core guide
Altcoin invoice emails that finance and customers can both read.
Combine an ordinary commercial invoice with precise blockchain instructions, independent verification, and a settlement record.
The invoice block
Keep business facts and payment facts in one predictable order.
A customer should understand the obligation before opening a wallet, while an operator should be able to match the resulting transaction later.
Pricing basis
What value is fixed, which currency denominates the invoice, and when any rate expires.
Asset identity
Full token name, symbol, network, and contract when applicable.
Destination
Complete address, required memo or tag, and change-verification path.
Fee rule
Whether the exact amount must arrive and how exchange deductions are treated.
Expiration
Named time zone and the late-payment rule when a quote or route has expired.
Confirmation
What counts as detected, confirmed, credited, and ready for fulfillment.
Receipt
Transaction ID, network, asset, amount received, settlement time, and any variance.
Lifecycle
Issue, verify, pay, monitor, credit, receipt.
Each status has a different meaning. A sent email is not a paid invoice, and a wallet notification is not necessarily final settlement.
Issued
The approved asset, network, destination, amount, and expiry are recorded.
Detected
A candidate transaction appears on the intended network.
Confirmed
The transaction meets the risk-appropriate confirmation threshold.
Credited
The received value is allocated to the invoice and a receipt is sent.
Plain-text example
Payment details
1
Asset
USDC on Polygon · verified contract on file
2
Amount
680.00 USDC · exact amount must arrive
3
Reference
AE-1042 · due October 28, 2026 at 5:00 PM PT
4
Verification
Confirm changed destinations by calling the number already in your vendor record.
Operational rule
Never let a button be the only instruction.
A payment link can improve usability, but the email should still display the exact asset, network, amount, destination, reference, and expiration. Links fail, wallets ignore parameters, and domains can be imitated.
Preserve the version of the invoice that was sent. If a route changes later, do not overwrite the historical record. A customer dispute or reconciliation review needs to know what instructions were visible at payment time.
Read the complete invoice checklist →Deciding between a link and a wallet address?
Compare portability, prefilled parameters, domain verification, compatibility, and fallback design.