Check compatibility first
Native Stripe and bank exports are not qualified. The preview requires the exact normalized headers shown in the interface. It checks supplied itemized amounts, declared payouts and explicitly mapped bank receipts; it does not infer which bank deposit belongs to a payout.
USD, EUR and GBP, exact dot-decimal major units with at most two fractional digits, and only charge/refund/fee detail categories. Each selected payout requires one positive paid automatic payout and one independently verified, explicitly mapped receipt. The normalized method=automatic value is our internal schema, not a native Stripe API value.
Each file is limited to 5 MB and 10,000 rows. No API key, login or payment is needed. Files remain in browser-tab memory; there is no file upload, file-content telemetry or session persistence. Clearing or reloading discards the selection. Downloaded reports remain on your device. Browser extensions and device security software operate independently.
Start with the fictional example
- Open the preview and choose Load synthetic example.
- Read the complete-selection assertion, then run the review. The example declares a payout of 95.92 USD and a bank receipt of 95.91 USD.
- Inspect the visible -0.01 USD mismatch and download the complete JSON/CSV. The JSON retains money as exact decimal strings.
Those are invented test records. The example does not establish native compatibility, bank receipt, customer demand or accounting approval.
A voluntary independent trial
We are evaluating whether this bounded workflow saves useful review time compared with your existing Stripe report, spreadsheet or script. If you already have a compatible task and are authorized to process the data, run the preview on your own device and compare the result with your originals. Preserve your complete original exports; a matching result cannot prove that data was complete or authentic.
Useful feedback is a non-sensitive account of the task, your existing method, approximate time for both methods, any missed or false finding, and which limitation prevented use. An explanation of why your existing free tool is sufficient is useful too. Trying the example does not commit you to a purchase or a follow-up.
Share a non-sensitive trial result or ask about joining →. Mention PLG pilot in your message. The existing contact form stores the details you choose to submit and asks for consent to respond. Do not include transaction/customer identifiers, CSV/PDF files, account details, credentials or a payment instruction. We do not offer incentives or promise a response time.
Visible limits
No native bank parser, account connection, automatic matching by date/amount, FX, Connect, disputes/reserves, manual/instant payouts, split/combined deposits, accounting import or posting, tax decision, payment approval or authenticity assurance. The experiment is freely inspectable; no licensed paid edition or commercial offer has been activated.
Questions about data handling: privacy policy. For an existing released tool, return to the four-product collection.