Overview of Account Settings
Author:
Fluent Commerce
Changed on:
1 Nov 2023
Overview
This is a quick reference of the most important Account and Payment Settings.
Account Settings
Author:
Fluent Commerce
Changed on:
20 Feb 2025
Overview
This article contains the list of Settings used in the context of ACCOUNT.
Key points
- Explore the ACCOUNT Settings available
The following Settings are used in the context of ACCOUNT:
- FC.MYSTIQUE.EVENT.SEARCH.FILTERBASED
- SSO.DETAILS
- ADMIN_CONSOLE_MANIFEST
- LARGE_VOLUME_CLIENT.BOOLEAN
- GRAPHQL.DISABLE_GRAPHQL_ME_QUERY
- INVENTORY_BATCH_ENHANCEMENT_ENABLED
- HOTFIX_NEW_APOLLO_CLIENT_ENABLED
- fc.enable.batch.preprocessing
- rubix.enable.enhanced.gi.exception.audit.event
- rubix.entity.parent.status.fix
- fc.api.fulfilment.uniqueness
- fc.mystique.apps
- fc.batch.auth.expiry.code
- fc.fulfilmentoptions.create.event.persistence
- fc.graphql.order.create.event
- fc.graphql.comment.access
- fc.graphql.compatibility.nullEmptyValidation
- fc.gql.compatibility.persistEmptyStrings
Related content
Payment Settings
Author:
Fluent Commerce
Changed on:
1 Nov 2023
Overview
The below settings control the allowed values in the order transaction create method in the REST API (POST /api/v4.1/order/{orderId}/transaction). The createFinancialTransaction GraphQL mutation can use custom-defined paymentProvider, paymentMethod and currency fields. We recommend that the below settings be used as the way to look up current configured values dynamically without hardcoding values for these fields.
These settings can be modified and retrieved via the settings API.
Key points
- Understand the basic setup of payment settings
- Example of how payment settings can be used
Example of use
The combination of these three fields provides a range of flexibility to control logic for a variety of use cases:
financialTransation Field | Setting | Example 1 | Example 2 | Example 3 |
cardType | No custom values allowed | VISA | MASTERCARD | (empty) |
paymentMethod | PAYMENT.METHOD | ELECTRON | CREDITCARD | GIFTCARD |
paymentProvider | PAYMENT.PROVIDER | ADYEN | SQUARE | CUSTOM_PROVIDER1 |
currency | PAYMENT.CURRENCY | USD | EURO | BITCOIN |
The above table combines the four different payment-related fields that can be used in combination to trigger different payment-related logic in workflows. Each example combination could be used to fire custom events to execute card, payment method, or provider-specific logic or returns requirements.
