Currency Minor Unit Lint for Payment API Amounts

It reads the file you have open and flags every line that builds a money amount the payment API will read differently from what you meant. Each finding gives the line number, the currency, its ISO 4217 exponent and, where a country changed codes, the date. It ships 24 rules.

Backend and platform engineers who write the charge call - the person who owns the repository the day finance asks why a Tokyo customer was billed a hundred times the price. It is aimed at teams selling into Japan, Korea, the Gulf states or the euro countries that recently switched currency codes.

Because the assistant writes Math.round(price * 100), which is correct for dollars and euros and wrong for the sixteen zero-decimal currencies. And it was trained before Bulgaria adopted the euro on 2026-01-01, so it still confirms BGN as a live currency code - the lev stopped being legal tender on 2026-02-01. A dated table does not have that blind spot.

Checking the open file is free and complete: all 24 rules run, every finding shows the currency and the date, and nothing is hidden or watermarked. The licence covers a different job - scanning every file in the repository, failing a CI build, exporting a report, and rewriting retired codes in place.

The extension is 29 US dollars once, with a 7-day full refund. Payment processors publish a fee of 15.00 dollars for every dispute received, and that fee is not returned when you lose. One mis-scaled charge produces a refund, a dispute fee and a support thread.