Skip to content
faker.tools
All 79

Plate III · Financial, E-Commerce & Retail Stubs

Transaction Log Generator

Charges, refunds, chargebacks and failures with a configurable failure rate.

#Transaction IDTypeAmountCurrencyStatusTimestampCustomerCustomer IDMethod
1txn_zkr0kydh9dm21h32qlm9aio5payout$642.82USDsucceeded2026-09-24 23:05:14Kevin Garciacus_ALBJ8SE62EF5BBbank_transfer
2txn_1jcozg4slixk7bh7ljuk4ym0chargeback$-628.13USDsucceeded2026-08-06 04:17:18Mary Jonescus_HBWLXTSXBXJJ5Pcard
3txn_38qp5liqphgcincwd559gpv0charge$842.65USDsucceeded2026-08-31 10:57:49Sarah Thomascus_6Y1AHGPNCNMHVJcard
4txn_1u6y6g6dp8qgexcvladwb8qqcharge$639.08USDsucceeded2026-10-20 10:18:42Anthony Williamscus_YPNFF2L2HHSP93card
5txn_4srzuivj836whhnxsxbjhy1hcharge$235.53USDsucceeded2026-09-16 01:20:10Patricia Nelsoncus_RCPTWUQG1DB01Xcard
6txn_4bznbupgf0jcjooc6ptvdceqcharge$243.52USDsucceeded2026-07-29 17:25:16Caleb Adamscus_WYMGZ05CWNMF3Ucard
7txn_52m68mfdgh8vwdums3aj54itpayout$331.86USDsucceeded2026-09-08 00:42:14Karen Jacksoncus_KTEBYXDF86HHKTcard
8txn_f6xxkswab3rigkffhwk2rslxpayout$844.12USDsucceeded2026-08-01 17:23:59Miles Nguyencus_U634NSJ5JGWYB7card
9txn_8244bnjrwsvlfx5q53rf3exxcharge$800.89USDsucceeded2026-08-23 19:27:32Ruth Thompsoncus_Y1ENEQPQE6Y2XScard
10txn_ph0nvv7v5z03lo9jz6y52cytcharge$737.68USDpending2026-08-29 13:42:13Thomas Martincus_RR8UHX72MZ4KN4card
10 rows · 2.0 KBGenerated in your browser · Transaction Log Generator

Payment code is mostly failure handling, and a fixture of successful charges never touches it. Set the failure rate to twenty per cent and a fifth of your batch arrives as declines, insufficient funds and expired cards.

What you can control

  • The failure rate is a direct control, so you can produce a batch that is mostly declines if that is the path you are testing.
  • Refunds and chargebacks carry negative amounts, which is where sign handling in a ledger sum breaks.
  • Three transaction mixes — retail, bank ledger and subscription billing — each with the columns that context needs.
  • The time window spreads transactions over anything from a day to two years for testing date filters.

Testing ideas

  • Failure rate. Raise the failure rate to 20% and check that dashboards, retries and alerting behave when failures are common.
  • Refunds and chargebacks. Keep them on to test reconciliation: a refund references an earlier payment, and totals should net it off.
  • Date spread. Spread transactions over 730 days to test date filters, monthly grouping and year boundaries.
  • Mixes. Switch between retail orders, a bank ledger and subscription billing to fit the screen you are building.

What this is not

Amounts convert at fixed indicative rates and each transaction is independent, so a running balance across rows will not reconcile. For a coherent ledger, generate in bank mode and recompute the balance yourself.

Questions

Do the balances add up across rows?

No. Each transaction is generated independently, including the balance-after column in bank mode. Recompute it from the amounts if you need a consistent ledger.

Why are refunds negative?

Because that is how most ledgers store them, and summing a column that mixes signs is where naive revenue calculations go wrong.

What do the failure statuses represent?

The common decline reasons a card network returns — declined, insufficient funds, expired card. Each usually needs a different message in your interface.

Next in Finance

All 11 →