Page body
What this page shows
This screen is the working catalog for payment methods. Operators use it to inspect the current set of methods, filter the list by internal name or provider name, and open the create or edit flow.
At the top of the screen, the page shows orientation cards such as total methods and active methods. Below that, the catalog is rendered as grouped cards rather than a classic table.
When to use it
- check whether a payment method is active, hidden, or withdrawal-enabled
- review traffic restrictions such as
Trusted OnlyorAffiliate Only - confirm which countries or currencies are explicitly allowed or restricted
- create a new payment method or edit an existing one
- remove a method that is no longer valid
- export or bulk-edit the catalog in JSON format
How to read it
The page is organized around the method card itself:
- identity fields such as internal
Name, providerPayment Method, and visible title - status badges such as active, hidden, withdrawal, bank, card, email, crypto, bonus, trusted-only, and affiliate-only
- geo and currency restrictions
- optional child methods when the item acts as a crypto parent group
For crypto groups, the parent entry is shown first and the network-specific child entries appear under it.
Filters that change the result
NamePayment method
These are text filters only. The page does not currently expose country, currency, or status filters on the main catalog route.
Why values can be confusing
Stats cards are orientation-only
The top cards come from the backend stats action on the same CRUD service, but their trend values are not reliable business trends.
The current backend implementation:
- generates card trends with a random helper
- builds the last-four-month trend dataset from created-at counts
- uses the same monthly count for both
activeMethodsandnewMethodsin the chart data
Operators should treat the cards as quick catalog health indicators, not as historical performance reporting.
Order on this page is not the player-facing order
Save Order on this page updates the global payments.order field. It does not replace the country- and traffic-aware ranking shown on the separate Payment Methods Order screen.
Known caveats
- Deleting a crypto parent fails if child methods still exist under that parent.
- Duplicate
name + paymentMethodcombinations are blocked by the backend. - JSON import/export is useful for admin maintenance, but it bypasses the normal form grouping and should be reviewed carefully before saving.
Verification status
- status:
verified_backend - FE mapping checked from
paymentMethods.tsx - backend CRUD and stats path checked in
CrudPaymentMethodService