Start with processor settings
Use the audit next to the payment integrations page so Stripe, PayPal, TaxJar, Avalara, test mode, and payment options stay visible.
Free audit · local import · remembered on this device
See what Stripe is really costing you.
Upload your Stripe payments export and get a concrete fee, failed-payment, refund, FX and country-mix report in about 30 seconds.
Processing feesFailed revenueFX exposure
Stripe payments CSV
Import the export
Processed in your browser. Plandalf does not receive the CSV.
1Upload export
Use the standard Stripe payments CSV.
2Review the audit
Fees, failed payments, refunds, country mix and FX.
3Return later
Your current import restores on refresh.
Use the audit to improve the payment stack, not just read fees.
The useful Stripe audit path connects the Stripe payments export to payment options, products, prices, subscriptions, checkout, invoices, webhooks, and the post-purchase Automations that depend on payment state.
Map costs back to products and prices
A fee audit is only useful when it leads back to products, prices, subscriptions, coupons, checkout choices, and offer packaging.
Keep invoices and payment records attached
After the Stripe audit, compare fees against invoices, payment state, product lines, tax, coupons, buyer context, and follow-up events.
Turn the finding into an offer change
The audit should flow into Offers so products, prices, checkout templates, coupons, invoices, payment state, and purchase events stay connected.
Check integrations before changing the stack
Payment costs often involve integrations: Stripe, PayPal, tax tools, CRM, fulfilment, webhooks, API docs, and reporting workflows.
Use docs when the audit becomes engineering work
API docs, SDK checkout, webhooks, and checkout events help an engineer route fee, payment, invoice, and fulfilment data into custom systems.
Keep these pages open after the CSV result.
Once the calculator shows the real Stripe rate, use these resources to decide whether to change payment processors, adjust prices, improve invoices, wire webhooks, or rebuild checkout through the API-first stack.