 Before your page redirects the user to the Auth0 /authorize endpoint, attach the collector's IDs as custom query parameters that start with ext- .  The Action reads two of them on each login deviceTransactionID and ubaID .

Passing Device and Behavioral IDs to Auth0 at Login

 Before your page redirects the user to the Auth0 /authorize endpoint, it attaches the collector's IDs as custom query parameters that start with ext- .  Auth0 enforces the following limits on these parameters.

Limits for ext- Parameters in the Auth0 Login Redirect

 The Post Login trigger runs after the user's credentials are validated, so no other placement is needed.  To add Expected result The Action appears between Start and Complete in Actions → Triggers → post-login , and changes are applied.

Adding the Account Protection Action to the Login Flow

 Work through this list on your test tenant.  To verify Expected result Every item in the list is confirmed on your test tenant.

Verifying the Account Protection Login Setup

Account Protection Action Settings

Login Screening

versionDSE

versionAndroid

versioniOS

versionADC

currentyear

signal

repbuilder

passwordless

inrisk

passkey

gateway

deviceserver

mobile

browser

riskID

extract

profiles

index

documentationplatform

returnssolution

protectionproduct

chargebackproduct

fraudproduct

Provides mobile device identification and risk assessment via Software Development Kits (SDKs) for Android and iOS devices.

InMobile

Accertify's post-transaction product that manages the chargeback process for merchants.

Chargeback_Module

The act of a credit card company charging a merchant for goods that a merchant consumer claims they either did not purchase or did not receive. Onus is on the merchant to prove the consumer made the purchase and the merchant delivered the goods.

Chargeback

A service that lets you choose a key field (such as email address) and define the fields you want to collect alongside it to create new data points you can add to the Transaction Detail screen or write rules against.

Profile_Builder

Accertify's platform can monitor the entire fraud lifecycle, including pre-transaction, payment, and post-transaction risk.

Interceptas_Platform

platformname

Device (formerly known as InBrowser) is Accertify’s browser-based data collection solution that gathers transaction and device data from end-user browsers and transmits it to Accertify servers for risk analysis.

Device

A product that collects device attributes, user behavior data, and authentication signals via JavaScript to support risk analysis and decisioning.

Accertify_Data_Collector

A solution that pairs with Fraud Management to mitigate risk associated with claims, adjustments, refunds, returns, reshipping, and exchanges.


CARE

An Accertify product that uses the Interceptas® Data Management Platform to process transaction data and enable users to address their fraud risk.

Accertify_Fraud_Management

The Accertify Case Management feature is the user interface within the Interceptas Platform.

Case_Management

Accertify Risk ID. A cross-client consortium of positive and negative data points.

ARID

An Accertify product that streamlines all aspects of the chargeback management process from review of a client’s payment, to receiving the chargeback, and submitting a representment response

Accertify_Chargeback_Management

Accertify Chargeback Management (ACM) is our official product offering. It helps to streamline all aspects of the chargeback management process from review of a client’s payment, to receiving the chargeback and submitting a representment response. 

A historical reputational data set that produces a risk assessment between 0.000 and 1.000, with the higher probability indicating a higher risk of fraud.

Accertify_Index

A group of Accertify products that analyze device attributes, environmental signals, and behavioral patterns to support event and transactional fraud decisions.

Device_Intelligence

An Accertify product that combines continuous monitoring and machine-learning algorithms to identify risky events that occur on Client websites using the five pillars: Device, Connection, Location, Behavior, and Reputation.

Account_Protection

companyname

alldeviceproductname

supportEmail

APIs

API Reference Page

Documentation Structure

Getting Started

Shared Core Data Model

Industry Specialization

SCA Optimization

3DS Optimization

RiskBased Authentication (RBA)

Integration Requirements

Data and Responses

Payment Optimization

Core Concepts

Authentication Methods

Importer ID and Endpoint Provisioning

Transaction Lifecycle Contexts

Hashing Requirements

Accertify Hash Algorithm

Error Handling

Global Constraints

Populating Universal Fraud API Requests

Retail Complete Request Structure

Accertify Unified Risk API - Retail

Retail Extension Overview

Airline Complete Request Structure

Accertify Unified Risk API - Airline

Airline Extension Overview

iGaming Complete Request Structure

Accertify Unified Risk API - iGaming

iGaming Extension Overview

Ticketing Complete Request Structure

Accertify Unified Risk API - Ticketing

Ticketing Extension Overview

Travel Complete Request Structure

Accertify Unified Risk API - Travel

Travel Extension Overview

Amusement Complete Request Structure

Accertify Unified Risk API - Amusement Park

Amusement Extension Overview

Universal Fraud APIs

Full Path

Chargeback API Changelog

Transaction Matching

Exporting Transactions

Accertify Chargeback Management API

Chargeback API Overview

Chargeback Search API Changelog

Accertify Chargeback Search API

Chargeback Search API Overview

Dispute APIs

Account Protection API Changelog

Event Overviews

Accertify Account Protection API

Auth0 Overview

Account Protection API Overview

CARE API Changelog

Accertify CARE API

Accertify CARE API (EU)

CARE API Overview

Accertify Data Privacy Request Submission API

Data Privacy API Overview

Risk and Intelligence APIs