Skip to main content
Follow the steps in Get started with connectors before proceeding. Feedzai access: An active Feedzai account, with the Feedzai SDK integrated on your frontend. Register your company ID in the Feedzai environment. Credentials: Authentication and authorization credentials from Feedzai. Allowlist: For private hosting, the cluster IP address or the root machine server IP address is on the Feedzai allowlist.

​
Prepare the connector

Backbase deploys this connector. To provide the environment details, follow these steps:
  1. Send environment details to Backbase. Send feedzai.request.orgId, feedzai.base.url, and, for New Account Fraud, feedzaiNaf.base.url to your Backbase support team.
  2. Choose level-of-assurance mapping. Tell your Backbase support team whether to enable decision-flag level-of-assurance mapping, and which risk-score thresholds to use. Agree the thresholds with Feedzai from the business rules in the Feedzai engine. For the mapping logic and the default thresholds, see Reference.

​
Streaming prerequisites

Before you use Feedzai Digital Trust streaming, complete these additional 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 Banking OS 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

Send the Feedzai Digital Trust streaming URL and the streaming OAuth credentials to your Backbase support team. Request filters (optional, on POST /stream/session-events):
  • 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)
The response includes the vendorSpecificFields.feedzaiStreaming.countermeasures object only when Active Defense (activeDefenseEnabled) is enabled. This flag gates the countermeasures data and is independent of the request filters.

​
Connection lifecycle behavior

Understanding how the streaming connection behaves helps you integrate and monitor correctly:
Feedzai replays events within a 5-minute window after reconnect. Disconnects longer than 5 minutes may result in permanent event loss for that period.

​
Test your integration

To use the Fraud Unified API, include your Banking OS subscription key in the request header. If you don’t have a key, contact your Backbase support team to have one provisioned. Test the API using the Postman collection. Test streaming: Include the same api-key header. Call POST /stream/session-events with your subscription filters. Verify session events arrive with expected sessionID, userId, and score. Simulate connector pod restart in a non-production environment to validate reconnect behavior.

​
Troubleshooting

If your connector isn’t responding as expected, check these common scenarios.
Cause: The Banking OS 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.
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.
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 Banking OS and partner infrastructure.Solution: Review your application’s request patterns to identify unexpected spikes. If you require higher throughput, contact your Backbase support team to request an adjustment to your APIM rate limit policy.
Cause: Normal Feedzai clean connection closure at max connection duration. This is expected vendor behavior, not an error.Solution: Open a new /stream/session-events subscription.
Cause: Feedzai idle timeout when no session activity exists.Solution: Expected when no sessions are active. Re-subscribe when monitoring resumes.