Payment History Table
Transactions ledger with date, description, card brand chip with last four digits, tabular amount, status badge, and a per row receipt link.
Transactions ledger with date, description, card brand chip with last four digits, tabular amount, status badge, and a per row receipt link.
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
Payment History Table is the transactions ledger for the Acme workspace, six rows spanning Feb to Jun 2026 covering charges, a retry, a failed attempt, and a refund. Each row carries the date, description, a mono method chip showing the card brand and last four digits, a right-aligned tabular amount, a status Badge (Paid, Failed, or Refunded), and a Receipt link that becomes No receipt on the failed row. The Export CSV button sits above the table and a footer note explains the 5 to 10 business day refund window and the 1-3-7 day retry sequence.
Payments are a typed const array with a union status field; the badge variant helper maps the status to secondary or outline. The Apr 1 failed row next to its Apr 3 retry makes the retry sequence visible without any extra explanation.
Reach for this block on the billing history page, wired to your charges endpoint. Show the most recent 6 to 12 rows by default and page or scroll for older ones. Wire the Export CSV button to your charge export route.
A natural flow around it on an Application Pro page:
Before
After
One strong use is a SaaS subscription charge ledger. Other payment table contexts:
Tip: showing one Failed row alongside the successful retry is the minimum needed to confirm the charge actually went through on the second attempt.