Get started

​

Prerequisites

• You have completed the steps in the Get 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

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
   

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

​

Streaming prerequisites

• Obtain a Feedzai Digital Trust for Account Monitoring license that includes Streaming API access.
• Assign the Streaming role to a Feedzai API user.
• Request OAuth 2.0 client credentials for the Streaming endpoint. If your tenant uses distinct API users, these credentials are separate from your synchronous scoring credentials.
• Enable outbound HTTPS from the Grand Central connector cluster to the region-specific Feedzai Digital Trust streaming host (EU or US).
• Configure IP allowlisting on both sides of the streaming connection.
• Activate the Feedzai SDK on your web and mobile channels, so that user_id and session_id are supplied during data gathering and echoed on streamed events.

​

Streaming configuration

streaming.upstream.url=https://api.digitaltrust.eu-03.feedzai.cloud/v5/analysis/streaming/session/{orgId}

# SSE reconnect tunables
# Initial back-off delay (ms) before the first reconnect attempt after a failure
sse.reconnect.initialDelayMs=1000
# Maximum back-off delay (ms); the delay is capped at this value
sse.reconnect.maxDelayMs=30000
# Multiplier applied to the current delay after every failed attempt (exponential back-off)
sse.reconnect.backOffMultiplier=2.0

• filter.dataSource: web, android_sdk, or ios_sdk
• filter.alertType: standard Feedzai alert type name
• filter.numberOfStream: parallel stream replicas (Feedzai supports up to 3)

​

Connection lifecycle behavior

​

Test your integration

​

Troubleshooting

​

Need more help?