Skip to main content

Payment Method

Fluid provides its customers the facility to create payment methods as required from the Payment Method page.

When a payment method is created, it will be added to the operator’s collection to use when needed.

View Payment Methods​

  • This tab displays all payment methods in the operator’s collection.

Creating a new Payment Method​

  • To add a new payment method:

    1. Click on the “+ New Record” button in the top right corner. This will open a new page.

    2. Populate the fields presented.

      • Name* - This field will define the payment method's name the end-users see when they use the wallet.
        • Use the locale tabs to provide a name for your payment method (in case the name is different and requires translations).
        • This field accepts single-line text input. Both uppercase and lowercase letters are accepted.
      • Name (Internal)* - This field is for internal use only and helps distinguish between payment method names from different providers.
        • Naming should follow the following format: PROVIDERTYPE_SERVICE-OperatorName.
      • Provider Type* - This field will define the transaction type used to set up the payment method in your Payment Orchestration platform. The transaction type in this field should be identical to the one you are using on your platform.
      • Service - This field will help you to separate APMs or providers with the same transaction type and in the cashier these methods will be with their own logo and name. (this field can be left empty if you are using only one Transaction Type)
      • Logo and Logo Light - This field allows you to upload .svg format logos directly from your computer or the Media library on your Fluid account.
        • Logo has to be in SVG format with dimensions 94 x 56
      • Terms & Conditions - This field allows you to add single line free text. (for example: interac-trademark)
      • Masked account format - The dropdown list lets you determine how much of the stored method details is shown to the user.
      • Info - This field is used to display information about the payment method. An “i” icon will be shown next to the payment method when any information is added.

      Text content customized

      Text content customized

      • Auto-Redirect Type - Enables auto-redirect for this method. When enabled, users are automatically redirected (if required) without any manual action. Select the container type (Popup Window or Browser Tab) that matches the method configuration.
      • Payment Type* - The dropdown list has 4 selections to choose from.
        • EWallet
        • BankTransfer
        • Crypto
        • CreditCard
      • Deposit Instructions (Payment method HTML) - The field is used to add HTML or Markdown with optional usage instructions shown to players on the deposit details screen for this payment method.

      Text content customized

      • Withdrawal Instructions (Payment method HTML) - A separate field for HTML or Markdown instructions shown to players on the withdrawal details screen for this payment method. Leave it empty to show no instructions during withdrawals — it does not fall back to the deposit instructions.

      • Deposit Input Fields - This field is used to specify any additional fields required by the payment method.

        Input fields are selected from the 'Library,' and a 'New Input Field' can be added if the Library does not have the desired value. 'Amount' and 'service' do not need to be specified in this section, as they are provided by default as part of the deposit flow.

      • Withdrawal Input Fields - This field is used to specify any additional fields required by the payment method. (same as 'Deposit Input Fields') Please note that the same Payment method entry can be used in case Provider Type & Service are the same for Deposit and Withdrawal. Input fields are selected from the 'Library,' and a 'New Input Field' can be added if the Library does not have the desired value. 'Amount' and 'service' do not need to be specified in this section, as they are provided by default as part of the deposit flow.

      • Withdrawal inputs shown when method is stored - This toggle can be switched when the player should be presented with the Input Fields even if they're using a stored method.

      • Payment Limits - Optional per-method deposit and withdrawal limits. The record exposes four numeric fields:

        • Min Deposit - Minimum amount a player can deposit using this method.
        • Max Deposit - Maximum amount a player can deposit using this method.
        • Min Withdrawal - Minimum amount a player can withdraw using this method.
        • Max Withdrawal - Maximum amount a player can withdraw using this method.

        Each field is optional. A value set here only applies when the payment provider does not return its own limit for the method — provider-supplied limits always win. Leaving a field empty (or setting it to 0) tells Fluid to fall back further to its global default. Use this record to define sensible per-method limits on gateways that don't return their own (for example Payage).

Attributes marked with * are mandatory.

Edit payment methods in collection​

  • Locate the payment method which requires editing.
  • Click the payment method. The screen with its details will be displayed.
  • Edit as necessary.

Delete payment methods from collection​

  • Locate the payment method to be deleted.
  • Click the payment method. The screen with its details will be displayed. Navigate to and click the options menu (3 dots) next to the header, in the top left corner.
  • Click “Delete”.

Additional Notes

Save Changes: Always click “Save” after making edits to ensure updates are applied.

Search Tip: Use the Find functionality to quickly find specific payment methods in large collections.

Hosted Fields​

For PCI DSS scope reduction, credit-card inputs can be rendered inside iframes hosted by the payment gateway instead of native inputs on the operator's site. When enabled, the raw card data never enters the operator's browser context — only encrypted tokens cross back to the widget.

Enabling hosted fields​

  • The Hosted Fields Enabled toggle lives on the operator's payment gateway entry (e.g. the operator's connection to PIQ), not on individual payment methods.
  • When On, every credit-card payment method routed through that gateway renders as hosted-field iframes — provided the gateway has a hosted-fields URL configured (set centrally by Fluid for each gateway environment).
  • When Off, the widget falls back to the regular client-side encrypted form (or plain text if no encryption is configured on the gateway) for every credit-card method on that gateway.
  • The flag is per-operator-per-gateway, so an operator can have, for example, all credit cards on PIQ using hosted fields while keeping all credit cards on Payage on the regular form.
  • Only affects credit-card payment methods. Non-card payment types (e-wallets, bank transfers, crypto, etc.) ignore the toggle.

What changes for the end user​

  • Visually, the form looks the same.
  • Validation feedback (errors, card brand icon) first appears when the user clicks out of a field. Once an error is showing, it updates live as the user corrects the input — they don't have to click out again to see the error clear.
  • The cardholder name input is also moved inside an iframe for consistency, even though the name itself isn't encrypted.

Switching off​

Toggling Hosted Fields Enabled back to Off on the operator's gateway entry and saving immediately reverts every credit-card method on that gateway to the regular form on the next request. No widget redeploy.