On 28 August 2026 Amazon removes the Finances v0 API. If your reporting still calls it, your payouts stop reconciling the day it goes dark. I migrate you to listTransactions and make every fee, refund and reserve tie out to the payout — cleanly, by text, no calls.
Paste your integration or point it at your code — it flags every Finances v0 call that breaks on 28 Aug, with the listTransactions replacement for each.
Run the scanner →Upload a settlement report and it reconciles payout vs line items client-side — catching the fees with no order id that quietly break the total.
Reconcile a report →The full v0 → listTransactions field map, the reconciliation edge cases, and the removal timeline — the reference I use on real migrations.
Get the guide →Working listTransactions client, a v0 → new field mapper, a reconciliation checklist and a runnable example that ties a payout to the cent — including the fee-with-no-order-id case.
Get the kit →Parses the flat-file settlement report into clean, typed rows — payout total, balances, per-type breakdown and the unassociated fees — ready to reconcile in your own stack.
Get the parser →Run the free scanner first. It tells you exactly how much of your code touches v0 — then the kit above closes the gap. Still unsure, just message me.
Ask me →Not ready to commit to a full migration? Send me one settlement report and your v0 exposure. I send back, in writing, exactly where your numbers stop tying out and what the cut-over breaks — the fees with no order id, the payout-level gaps. If you then go done-for-you, the €90 comes off the price.
I migrate your integration before the deadline and prove it reconciles against real payouts, not a demo.
Amazon owes most sellers money — lost or damaged inventory, wrong-dimension fees, return errors. I find it by reconciliation and you file within Amazon's own process.
Tell me your SP-API setup and one payout that looked off — I'll tell you, in writing, where it stops reconciling. Then we fix it before the deadline.
Email me ↗