Operator guideEN

Configuration / Payment Methods Order

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

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 section is for

Use Configuration / Payment Methods Order to preview the score-based deposit-method order for a selected context and to manage manual override rules.

This screen does not create methods, enable methods, or define deposit and withdrawal limits. Those tasks belong to Configuration / Payment Methods.

Important preview limitation

The page is an operational ranking preview, not a complete per-player eligibility simulation:

  • the current CRM request always uses affiliate traffic
  • the live player flow derives affiliate status from the player
  • live player tags are applied after ranking and are not available in this preview
  • Currency selects score rows; it does not prove payment-method currency eligibility
  • active and hidden states have product-specific exceptions in the ranking path

Use the exact player country, currency, trust state, FTD/repeated state, tags, and attribution when validating cashier output.

How automatic ranking works

The score generator uses successful deposit history from the prior 90 calendar days. For each score context, the casino service ranks candidate methods by the aggregated score value and falls back to configured method order when score is zero or unavailable.

The visible Amount (EUR) value is the stored score aggregate. Its audited currency basis, exchange-rate timestamp, and rounding policy are not established by this screen. Do not use it as a financial total.

Successful deposits is displayed for context, but it is not the primary rank value.

Filters

  • Country
  • Currency, used as score context
  • Traffic Type: Primary/non-trusted or Secondary/trusted
  • FTD or repeated payment

Refresh and CSV

Refresh all existing lists requests score regeneration, then reloads the selected context. If the system setting disablePaymentScoreCollection is enabled, regeneration can return success without creating replacement scores.

Score regeneration is destructive and non-atomic: it clears the current score table before calculating and inserting replacement rows. A failed refresh can therefore leave no score rows or only a partial rebuild. Recheck the affected contexts after every refresh error.

The scheduled score process runs independently of this page. The traced scheduler is approximately every 22 hours, not a guaranteed nightly wall-clock run.

Export to CSV exports the rows currently loaded for the selected filters.

Manual override rules

Each rule selects a payment method, traffic type, FTD/repeated mode, position, optional countries, and optional dates.

  • a smaller Order value places the method higher
  • UI positions are one-based and stored zero-based
  • overrides are applied after score ordering
  • a matching country-specific rule wins over a global rule
  • a Date To without Date From does not become active
  • active dates are compared with the ranking service's server-local current day
  • otherwise equivalent rules have no deterministic relative precedence

Avoid duplicate matching rules. Saving the modal replaces the complete stored override set, so review every row before Save custom order.

What overrides cannot do

An override only repositions a candidate method. It does not make an otherwise ineligible method available and does not replace payment-method country, traffic, tag, or live player checks.

System switches

  • newAutomaticPaymentMethodsSortingType enables the score-based ranking path for live player deposits.
  • disablePaymentScoreCollection disables score collection even when a manual refresh is requested.

If the first switch is off, the player flow uses legacy ordering and can differ materially from this screen.

Access and operating recommendation

Limit override writes to payments, finance operations, conversion owners, or superadmins. Verify the whole override set, save once, refresh the target context, and test the live cashier before and after a high-impact change.

The backend permission family is Settings. Read operations require the route-specific read capability; score refresh and override changes require update capability. Verify the target role in the current environment rather than relying on menu visibility alone.

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 calculations6 topicsOpen details

casino-side-ranked-order

Reads the player-facing ranked list through the Backoffice request path.

Formula
Rank eligible deposit methods for the selected currency, country, deposit stage, trust state, and affiliate context.

score-window

Produces the recent score rows used by the ranking path. The exact audited EUR rate basis is not established.

Formula
Aggregate successful deposit amount divided by stored conversion rate for the prior 90 calendar days, grouped by country, score currency, trusted state, and FTD state.

score-ranking

Successful-deposit count is displayed but is not the primary rank value.

Formula
Rank candidate methods by the summed trusted score value; use configured payment-method order when no positive score determines position.

live-player-gate

Explains why CRM preview can differ from the actual cashier.

Formula
Use score ordering for deposit requests only when newAutomaticPaymentMethodsSortingType is enabled, then apply player tag visibility.

override-normalization

Normalization applied before override rows are saved in bulk.

Formula
trafficType 'all' -> null, isFirstDeposit 'both' -> null, countries -> sorted JSON, order -> zero-based integer, date strings -> ISO timestamps or null

override-precedence

Other equally matching rows have no explicit stable precedence.

Formula
Apply matching overrides after score order; prefer a matching country-specific rule over a global rule for the same method.
Filters4 topicsOpen details

Country

Chooses the country context for the ranked deposit-method list.

Type
select

Currency

Chooses the score-row currency context for the ranked deposit-method list. Current default is EUR.

Type
select
Caveats
This filter does not prove that the method is eligible for the same player wallet currency.

Traffic Type

Switches the ranking between Primary/non-trusted traffic and Secondary/trusted traffic.

Type
select

FTD or repeated payment

Switches the ranking between first-deposit and repeated-deposit traffic.

Type
select
Metrics3 topicsOpen details

Amount (EUR)

Recent successful-deposit score aggregate used to rank methods in the selected country, currency, trust, and deposit-stage context.

Aliases
payment method ranking amount, payment score amount
Filter Dependencies
country, currency, trusted, is_first_deposit
Currency Basis
Reporting Label: EUR | Conversion: Included successful deposit amounts are divided by the stored conversion rate before aggregation. | Rate Source: not_proven | Rate Timestamp: not_proven | Rounding Boundary: not_proven | Missing Rate Behavior: not_proven
Caveats
Treat this as a ranking score, not as a reconciled financial total., The displayed EUR basis remains unverified.

Initiated deposits

Successful plus failed deposit attempts stored for the selected ranking context.

Aliases
payment method initiated deposits, payment score attempts
Formula
success_count + fail_count
Filter Dependencies
country, currency, trusted, is_first_deposit

Successful deposits

Successful deposit count shown for context; the ranking itself uses the score amount rather than this count.

Aliases
payment method successful deposits, payment score success count
Filter Dependencies
country, currency, trusted, is_first_deposit
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.

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.

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.

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.

Affiliate Deals / List

Searchable table of affiliate deal rows with PID filter, create action, dashboard shortcut, and edit/delete row actions.