Initiate Action Request

The InitiateAction request is used to signal to the partner to take action on an item.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

InitiateAction Request Object

string
required
Defaults to 5723ae630063ac1a9c3ab079

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

string
required
Defaults to 5723ae630063ac1a9c3ab654

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

string
required
Defaults to 00ec043e-40b5-4ce4-95c2-9e83b644f412

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

string
Defaults to 00ec043e-40b5-4ce4-95c2-9e83b644f258

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

string
enum
Defaults to RecurringTransaction

Indicates the type of 3RI request for EMV transactions. Note: Please allow for future values in this field. EMV has reserved up to 99 values for future use.

string
enum
Defaults to 01

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.

string
required
Defaults to 878f4751-4140-4881-9e4a-003e83524f22

Unique identifier to identify the particular Stepup request. Length - 36 characters.

string
enum

Used to identify the method of Stepup.

Allowed:
integer
required

Counter for tracking the number of Stepups. Each stepup can go from Stepup -> InitiateAction -> Validate. If the user requests a "resend" via the browser templates it will initiate another Stepup request.

string

This is a unique value generated with each new OTP value or “VerificationToken”. In the instance where the consumer can receive multiple OTPs for the same transaction, this can be leveraged to show the consumer which OTP the system is expecting to be entered. This value should be sent in the SMS or Email along with the VerificationToken and then displayed on the consumer screen.

string

URL provided by VCAS to be used by issuer to return the OOBCallbackValidateStatus response back to the RDX/VCAS service during the OOB API Callback flow. Issuer will append the transaction status to the URL. Example: https://qa-oob-callback-api-vcas.visa.com/V1/OOBCallbackValidateStatus

string

Token to be sent to cardholder.

string
required
Defaults to 2.2.0

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

string
Defaults to 2.2.4

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

string
Defaults to 01

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

Credentials
array of objects
required
Credentials*
MerchantInfo
object
PaymentInfo
object
TransactionInfo
object
string
enum
Defaults to VISA

Name of the card network for a specific transaction.

Responses

405

Invalid input

Language
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json