Operator guideEN

Payments Orientation

Operator map for payment-related CRM areas: payment-method setup, transaction investigation, withdrawals, automatic withdrawal rules, and affiliate payment settings.

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

Use this page as the payment-operations map before opening a more specific guide.

Where to go

  • Payment Methods: configure the internal catalog of deposit and withdrawal methods, logos, method rules, global order, JSON maintenance, and player-facing order overrides.
  • Transactions / Banking: inspect deposit, withdrawal, bonus, correction, and provider-related banking rows.
  • Transactions / Withdrawals: process withdrawal queues and postponed withdrawal actions such as moving a row back to pending, approving a postponed withdrawal, or rejecting a postponed withdrawal.
  • Transactions / Failed Deposit: investigate failed payment attempts and provider error groups.
  • Transactions / KYC: review KYC transaction and document workflow.
  • Settings / Automatic Withdrawal: configure automatic-withdrawal rules and review processed or non-qualified withdrawal queues.
  • Settings / Affiliate Payment Settings: configure affiliate payout settings and sending windows.

Common confusion points

  • Payments is a business area, not a single confirmed Backoffice screen in the current docs map.
  • A generic Approve Payment action is not documented as a real standalone payment action. The verified approval-style action currently belongs to the withdrawal queue as Approve Withdrawal for postponed withdrawals.
  • A generic Retry Provider Call action was not found in the current Backoffice payment surfaces. If an operator needs provider recovery, start from the relevant transaction detail or failed-deposit surface and follow the documented action there.
  • Payment-method configuration changes what players can see or use. It does not approve, retry, or settle an existing transaction.
  • Withdrawal automation rules decide eligibility for automatic processing. They are not the same as manual withdrawal queue actions.

Current coverage

  • This is an orientation page for payment-related work across CRM, not a standalone payment grid.
  • The child pages carry the detailed fields, actions, formulas, and caveats for their own workflows.
  • No standalone generic Approve Payment or Retry Provider Call action is documented at this business-area level; start from the specific transaction or withdrawal surface when troubleshooting a concrete payment row.
More help

Related pages

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.

Affiliate Payment Settings / Detail

Detail/edit shell for one saved affiliate payment-setting record.

Affiliate Payment Settings / Form

Create and edit form for one affiliate payment-setting record, with visible PID targeting, minimum deposit threshold, and active-state control.

Affiliate Payment Settings / List

Affiliate payment settings inventory page for reviewing configured rows and opening saved records.