A useful example, with the checks in view
SYNTHETIC INPUTS · NO CUSTOMER DATAA neat pack still needs a factual review.
Practice arranging clearly labeled synthetic records, then distinguish source size from the generated evidence size and page count.
Practice files, never submission evidence
These original PDFs are explicitly marked synthetic and contain no customer details. They exist to exercise the organizer’s file and page checks. Do not submit them to a payment processor or describe them as real records.
Build a factual practice pack
- Open DisputePack. Use a reference such as “SYNTHETIC PRACTICE.” Leave unknown case details blank. No real dispute is needed.
- Choose Mastercard to exercise the 19-page check. This is a test setting, not a claim about a real card network or transaction.
- Under Evidence, choose the receipt evidence type and select the one-page fictional receipt. Enter only facts present in that file. Do not invent a customer exchange or delivery event.
- Go to Review, read the checklist and acknowledgements, then build review files. Inspect the generated evidence PDF and the separate worksheet.
- Start a fresh practice case for each boundary fixture. The 19-page source tests the page boundary. The 20-page source should prevent evidence downloads for Mastercard. The large synthetic image tests a generated file above the byte ceiling.
Which size actually counts?
Generated evidence PDFs can be larger or smaller than the source files. DisputePack totals the evidence outputs, not just the uploaded bytes. It keeps the review worksheet separate from the submission ZIP.
| Checked fixture | Observed evidence output | Result for Mastercard |
|---|---|---|
| 1-page PDF | 925 bytes · 1 page | Within both limits |
| 19-page PDF | 6,514 bytes · 19 pages | Within both limits |
| 20-page PDF | 6,821 bytes · 20 pages | Over the page limit |
| 1,500 × 1,100 synthetic PNG | 4,952,525 bytes · 1 page | Over the byte limit |
Observed October 11, 2026 with the actual inspect and merge functions in Node; outputs were reopened to count pages. Size/page decisions were checked against the production app’s conditions. This was not a browser UI or processor-submission test. PDF metadata timestamps can change exact byte counts on later runs.
Current reference limits
Stripe’s guidance states a 4.5 MB combined evidence-file maximum and a 19-page combined limit for Mastercard. The app conservatively interprets 4.5 MB as 4,500,000 bytes and checks the sum across evidence PDFs.
Read Stripe’s responding-to-disputes guidance ↗
Reference checked October 11, 2026. Verify current requirements in your real case before submission.
A pass is only a file check
Passing size and page checks says nothing about the record’s truth, relevance, completeness or ability to support the case. The tool cannot verify signatures, judge the claim or predict an outcome.
Stripe permits one submitted response that cannot later be amended. Review the actual requested evidence types and fields yourself.
When to stop and review the source
- A source has signatures, forms, annotations, active content, embedded files or encryption. This tool rejects detected structures instead of silently removing them.
- The page is illegible, missing context or says something different from your notes. Repair the record trail, not the narrative.
- You only have an external link. Keep the relevant authentic record; the tool does not retrieve or certify third-party content.
- A file contains secrets, card numbers or identity documents. Do not add unnecessary sensitive information.
Ready to try it?
Every feature and export is free. No account is needed. Start with a practice file, then keep your real inputs local.