Integrations and Connectors/Connectors/Setup Guides/Fraud

Sardine Connector

Sardine AI is a risk intelligence platform that provides real-time fraud detection and behavioral risk scoring using machine learning. It offers tools for login protection, identity verification, and user onboarding assessment.

Descope's Sardine connector integrates directly with Sardine's API to evaluate user risk during login or signup. The connector enables you to receive fraud risk assessments and drive security decisions dynamically within your Descope flows.

Setting Up the Sardine Connector

To integrate the Sardine connector, follow the steps below:

  • Visit the Connectors page in the Descope Console.
  • Choose Sardine from the list of connectors.

Connector Setup

Set up the required credentials provided by Sardine:

  • Connector Name: Assign a name to distinguish this connector in your flows.

  • (Optional) Connector Description: A short description of this connector's purpose.

  • Client ID: Your Sardine-issued Client ID.

  • Client Secret: Your Sardine-issued Client Secret.

  • Base URL: The Sardine API endpoint to use, such as:

    • https://api.sandbox.sardine.ai (sandbox)
    • https://api.sardine.ai (production, US)
    • https://api.eu.sardine.ai (production, EU)

Note

Ensure the credentials you provide have access to Sardine's API, and that the base URL matches your deployment region and environment.

Test & Save

  • Use the Test button to validate your connection with test inputs.
  • Once successful, click Create to save the connector.

Implementing the Sardine Connector

Warning

Because the Sardine connector evaluates risk at runtime, it must be placed after a user input screen or action in the flow.

Select or Create a Flow

Navigate to Flows in the dashboard and open an existing flow or create a new one.

Integration

Click the blue plus icon in the flow builder and select Connector. You'll now see the available Sardine actions:

sardine flow actions

Available Actions

The Sardine connector includes the following actions:

Sardine / Login Account Takeover Check

Evaluate a login attempt for potential account takeover risk.

Parameters:

  • User ID (required): A unique identifier for the user being evaluated.

  • Customer Properties: Optional key-value pairs matching Sardine's customer details object, such as:

    • email
    • phone
    • ip_address
    • device_fingerprint
    • user_agent

These properties can be passed dynamically using context keys, such as {{user.email}} or {{ipAddress}}.

Sardine / Onboarding User Identity Check

Evaluate a new sign-up attempt for fraud or risk.

Parameters:

  • User ID (required): A unique identifier for the new user.
  • Customer Properties: Optional key-value pairs similar to those used in the login check.

This action is typically used right after a registration or sign-up screen to determine whether further verification is necessary.

Response Handling

The response is saved in the connector context, e.g., connectors.sardine_loginCheck or connectors.sardine_onboardingCheck.

Fields available for use in the flow include:

  • decision: The Sardine risk decision (e.g., approve, review, decline).
  • score: A numeric risk score assigned by Sardine.
  • reason: Explanation or factors contributing to the decision.
  • recommendation: Any follow-up action suggested by Sardine, such as requiring additional verification.

You can use these values in conditional branches to determine if the user should proceed, step-up authentication, or be blocked.

Example Flow

Below is an example flow that checks a user's login risk and routes them through passkey-based MFA authentication if the decision is not approve.

sardine flow example

Note

Refer to the Sardine API Reference for detailed information on supported fields and integration best practices.

Was this helpful?