Receipt Card
Single payment receipt with amount, date, card, transaction ID, a download PDF action, and a link to the formal tax invoice.
Single payment receipt with amount, date, card, transaction ID, a download PDF action, and a link to the formal tax invoice.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Receipt Card is the paid-confirmation surface: a single charge of $204.00 on Jun 1, 2026, Acme Team plan, 8 seats at $12 plus a $96 base, paid by VISA ending 4242, with the mono transaction ID ch_3QxT4nLkdIwHu7ix0Y3vBm9p and a Download PDF action pinned to the header. The footer note makes the split explicit: this is a payment receipt, the formal invoice with itemised tax details is one external link away.
The receipt rows are static markup, no array needed at this scale. The distinction between receipt and tax invoice is the difference between a user finding what they need and opening a support ticket.
Reach for this block on the billing history page when a user clicks into a single charge, wired to your payment record and PDF-generation endpoint. Pair the tax invoice link with your actual invoice URL.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the monthly subscription receipt. Other receipt shapes:
Tip: the tax invoice link earns its space even when you auto-attach the PDF, some users need the separate document for their accounting systems.