Classification & payment methods
Use the approved Reporting fields and branch requirements.
Classification #
Report creation requires a supported scam classification. Prefer scam_type. A compatible taxonomy path may use scam_category, scam_group, and scam_subtype. If both group and subtype are present, the subtype must belong to that group. Use canonical snake_case names; consult OpenAPI for allowed values.
Payment branches #
| payment_method | Required data |
|---|---|
| bank_transfer | type = bank_account; identifier; bank_code; reported_account_name |
| crypto | type = crypto_wallet; identifier; payment_submethod; payment_details |
| card_payment | reported_account_name; payment_details.card_used_at |
| online_payment_gateway | reported_account_name; payment_submethod |
| pos_agent_payment | reported_account_name; supported POS payment_submethod; payment_details.agent_location |
| other | Nonempty narrative |
Submethods #
Crypto payment_submethod: bitcoin_btc, usdt_tether, ethereum_eth, bnb, other. If other, payment_details.crypto_type_other is required. Optional payment_details.network follows OpenAPI bounds.
Gateway payment_submethod: paystack, flutterwave, interswitch, monnify, remita, voguepay, etranzact, nomba, squad, other. If other, payment_details.gateway_other is required.
For POS other, provider_other is optional but must be valid when present. The canonical OpenAPI defines supported POS submethods.
Bounded payment details #
payment_details is a bounded canonical subset: at most four top-level properties, at most one nested-object level, and at most four properties in a nested object. Arrays are not allowed. Use canonical safe property names and OpenAPI-bounded scalar values.