Operator guideEN

Payment Methods / List

Filterable catalog view for payment methods, provider variants, top-level status cards, and quick actions such as create, edit, delete, JSON import/export, and global order save.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

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 Only or Affiliate 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, provider Payment 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

  • Name
  • Payment 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 same system catalog service as the list, but their trend values are not reliable business trends.

The current 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 activeMethods and newMethods in 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.
  • Do not treat name + paymentMethod as the unique identity. Stable identity is the saved payment row/id, because similar names can exist for different targeting contexts.
  • Save Order rewrites the stored global order. If the save is interrupted after reset, operators should reload and save again before assuming the order is stable.
  • JSON import/export is useful for admin maintenance, but it bypasses the normal form grouping and should be reviewed carefully before saving.
More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Source calculations3 topicsOpen details

withdrawal-enabled-percentage

Used for the percentage subtitle on the withdrawal-enabled card.

Formula
(withdrawalCount / totalCount) * 100

type-distribution

Builds the card/chart distribution dataset for method types.

Formula
Bank = count(isBank), Card = count(isCardForm), Crypto = count(isCryptoForm), Email = count(isEmail), Other = total - known typed counts

monthly-trend-dataset

Backend returns created-at counts per month for the orientation trend block.

Formula
count(payments.createdAt within each of last four months)
Fields17 topicsOpen details

Name

Internal identifier used by operators and backend integrations.

Data Type
string

Payment Method

Provider or method code used to distinguish integrations under the same internal family.

Data Type
string

Title

Operator-facing or player-facing display title when the integration uses a formatted title.

Data Type
string

Raw Title

Unformatted title variant often used for grouping or provider naming.

Data Type
string

Active

Controls whether the method is active in the catalog.

Data Type
boolean

Hidden

Hides the method without making it the same thing as inactive.

Data Type
boolean

Withdrawal Enabled

Shows whether this method can be used for withdrawals.

Data Type
boolean

Type badges

Quick classification badges used to understand the kind of payment flow.

Data Type
badge-set

Trusted Only

Limits the method to trusted-player traffic only.

Data Type
boolean

Affiliate Only

Limits the method to affiliate-attributed traffic only.

Data Type
boolean

Allowed Countries

Explicit allowlist of countries for the method.

Data Type
string-list

Restricted Countries

Explicit denylist of countries for the method.

Data Type
string-list

Allowed Currencies

Explicit allowlist of currencies for the method.

Data Type
string-list

Restricted Currencies

Explicit denylist of currencies for the method.

Data Type
string-list

Thumbnail

Logo or icon shown for the method.

Data Type
asset-url

Parent

Parent group name used for crypto network children.

Data Type
string

Global Order

Global admin order stored on the payment row and saved from the list page.

Data Type
integer
Filters2 topicsOpen details

Name

Filters the catalog by the internal payment-method name.

Type
text

Payment Method

Filters the catalog by the provider/payment-method identifier.

Type
text
Summary cards4 topicsOpen details

Total Methods

Total number of payment rows in the catalog.

Active Methods

Number of rows marked active in the catalog.

Group Count

Number of methods marked as crypto group parents.

Withdrawal Enabled

Number of methods where withdrawals are enabled.

Metrics4 topicsOpen details

Total Methods

Total number of payment rows in the admin catalog.

Aliases
payment methods total, how many payment methods, payment catalog size
Formula
COUNT(*) FROM payments

Active Methods

Number of catalog rows where `isActive` is true.

Aliases
active payment methods, enabled payment methods
Formula
COUNT(*) WHERE isActive = true

Group Count

Number of payment rows flagged as crypto parent groups.

Aliases
crypto groups, payment groups
Formula
COUNT(*) WHERE isCrypto = true

Withdrawal Enabled

Number of methods where withdrawals are enabled, plus a percentage of the full catalog.

Aliases
payout methods enabled, methods with withdrawal
Formula
COUNT(*) WHERE withdrawalExist = true
Comparison Notes
Percentage is calculated against total catalog size on the same service response.
Notes2 topicsOpen details

These cards are catalog health indicators, not financial analytics.

Current trend values are orientation-only and should not be described as reliable historical business trends.

More help

Related pages

Configuration / Payment Methods

Operator guide for the internal payment-method catalog, the create/edit flow, and the player-facing ordering tools used in backoffice.

Configuration / Payment Methods Order

Preview score-based deposit-method ranking and manage manual country, traffic, and FTD overrides.

Payment Methods / Form

Full create and edit flow for payment methods, including normal form mode, JSON mode, logo upload, geo/currency restrictions, amount rules, and crypto-specific toggles.

Activity Tag Rules / List

Main inventory for activity-driven tag rules, with search, activity and status filters, grouped rows, clone, edit, and run actions.

Affiliate Deals / Dashboard

Affiliate deal cohort report that period-bounds registrations, then combines the selected players with cumulative deposit and linked-event values.

Affiliate Deals / Form

Create and edit form for affiliate deals, including PID, date window, commercial terms, and responsible person.