Updates from RDX Message Version 2.2.3 to 2.2.4
Updates from RDX Message Version 2.2.3 to 2.2.4:
New Transaction Status Reason Codes
The following values have been added to the Transaction Status Reason Codes:
Addition of Out-of-Band Callback Validate Status API
The Out-of-Band (OOB) Callback API is an ingress API which allows issuers to automatically send a transaction authentication status using the RDX Initiate Action and the Validate Request API calls. The OOB Callback API is only applicable with OUTOFBANDOTHER and BIOMETRIC stepup type values.
Deletion of TransactionInfo.ShoppingCart (Object)
RiskRequest.TransactionInfo.ShoppingCart (Object) has been deleted.
DeviceName Field Update
The "DeviceName" field in RiskRequest.TransactionInfo.DeviceInfo (Object) has been updated to "up to 256 characters".
Updated Channel Values
Values for Channel field in RiskRequest.TransactionInfo (Object) have been updated to:
• WEB
• APP
• M_WEB
• THREERI
Updates to JWE Requirements for RDX
Clarification of certificate creation and renewal processes.
Field Updates
ProcessorID and IssuerID fields updated from “Up to 24 characters” to “24 characters”.
Firewall Configurations
Partners will need to trust list VCAS IP addresses in order to allow requests to pass through their firewall.
RDX 2.2.3 Updates
MessageCategory field with EMVCo values added to RiskRequest and InitiateActionRequest; previously only on StepupRequest.