What problem does it solve? Fintech GraphQL APIs sit in front of ledgers, wallets, and payment systems where a single resolver bug can move real money, yet generic GraphQL testing guidance misses the financial-specific attack surface like decimal rounding abuse, idempotency replay, and source-account authorization gaps. ## Core Features & Use Cases - Money-Movement Mutation Testing: Systematically maps and probes transfer, withdrawal, redemption, and top-up mutations for idempotency-key replay, double-spend via alias batching, and non-atomic ledger writes. - Decimal & Precision Abuse Probes: Tests custom Money/Decimal scalars with sub-cent amounts, scientific notation, oversized values, and negative amounts to expose rounding drift and float-parsing fallbacks. - Fintech-Specific Authorization Checks: Detects asymmetric source-account IDOR, nested KYC/PII field-level authorization gaps, and admin-tier mass assignment on transaction input objects. - Use Case: When assessing a neobank or brokerage target exposing a GraphQL endpoint, use this methodology after generic schema discovery to test whether transferFunds validates source-account ownership and whether replayed idempotency keys produce duplicate ledger writes. ## Quick Start Ask the AI to hunt fintech-specific GraphQL vulnerabilities on an authorized bug bounty target that exposes balance, transfer, or ledger mutations.