Operator guideENcrmpaymentsformcrud

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.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this form does

The form creates or updates one payment-method record. It is used for both simple provider rows and more complex card or crypto flows.

Operators can work in two modes:

  • regular form mode
  • JSON mode for direct structured editing

The same shared modal is also used for four operator entry points:

  • Add Method
  • Edit Payment Method
  • Create Group
  • Edit Payment Group

Group mode is still the same payload editor, but it starts from a different default state and is aimed at parent/group rows instead of standalone methods.

When to use it

  • add a new provider or method variant
  • change display titles or descriptions
  • switch a method on or off
  • set country, currency, email, or traffic restrictions
  • configure card or crypto-specific behavior
  • upload or replace the method logo
  • create or maintain a payment group that other rows can attach to through Parent Group

How to read it

The form is easiest to think about in sections:

  • identity: name, provider, title resource key, raw title, description resource key
  • core status: active, hidden, withdrawal enabled, bonus flag
  • method type: bank, email, card, crypto, payment-group behavior, network behavior
  • limits and defaults: default amount, bottom-amount helper text, EUR limits, and per-currency ranges
  • targeting: country, currency, email, and traffic restrictions
  • copy blocks: deposit and withdrawal text blocks used by player-side payment UX

What usually confuses operators

JSON mode is powerful but bypasses the grouped form layout

JSON mode is useful for advanced edits or structure review. It should be used carefully because it exposes the raw payload that will be posted to the backend. The modal also exposes helper actions to format, copy, download, upload, and re-apply JSON back into grouped form mode.

The FE does not save invalid JSON. Apply & Switch to Form is blocked until the JSON parses successfully.

Title and Description are resource keys, not plain content fields

The visible labels are Title (key from Resources) and Description (key from Resources). Operators should enter resource keys that map to translation resources, not long free-text copy.

Payment groups are configured from the same modal

The same create/edit surface is also used for Create New Group and Edit Payment Group. The Is Payment Group switch changes the row into a parent/group record and affects how child rows use the Parent field.

Create Group also starts from group-oriented defaults in the FE:

  • isCrypto: true
  • name: new-group
  • rawTitle: New Group
  • title: New Payment Group
  • isActive: true

Card and crypto toggles unlock extra fields

Options such as saved-card behavior or QR/static-network behavior matter only when the corresponding form type is enabled.

Traffic flags are not the same thing

  • Allowed Traffic Type controls broad traffic targeting
  • Trusted Only narrows to trusted traffic
  • Affiliate Only narrows to affiliate-attributed traffic

The FE also forces Trusted Only off for some traffic selections and disables it for traffic modes where the combination is not allowed.

Known caveats

  • The backend enforces uniqueness on the name + paymentMethod combination.
  • FE validation only hard-requires Name. The modal does not require Payment Method, Title, or Description before save.
  • The list page, not the form page, owns delete.
  • Some numeric fields allow blank values, which the hook converts to null before submit.
  • Gateway Crypto Static QR Next Step can be auto-enabled in the FE when Gateway Crypto Static QR Flow is enabled for the gatewaycrypto method name.
  • Traffic Type can forcibly clear and disable Trusted Only for combinations the FE does not allow.

Verification status

  • status: verified_backend
  • FE mapping checked from the shared modal editor in paymentMethods.tsx
  • backend create and update paths checked in CrudPaymentMethodService
Field dictionary

Fields

field

Name

Internal method identifier. This is the only field the FE hard-requires before save.

Group
identity
Data Type
string
field

Payment Method

Provider or method code paired with the internal name for uniqueness and routing. It is not FE-required, but still matters for backend uniqueness and routing.

Group
identity
Data Type
string
field

Title

Resource key used for the display title. The FE labels this field as `Title (key from Resources)`.

Group
identity
Data Type
string
field

Raw Title

Raw grouping title often used for provider-family naming.

Group
identity
Data Type
string
field

Description

Resource key used for the display description. The FE labels this field as `Description (key from Resources)`.

Group
identity
Data Type
string
field

Active

Enables the method in the catalog.

Group
status
Data Type
boolean
field

Hidden

Hides the method without making it identical to inactive.

Group
status
Data Type
boolean
field

Withdrawal Enabled

Allows the method to appear on withdrawal flows.

Group
status
Data Type
boolean
field

Bonus

Marks whether the method participates in bonus-enabled flows.

Group
status
Data Type
boolean
field

Bank

Marks the method as bank-based.

Group
method-type
Data Type
boolean
field

Bank Form (Withdrawal Only)

Shows the bank-form variant only on withdrawal flows while leaving deposit behavior unchanged.

