Pre-authenticate

Overview

The preAuthenticate method initiates the 3D Secure authentication flow. It collects device data and prepares the authentication context, determining whether frictionless or challenge-based verification is needed.

Business Use Case: Before processing a high-value transaction, initiate 3DS to reduce fraud liability and comply with Strong Customer Authentication (SCA) requirements.

Purpose

Scenario
Benefit

Fraud prevention

Shift liability to card issuer

SCA compliance

Meet European regulatory requirements

Risk-based auth

Frictionless flow for low-risk transactions

Request Fields

Field
Type
Required
Description

merchantOrderId

string

Yes

Your unique order reference

amount

Money

Yes

Transaction amount

paymentMethod

PaymentMethod

Yes

Card details

customer

Customer

No

Customer information

returnUrl

string

Yes

URL to redirect after 3DS

Response Fields

Field
Type
Description

connectorTransactionId

string

Connector's 3DS transaction ID

status

string

AUTHENTICATION_REQUIRED, FRICTIONLESS

authenticationData

object

Device data for next step

redirectionData

object

Challenge URL if required

statusCode

number

HTTP status code

Example

SDK Setup

Request

Response - Frictionless

Response - Challenge Required

3DS Flow

spinner

Next Steps

Last updated

Was this helpful?