PaymentTagger
Flags payment / financial transaction endpoints. These routes carry direct monetary impact, so they are prime targets for business-logic flaws (amount/price tampering, currency confusion, negative amounts), IDOR on financial records, and replay. Surfacing them helps a reviewer focus on the highest-stakes surface.
Constants
Path segments that often — but not always — mean money: a DB "transaction", a newsletter/web-push "subscription", a battery "charge", a non-financial "withdraw"/"transfer", an unpaid "order". Require a corroborating money parameter before flagging.
Generic money parameters. Weak on their own (and so never trip the tagger by themselves), but enough to corroborate an ambiguous path.
Parameter names that strongly imply payment handling on their own (card data, gateway tokens, payment-method references, bank details).
Path segments that strongly imply a payment/financial surface.
Matched as whole path segments after splitting on /, -, _, ..
withdrawal(s) (the noun) stays here; the bare verb withdraw is
ambiguous (withdraw an application/registration/bid) and lives below.