Skip to main content
Complete the following prerequisites and configuration to start using the Feedzai Connector.

​
Prerequisites

Before you begin, make sure that the following requirements are met:
  • You have completed the steps in the Getting started.
  • You have integrated the Feedzai SDK on your frontend system.
  • You have an active Feedzai account. Register your company ID in the Feedzai environment and configure it under the connector configuration.
  • You have valid authentication and authorization credentials from Feedzai.
  • For private hosting, ensure that the IP address of the cluster or the IP address of the root machine server is on the Feedzai allowlist.

​
Configuration

To configure your connector, follow these steps:
  1. Set your APIM subscription key in the header as follows:
    • Key: api-key
    • Value: <your subscription key>
  2. Configure the following details in gc-applications-live, in the values.yaml file. For example: 
    ├── iPaaS
└── azure/runtimes
    ├── dev-v2
    └── test-v2
        └── values
            ├── gc-feedzai
                └── fraud-v0.values.yaml
  3. Configure the environment details for user activity analysis in the values.yaml file:
    • feedzai.request.orgId - Company ID issued by Feedzai.
    • feedzai.base.url - Feedzai URL.
  4. To configure the environment details for New Account Fraud in the values.yaml file, use the following:
    • feedzaiNaf.base.url - Feedzai NAF URL.
  5. Configure the risk score thresholds for the level of assurance (LOA): 
    retryFlag=true
levelOfAssuranceMin=30
levelOfAssuranceMid=60
levelOfAssuranceMax=90
Set the risk score threshold in consultation with Feedzai based on the business rule definition in the Feedzai engine.
The following values are configurable for user-activity-analysis:
  • levelOfAssuranceMin - The connector returns LOA_LOW if the risk score falls below the defined threshold.
  • levelOfAssuranceMid - The connector returns LOA_SUBSTANTIAL if the risk score is below the defined threshold but exceeds the minimum threshold specified in levelOfAssuranceMin.
  • levelOfAssuranceMax - The connector returns LOA_HIGH if the risk score exceeds the minimum threshold specified in levelOfAssuranceMid. The connector returns BLOCK if the risk score exceeds the maximum threshold specified in levelOfAssuranceMax.
Optional: To enable retry between Grand Central and Feedzai, set retryFlag to true.

​
Test your integration

To access the Fraud Unified API, include your Grand Central subscription key in the request header. If you don’t have a key, contact the Grand Central Support Team to have one provisioned.
KeyValue
api-key<your_subscription_key>
Test the API using the Postman Collection.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Grand Central gateway can’t establish a handshake with the Feedzai endpoint. This typically indicates an upstream service outage at Feedzai or a network routing failure.Solution: Verify the operational status of the Feedzai environment with Feedzai. If the service is operational, contact the GC Support team.
Cause: The request to Feedzai exceeded the configured timeout threshold. This can occur during high load or network latency issues.Solution: Verify the operational status of the Feedzai environment with Feedzai. If the service is operational, contact the GC Support team to review timeout configurations.
Cause: The credentials provided during setup are incorrect.Solution: Verify your credentials with Feedzai and contact the GC team to update the connection.
Cause: The number of incoming requests exceeded the defined threshold for your subscription tier. This response protects the stability of the Grand Central and partner infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If you require higher throughput, contact the Grand Central team to request an adjustment to your APIM rate limit policy.

​
Need more help?

Contact support

Reach out to the Grand Central team for assistance with environment setup or rate limit increases.