Each Tenant has a large number of configuration options available to them. In addition, QFD is a multi-Client system. This means that a Tenant can have multiple Client configurations for applying different options in a way that best suits their business. Some examples of this are:
- An enterprise bank with multiple brands (such as a consumer prepaid or private wealth offering)
- A card servicer with multiple Clients of their own (such as a fully managed credit card offering to a bank)
- A processor with multiple consumers, each issuing cards, having their own needs for how disputes are managed - but there is still one back office
In addition, there are a multitude of settings available. As much as possible, these are managed at a Client level. It's important to note that a Tenant might simply have one Client only. This is the most common configuration.
Settings are made available for Tenants to configure in several different ways. The way settings are altered is primarily based upon how risky to change or difficult to understand the setting is. In some cases, settings may have direct dependencies on the underlying service layer, which will go through a development process to change.
Configuration Methods
Self Configuration (Configuration Portal)
QFD includes a configuration portal, commonly referred to as "Config", which allows clients to customize application behavior and user experience. Configuration settings are typically broken down based on transaction type and/or the system/user process that is impacted. These settings can be viewed and changed directly by users with appropriate access.
Examples:
- Auto Pay/PC/additional monetary thresholds
- Client logos
- Notification email addresses
- Document requirements
- Regulatory settings
- Approvals
More details here. For any Clients not yet utilizing self configuration, all of these settings can be configured via the Quavo Configured path below.
Quavo Configured ("Client Info")
These are settings that are maintained by Quavo staff and can be changed via support ticket. In many cases, changing these settings could have extensive compliance, financial or work management effects. These changes are considered development and will go through Quavo's change process, which includes testing, approval, etc..
Examples:
- Accounting plan/fee mapping
- Available transaction types
- Work queues
- Network/processor settings
- Authentication details
- International settings
More details here.
Quavo Development (Implementation Change)
Some settings are directly related to service integrations and changes to them require refinement, analysis, development, testing, etc.. minor changes are usually included in your support agreement. Major changes (such as a core conversion, switching networks, etc..) may require a separate engagement.
Examples:
- Transaction type mapping
- Account status codes
- Communication channels
- Letter styling/content changes
- Adding a Client
- Certificate changes