Risk Request

post

https://4f1f4a08-8aba-4366-bbcc-001af05920ab.mock.pstmn.io/risk

Risk-based authentication requests are sent by VCAS to the partner. The partner receives the request and responds with Success, Failure or Stepup.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Risk Request Object

ProcessorId

string

required

length between 24 and 24

^[0-9a-fA-F]{24}$

VCAS provided identifier for the partner. Max. 24 characters.

IssuerId

string

required

length between 24 and 24

^[0-9a-fA-F]{24}$

VCAS provided identifier for the partner. Max. 24 characters.

TransactionId

string

required

length between 36 and 36

^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$

VCAS generated transaction reference id. Max. 36 characters. GUID format.

DSTransactionId

string

length between 36 and 36

^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$

Directory Server (DS) generated transaction reference id. GUID format.

MerchantChallengeIndicator

string

enum

Indicates whether a challenge is requested from the merchant. Note: Please allow for future values in this field. EMV has reserved up to 99 values for future use.

3RIIndicator

string

enum

Indicates the type of 3RI request for EMV transactions. Values are defined as follows:

RecurringTransaction
InstallmentTransaction
AddCard
MaintainCardInformation
AccountVerification
SplitOrDelayedShipment
TopUp
MailOrder
TelephoneOrder
WhitelistStatusCheck
OtherPayment

ThreeDSRequestorAuthenticationInd

string

length between 2 and 2

Indicates the type of Authentication request. This data element provides additional information to the ACS to determine the best approach for handling an authentication request. Values are defined as follows:

01 - Payment Transaction
02 - Recurring Transaction
03 - Installment Transaction
04 - Add Card
05 - Maintain Card
06 - Cardholder verification as part of EMV token ID&V
07 - Billing Agreement
08 - Split shipment
09 - Delayed shipment
10 - Split payment
11-79 - Reserved for EMVCo future use (values invalid until defined by EMVCo)
80 - Reserved for Visa Payment Passkeys (Visa transactions only)
81-99 - Reserved for future network program usage.
Reserved values may be introduced by network program updates. New values will be defined and published as they become available.

MessageVersion

string

required

length between 5 and 8

^[0-9]{1,2}\.[0-9]{1,2}\.[0-9]{1,2}$

Version of the message based on 3DS spec. Examples - 2.2.0, 2.2.0

RDXMessageVersion

string

length between 5 and 8

^[0-9]{1,2}\.[0-9]{1,2}\.[0-9]{1,2}$

Version of the RDX protocol being used. This will be used to enable new features without breaking current integrations. Example: 2.2.3 and 2.2.4

MessageCategory

string

length between 2 and 2

Identifies the category of the message for a specific use case; 01=PA, 02=NPA

RiskScore

string

length between 2 and 2

^[0-9]{1,2}$

Risk score of the transaction as determined by VCAS. Max. 2 characters.

RuleOutcome

string

enum

If the transaction is configured to evaluate risk rules, this will be the outcome of that evaluation.

Allowed:

CardBrandName

string

enum

Name of the card network for a specific transaction.

ExemptionInfo

object

Object containing information related to EMV exemptions as related to the EEA PSD2 regulations.

MerchantAuthInfo

object

Object containing information related to any Merchant Authentication information on EMV requests.

MerchantInfo

object

required

TransactionInfo

object

required

ExtensionData

object

Responses

405

Invalid input

200Successful Risk Response