What this module is for

Payment Methods is the backoffice area where operators maintain the internal catalog of deposit and withdrawal methods that can later appear in player payment flows.

This module covers three different operator jobs:

• keeping the master catalog of methods and provider variants up to date
• maintaining per-method rules such as visibility, restrictions, card and crypto behavior, and traffic gating
• checking or overriding the player-facing order used for deposit methods in specific traffic and country contexts

Surface map

• List: filterable catalog with status badges, quick stats, create/edit actions, delete, JSON import/export, and global order save
• Form: modal editor for create and update, including JSON mode and logo upload
• Reorder: separate screen for scored payment ordering and custom override rules used in player-facing deposit ranking

When operators usually open this module

• a new provider or method variant must be added
• a method should be hidden, disabled, or limited to specific countries or currencies
• deposit or withdrawal rules need to change
• crypto-specific settings such as network behavior or QR-flow toggles need to be adjusted
• player-facing payment ordering must be checked for a country, currency, or traffic segment

Main configuration groups

Identity and player-facing copy

• Name and Payment Method identify the internal provider/method row.
• Raw Title can be displayed directly.
• Title and Description are resource keys, not long free-text copy.
• Thumbnail or icon assets provide cashier imagery.

Amount limits

• minimum and maximum deposit in EUR
• minimum and maximum withdrawal in EUR
• optional currency-specific deposit and withdrawal ranges

Blank numeric values can be stored as null. Always test the intended currency after changing a range.

Country, currency, and player targeting

• allowed and restricted countries
• allowed and restricted currencies
• allowed email addresses
• include and exclude player tags
• FTD/repeated traffic mode
• Trusted Only
• Affiliate Only

These controls combine with downstream player, provider, and payment-flow checks. The catalog form is not a complete eligibility simulator.

Method behavior

• active and hidden state
• bank, email, card, and crypto form types
• withdrawal and bonus flags
• saved cards for deposit or withdrawal
• require a prior deposit before withdrawal
• parent payment group and network-specific child behavior

Safe create or edit process

1. Confirm the provider code and intended player-facing name.
2. Configure deposit/withdrawal purpose, amount limits, countries, currencies, and traffic rules.
3. Enable only the form-type flags required by the provider flow.
4. Review Include/Exclude Tags and Trusted/Affiliate restrictions.
5. Save the row.
6. Test the exact country, currency, authentication, FTD/repeated, trust, affiliate, and tag scenario in cashier.
7. If player ordering matters, validate it separately in Payment Methods Order.

Common confusion points

• Hidden and Inactive are not the same thing. The page exposes both because they change visibility differently.
• The main Payment Methods page saves the internal global order on the payments table. The separate Payment Methods Order screen is about player-facing ranking logic and override rules.
• Crypto parent methods and crypto child methods are shown together, but they do not behave like a normal flat list.
• Some top cards on the list page are only orientation stats, not financial analytics.
• GatewayCrypto static QR flags are configuration switches for the downstream player payment flow. They should be changed only on the intended GatewayCrypto rows.

Groups, ordering, and JSON

Create Group uses the same editor to create a parent grouping row. A parent with child methods cannot be deleted until the children are removed or reassigned.

Save Order on the catalog updates the global stored order. It is different from the score-based, context-aware Payment Methods Order screen.

Edit as JSON is an advanced bulk editor. Review the whole payload before applying it because it bypasses the normal grouped form layout.

Access recommendation

The backend permission family is Settings, with route-specific read, create, update, and delete capabilities for the payment-method operations. Restrict write access to payments, finance operations, product/conversion owners, or superadmins, and verify actual role behavior in the target environment.

Changes can remove deposit or withdrawal options for a player segment. Avoid uncoordinated changes during peak traffic and validate cashier behavior immediately after save.