Group
method-type
Data Type
boolean
field

Email

Marks the method as email-based.

Group
method-type
Data Type
boolean
field

Card Form

Enables card-form behavior and saved-card sub-options.

Group
method-type
Data Type
boolean
field

Saved Cards (Deposit)

Allows saved-card reuse on deposits.

Group
method-type
Data Type
boolean
field

Saved Cards (Withdrawal)

Allows saved-card reuse on withdrawals.

Group
method-type
Data Type
boolean
field

Require Deposit For Withdrawal

Requires an earlier deposit before using this method for withdrawal.

Group
method-type
Data Type
boolean
field

Crypto Form

Enables crypto-specific inputs and QR/network options.

Group
method-type
Data Type
boolean
field

Currency

Default crypto currency code when the method is crypto-related.

Group
crypto
Data Type
string
field

Is Crypto Network

Marks the row as a concrete crypto-network option.

Group
crypto
Data Type
boolean
field

Parent Group

Parent group title used when the row belongs to a payment group.

Group
crypto
Data Type
string
field

Is Payment Group

Marks the row as a parent/grouping record edited through the same modal as normal payment methods. `Create Group` opens the form with this already enabled.

Group
crypto
Data Type
boolean
field

Default Amount

Default amount suggested in the payment flow.

Group
limits
Data Type
string
field

Text Bottom Amount

Helper text shown under amount controls for integrations that display a bottom-amount note.

Group
limits
Data Type
string
field

Min Deposit EUR

EUR-denominated minimum deposit value.

Group
limits
Data Type
amount
field

Max Deposit EUR

EUR-denominated maximum deposit value.

Group
limits
Data Type
amount
field

Min Withdraw EUR

EUR-denominated minimum withdrawal value.

Group
limits
Data Type
amount
field

Max Withdraw EUR

EUR-denominated maximum withdrawal value.

Group
limits
Data Type
amount
field

Currency Ranges

Per-currency override for min/max deposit and withdrawal values.

Group
limits
Data Type
object-list
field

Allowed Countries

Explicit country allowlist.

Group
targeting
Data Type
string-list
field

Restricted Countries

Explicit country denylist.

Group
targeting
Data Type
string-list
field

Allowed Currencies

Explicit currency allowlist.

Group
targeting
Data Type
string-list
field

Restricted Currencies

Explicit currency denylist.

Group
targeting
Data Type
string-list
field

Allowed Emails

Email-level allowlist used for restricted rollout cases.

Group
targeting
Data Type
string-list
field

Allowed Traffic Type

Traffic segment rule such as FTD-only or repeated-only.

Group
targeting
Data Type
enum
field

Trusted Only

Restricts the method to trusted traffic only. The FE disables and clears it for traffic modes where the combination is not allowed.

Group
targeting
Data Type
boolean
field

Affiliate Only

Restricts the method to affiliate-attributed traffic only.

Group
targeting
Data Type
boolean
field

Thumbnail

Logo or icon uploaded for the method.

Group
assets
Data Type
asset-url
field

Deposit Text Block

Deposit-side text block rendered by integrations that support custom payment copy.

Group
copy
Data Type
string
field

Withdrawal Text Block

Withdrawal-side text block rendered by integrations that support custom payment copy.

Group
copy
Data Type
string
field

Auto Detect Network

Lets the crypto flow detect network automatically when supported.

Group
crypto
Data Type
boolean
field

Gateway Crypto Static QR Flow

Enables static QR flow for supported gateway-crypto integrations.

Group
crypto
Data Type
boolean
field

Gateway Crypto Static QR Next Step

Enables the next-step behavior paired with static QR flow.

Group
crypto
Data Type
boolean
Operational notes

Notes

item

The frontend uses one shared modal for create and edit.

item

The same modal is also used for `Create New Group` and `Edit Payment Group` flows.

item

`Save` is the visible modal button label for create, update, and group-mode save paths.

item

The hook converts form arrays into comma-separated backend payload fields and normalizes empty numeric strings to null.

item

JSON mode uses the same save path as form mode after parsing and validation.

item

The FE disables or clears `trustedOnly` for traffic modes where the combination is not allowed.

Related references

Related pages

pagePayment 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.

pagePayment Methods / Order

Country- and traffic-aware ordering screen for deposit methods, with casino-side scored order on read and admin override rules for manual ranking.

pagePayment Methods Overview

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

pageAffiliate Deals / Dashboard

Deal-period performance report that combines traffic, deposit, GGR, NGR, payout, and ROI metrics for affiliate deals.

pageAffiliate Deals / Form

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

pageAffiliate Deals / List

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