Modirum MPI Merchant Interface v4

1. Introduction

Modirum has developed a range of software products to support the use of 3-D Secure protocol for payer
authentication. Modirum MPI is a product that is developed for merchants, acquirers or payment service
providers that want to implement the 3-D Secure Merchant Plug-In (MPI) protocol. Modirum MPI is
compliant with Visa, MasterCard, American Express, Diners and JCB schemas (protocol version 1.0.2).
Since version 4.0.2.51 also ThreeDSecure 2.0 and 2.1 support has been established. As of now 2.0 is
discontinued and Modirum MPI is certified to 2.1 protocol.
This document is the reference manual of Modirum MPI merchant interface. It has been targeted to
merchants who connect to and process 3D Secure through Modirum MPI
The structure of this document is as follows:

Section HTTP POST Interface describes the merchant application interface of the product. The
interface enables implementation of 3-D Secure protocol without any programming work. This
section includes a separate summary of different result values of the 3-D Secure process
(mdStatus, eci).

The new interface specification introduces recently emerged new MPI extension such as Brazil Market
and Trusted Third Party and ThreeDSecure 2.x specifics and extensions. Please check for new fields in
this version to ensure compability (look for “Since 4.0.2.54”)

1.1 Prerequisites

It is assumed that the reader has basic knowledge of payment cards in the traditional commerce and in
electronic commerce. It is also assumed that the reader has basic knowledge about the acquiring process
of the payment cards.

1.2 Glossary

This section includes selected terms that are commonly used in the document. An extensive 3-D Secure
glossary is available in 3-D Secure: System Overview, available through the “Vendors & Merchants” link
on http://corporate.visa.com.

ACS =Access Control Server	A component that operates in the Issuer Domain, verifies whether authentication is available for a card number, and authenticates specific transactions.
API	Application Programming Interface
HTML	HyperText Markup Language
PSP/Processor	Payment services provider
MPI Manager/Admin Tool	User interface implementation of the MPI database. The tool can be used to maintain merchant and directory server data as well as to browse transactions.
Merchant Plugin	A component that operates in the Acquirer Domain; incorporated into the merchant’s Web storefront to perform functions related to 3-D Secure on behalf of the merchant, such as determining whether authentication is available for a card number and validating the digital signature in a 3-D Secure message.
MPI	See Merchant Plug-in.
PAN	Primary Account Number – often referred to as card number
PATransReq	Payer Authentication Transaction Request; a record of authentication activity sent by the ACS to the Authentication History Server
PATransRes	Payer Authentication Transaction Response; Authentication History Server response to PATransReq
PAReq = Payer Authentication Request	A message sent from the Merchant Server Plugin to the Access Control Server via the cardholder device. Requests the issuer to authenticate its cardholder and contains the cardholder, merchant, and transaction-specific information necessary to do so.
PARes = Payer Authentication Response	A message formatted, digitally signed, and sent from the Access Control Server to the Merchant Server Plug-in (via the cardholder device) providing the results of the issuer’s 3D Secure cardholder authentication.
VEReq = Verify Enrollment Request	A message from the Merchant Server Plug-in to the Visa Directory or from the Visa Directory to the ACS, asking whether authentication is available for a particular card number
VERes = Verify Enrollment Response	A message from the ACS or the Visa Directory, telling the Merchant Server Plug-in whether authentication is available
Directory Server	A server hardware/software entity which is operated in the Interoperability Domain; it determines whether authentication is available for a specific card number, and if so, it returns the URL of the appropriate Access Control Server to the Merchant Server Plugin.
WAP	Wireless Application Protocol
WML	Wireless Markup Language
3DS Server	A server component used in ThreeDSecure 2.x that resempbles somewhat MPI functionality of ThreeDSecure 1.0 and is responsible with communications and interfacing with Directories and 3DS Requestors and ACS redirections in browser and redirection mode.
3DS Requestor	An end entity or Merchant participating in 3DS Secure 2.x protocol.
AReq	Authentication request in 3DS 2.x protocol
Ares	Authentication response in 3DS 2.x protocol
RReq	Results request in 3DS 2.x protocol
RRes	Results request response in 3DS 2.x protocol
CReq	Challenge request in 3DS 2.x protocol
Cres	Challenge request response in 3DS 2.x protocol

1.3 Getting Started

The purpose of this section is to describe the basic functionality of Modirum MPI. Functions of the product
are walked- through with help of examples. More detailed description of the product is included in the rest
of the document.
Note that the examples can be tested with a demo merchant and a live Modirum MPI. In order to get access
to Modirum demo site, please contact Modirum support.
In order to try the following examples with Modirum software, please note the following
recommendations:

With the example merchant application, it is recommended to use FireFox, Chrome, or Internet Explorer 9
(or newer). The software has also been tested with other browsers, but there have been some technical
problems with earlier browser versions.
It is highly recommended to use a display with a minimum 1024×786 graphics resolution.

1.4 Which MPI Interface Should Be Used

Modirum MPI supports several alternative protocols for integration to the payment page:
1. HTTP POST as Foreground
2. HTTP XML or XML+SOAP API
Which one to use depends on how much integration effort you are willing to invest. The biggest architectural decision
you need to make is whether you will be using the MPI in “foreground” or “background” mode.
In “foreground” mode, the MPI is exposed directly to the Internet as a separate web application, typically on a separate
dedicated server or a separate web application on some server also used for other purposes.
In “XML” mode, the MPI may not be directly exposed to Internet for end users but only for inbound directory
connection for 3DS2 RReq, but some other application, typically the one displaying the payment page, handles the
user browser session and passes data between the cardholder browser and the MPI.
HTTP POST as foreground is the easiest and the technical integration effort should be up to few days, whereas XML
integration effort may be a few weeks.

1.4.1 HTTP POST as Foreground

Payment page and MPI are separate applications residing on same or different servers. In this model the transaction
flow is:
1 The payment page places MPI input values into HTTP fields on HTML page and redirects the user browser
to the MPI (using html form with Javascript).
2 MPI contacts directory and either returns immediately (not enrolled of frictionless authentication) or
redirects the user browser session to the ACS for challenge authentication.
3 ACS authenticates
4 MPI receives the user session back from the ACS.
5 MPI verifies the ACS response and Directory Response in 3DS2.
6 The MPI redirects the user browser back to the payment page and payment page application reads the
return values from HTML fields.

1.4.2 XML API or with SOAP

Payment page and MPI are separate applications residing on same or different servers. In this model, MPI never
receives the user browser session. The payment page application has the user session, performs necessary redirections
and receives the response.
In this model the transaction flow is:
1. The payment page places MPI input values into XML message and sends a background system-to-system
HTTP(S) call to the MPI.
2. MPI contacts directory and returns either final response, continue with enrollment and perform 3ds method
or finalized HML redirect form with included formatted PAReq/CReq message and ACS URL to the payment
page application.
3. If cardholder was enrolled and or challenge authentication requested, payment page application redirects the
user browser to the ACS with posting the PAReq/CReq from acquired from MPI.
4. ACS authenticates
5. Payment page application receives the user session back from the ACS with PARes/CRes.
6. Payment page application submits the ACS response PARes/CRes to the MPI in XML message for
verification.
7. MPI verifies the ACS response and DS direct response in case of 3DS2.
8. The MPI places results to merchant with final XML message with verified results and payment page
application reads the return values from XML message fields.
Note: The communications in background use XML or XML SOAP messages defined in interface specification
sections in this document.
So, the payment application should be aware of this and should be capable to send such requests to mpi and extract
the needed values from response XML/XML SOAP.

2 HTTP POST Interface

The simplest way to add 3-D Secure support to existing Merchant site is to use HTTP Post interface of the Modirum
MPI.
The control flow using HTTP Post interface is the following:
1. Merchant payment page asks the user all the relevant payment data, such as card number, expiry, etc.
2. Merchant payment page calculates the signature (v 4.0, detailed below) of all the fields to be posted to
Modirum MPI and POSTs these fields to the Modirum MPI.
3. Modirum MPI checks the card participation from the 3-D Secure directory and return the redirection
page to the Issuer ACS. The right directory is found with either card scheme id or matching the beginning
of the card number.
4. After the ACS is finished with the user authentication, ACS returns the control to the Modirum MPI. The
MPI Server verifies the signature of ACS and POSTs the response to either success URL or fail URL,
which the MPI has earlier passed to the ACS.
5. Merchant payment page reads the response and continues with the authorization of the payment (or does
the error processing).

2.1 Parameters of the Post to MPI Server

2.1.1 Start or process an authentication session

The following table describes the parameters of the POST from the payment page to Modirum MPI.
HTTP POST interface version has been upgraded to 4.0.

Field	Required / Optional/	Description
General parameters	Condition
version	R	4.0
cardType	O/R	Card scheme can be defined explicitly. Values with one digit are valid. The value is matched to directory server entry that is mapped to the merchant with that particular cardType The field can also be left empty, which means that the directory server is determined from the card number
pan	R	Card number. 13-19 digit account number Note: must nor present if cardEncData field is used
expiry	R	Expiration Date supplied to the merchant by cardholder (YYMM). Note that this field is not checked in most of the production ACS installations. Note: must nor present if cardEncData field is used
cardEncData	C	In case Client-side card data encryption used with VPOS support. And then fields pan and expiry must be missing
deviceCategory	R	Integer length 1, Indicates the type of cardholder device. Supported values are: 0 = www 1 = legacy mobile (deprecated, means wml interfaces) 4 = dtv (deprecated) 5 = mobile SDK (for ThreeDSecure 2.x only) 6 = for ThreeDS Requestor initiated (3RI) flow (for ThreeDSecure 2.x only) Since version 4.0.2.37 this field is required. Most cases this value shall be always 0 as wap phones are no longer mainstream and may not be supported by ACSes.
purchAmount	O	Max. 12-digit numeric amount in minor units of currency with all punctuation removed. (Optional for NPA only) Examples: Display Amount USD 123.45 Purchase Amount 12345
exponent	O	Exponent number length 1 (Optional for NPA only) The minor units of currency specified in ISO 4217. For example, US Dollars has a value of 2; Japanese Yen has a value of 0.
description	O	Purchase description. Brief description of items purchased, determined by the merchant. Maximum size is 125 characters, but merchant should consider the characteristics of the cardholder’s device when creating the field. Note: Most Issuers do not display the description to the user.
currency	O	Currency. Determined by merchant. ISO 4217, 3-digit numeric. (Optional for NPA only)
merchantID	R	ID to identify the merchant to Modirum MPI.
merchantName	O	Length: 1-25 characters Format: any characters Send this parameter if you want to override PAReq.Merchant.name. Effective only in Multinamed or PSP mode only merchant only. Else of by default it is taken from mpi database. ***
xid	R	Unique transaction identifier determined by merchant. Contains a 20 byte statistically unique value that has been Base64 encoded, giving a 28-byte result. Note: used only in or for 3DS1.0.2 protocol, but still needed for any case to be present for later reference lookups etc.
merchantTxId	C	Unique transaction identifier determined by merchant. If present, the value will be validated in the database if it is already existing for the specified merchant. An error will be returned if found. A maximum of 40 characters is allowed. The parameter is required if the merchantTxIdRequired setting is set to true.
okUrl	R/-	Fully qualified URL to Merchant. Modirum MPI will do POST when finished to this URL in all other cases, except when authentication or signature validation fails (mdStatus = 0). Max length 2048 chars Not applicable if deviceCategory = 5 or 6
failUrl	R/-	Fully qualified URL to Merchant. Modirum MPI will do POST to this URL when authentication or signature validation fails. mdStatus = 0. Max length 2048 chars Not applicable if deviceCategory = 5 or 6
MD	O	The MD (“Merchant Data”) field: merchant state data that must be returned to the merchant. The content of this field is passed unchanged and without assumptions about its content to the return POST. This field is used to accommodate the different ways merchant systems handle session state. If the merchant system does not maintain state for a given shopping session, the MD can carry whatever data the merchant needs to continue the session. This field must contain only ASCII characters in the range 0x20 to 0x7E; Since version 4.0.2.15 characters ‘<‘ and ‘>’ are not allowed in this parameter. If other data is needed, the field must be Base64 encoded. The size of the field (after Base64 encoding, if applicable) is limited to 254 bytes. If MD includes confidential data (such as the PAN), it must be encrypted.
recurFreq	C	Recurring frequency for PAReq/AReq Purchase. Recur.frequency (integer days, 28 means monthly). Required for recurring transactions.
recurEnd	C	Recurring end date for PAReq/AReq format YYYYMMDD, if recurFreq is present then recurEnd is required.
installments	C	Number of Installments for PAReq/AReq. Purchase.install integer value >1 and <=999. Install and recurring parameters can not be present at the same time. Required for transactions with installments.
panMode	O	Possible values: VPOSToken – to indicate that instead of real pan pan parameter will contain VPOS token.
3DS 2.x general extra fields (reflecting the fields of EMVCo spec)
TDS2.acctID	O	Variable string..64 extra account info
TDS2.acctType	O	Fixed str 2: 01 = Not Applicable, 02 = Credit, 03 = Debit
TDS2.addrMatch	O	Fixed string Y/N: Y = Shipping Address matches Billing Address. N = Shipping Address does not match Billing Address.
TDS2.cardholderName	R	Var string 2..45. Cardholder name. Greek characters not allowed.
TDS2.email	R	Var string ..254 .Format name@domain.tld
TDS2.homePhone	O	Var string ..19 (..3-..15): Home phone format cc-subscriber 1-686123456.
TDS2.mobilePhone	O	Var string ..19 (..3-..15): Mobile phone format cc-subscriber 1-686123456.
TDS2.workPhone	O	Var string ..19 (..3-..15): Work phone format cc-subscriber 1-686123456.
TDS2.messageCategory	O	Fix string 2: 01 = PA(payment), 02 = NPA(non-payment), defaults to 01
TDS2.messageVersion	O	In case it is required to force MPI to use particular message version for this transaction (in case MPI and Issuer supports it). If not supported, then MPI will use one of supported messageVersion-s Format: 2.0.1 or 2.1.0 Length: 5. Mostly for specific testing only. Not recommended to be used as MPI resolves on its own appropriate version.
TDS2.purchaseDate	O/C	Purchase date in GMT: Format YYYYMMDDHHMMSS. Optional for normal purchases and will de defaulted to current time. Shall be present for installments and recurrings and set to original purchase agreement date.
TDS2.transType	O	Fix string 2: 01 = Goods/ Service Purchase 03 = Check Acceptance, 10 = Account Funding, 11 = Quasi-Cash Transaction, 28 = Prepaid Activation and Load
TDS2.threeDSRequestor3RIInd	O	Fix string 2: Unsure its use case: 01 = Recurring transaction 02 = Installment transaction, 03 = Add card,04 = Maintain card information, 05 = Account verification. (this is field threeRIInd in case of 2.1), to be used only if deviceCategory=6.
TDS2.threeDSRequestorAuthenticationInd	O	Type: string Length: 2 Accepted values: 01 – Payment, 02 -recurring, 03 – instalment, 04 – add card, 05 – maintain card, 06 – verification as part token EMV token ID
TDS2.threeDSRequestorChallengeInd	O	Fix string 2. Challenge request prefrences indicator. 01 = No preference 02 = No challenge requested, 03 = Challenge requested: 3DS Requestor Preference, 04 = Challenge requested: Mandate
TDS2.threeDSRequestorID and TDS2.threeDSRequestorID.{schemaId}	O	Type: string Length: 1-35. Note: Normally filled by MPI from its configuration *** If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS2.threeDSRequestorName and TDS2.threeDSRequestorName.{schemaId}	O	Type: string Length: 1-40 Note: Normally filled by MPI from its configuration *** If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS2.threeDSRequestorNPAInd	O/R	Fix string 2, unsure of use case: 01 = Add card, 02 = Maintain card information, 03 = Cardholder verification as part of EMV token ID&V According to EMVCo 3DS Spec Required if TDS2.messageCategory is 02
TDS2.threeDSRequestorURL	O	Fully qualified URL of 3DS Requestor website or customer care site. If not provided, then url will be taken from merchant config in database. Length: Var string..2048 (applies also for 3DS1) Example: http://server.domainname.com
TDS2.challengeWindowSize	O	Desired challenge window size for 2.x. Number 2. Values accepted 01 = 250 x 400, 02 = 390 x 400, 03 = 500 x 600, 04 = 600 x 400, 05 = Full screen
TDS2.payTokenInd	O	Type: string, Length: 4
TDS1.acquirerBIN and TDS1.acquirerBIN.{schemaId}	O	Type: numeric, Used as first priority if 3DS1 and present. Length: 1-11 (if present overrides acqBIN ***). If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS2.acquirerBIN and TDS2.acquirerBIN.{schemaId}	O	Type: numeric Length: 1-11 (if present overrides acqBIN ***) If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS1.acquirerMerchantID and TDS1.acquirerMerchantID.{schemaId}	O	Type: string. Used as first priority if 3DS1 and present. Length: 1-35 (if present overrides merchantId, ***). If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS2.acquirerMerchantID and TDS2.acquirerMerchantID.{schemaId}	O	Type: string Length: 1-35 (if present overrides merchantId, ***) If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS2.merchantName	O	Type: string (applies also for 3DS1 if merchantName not set) Length: 1-40 (if present overrides merchantName, **)
TDS2.mcc and TDS2.mcc.{schemaId}	O	Type: numeric Length: 4 (if present overrides mcc in profile ***) If You have multiple schema values and unsure with what schema card goes to send schema specific values for all possible schemas
TDS2.merchantCountryCode	O	Type: numeric Length: 3 (if present overrides country code in profile ***)
*** Effective only if merchant PSP mode (3DS1 effect also)
** Effective only if merchant PSP or Multi named mode (3DS1 also)
3DS 2.0 Merchant Risk fields
TDS2.mriShipIndicator	O	Format 2 numeric characters, See table A.7.2 EMVCO spec
TDS2.mriDeliveryTimeframe	O	Type: numeric, Length: 1-2
TDS2.mriDeliveryEmailAddress	O	Format up to 254 numeric characters eamil, See table A.7.2 EMVCO spec
TDS2.mriReorderItemsInd	O	Type: numeric, Length: 1-2
TDS2.mriPreOrderPurchaseInd	O	Type: numeric, Length: 1-2
TDS2.mriPreOrderDate	O	Format 8 character, date YYYYMMDD See table A.7.2 EMVCO spec
TDS2.mriGiftCardAmount	O	Format max len 15 numeric value in minor units.
TDS2.mriGiftCardCurr	O	Format 3 numeric characters ISO4217
TDS2.mriGiftCardCount	O	Format 2 numeric characters
3DS 2.0 extra account info fields
TDS2.chAccAgeInd	O	Length of time that the cardholder has had the account with the 3DS Requestor. Format and values according to EMVCo specification
TDS2.chAccDate	O	Fix YYYYMMDD, Date that the cardholder opened the account at merchant
TDS2.chAccChangeInd	O	Length of time since the cardholder’s account information with the 3DS Requestor was last changed. Including Billing or Shipping address, new payment account, or new user(s) added. Format and values according to EMVCo specification
TDS2.chAccChange	O	Fix YYYYMMDD, Date that the cardholder’s account with the 3DS Requestor was last changed. Including Billing or Shipping address
TDS2.chAccPwChangeInd	O	Length of time since the cardholder’s account with the 3DS Requestor had a password change or account reset. Format and values according to EMVCo specification
TDS2.chAccPwChange	O	Fix YYYYMMDD, Date that cardholder’s account with the 3DS Requestor had a password change or account reset.
TDS2.nbPurchaseAccount	O	Var num string..4: Number of purchases with this cardholder account during the previous six months.
TDS2.provisionAttemptsDay	O	Var num string..3: Number of Add Card attempts in the last 24 hours.
TDS2.txnActivityDay	O	Var num string..3: Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous 24 hours.
TDS2.txnActivityYear	O	Var num string..3: Number of transactions (successful and abandoned) for this cardholder account with the 3DS Requestor across all payment accounts in the previous year.
TDS2.shipAddressUsageInd	O	Indicates when the shipping address used for this transaction was first used with the 3DS Requestor. Format and values according to EMVCo specification
TDS2.shipAddressUsage	O	Fix YYYYMMDD, Date when the shipping address used for this transaction was first used with the 3DS Requestor
TDS2.shipNameIndicator	O	Type: numeric, Length: 1-2
TDS2.paymentAccInd	O	Indicates the length of time that the payment account was enrolled in the cardholder’s account with the 3DS Requestor. Format and values according to EMVCo specification
TDS2.paymentAccAge	O	Fix YYYYMMDD, Date that the payment account was enrolled in the cardholder’s account with the 3DS Requestor.
TDS2.suspiciousAccActivity	O	Indicates whether the 3DS Requestor has experienced suspicious activity (including previous fraud) on the cardholder account. Type: numeric Length: 1-2
3DS 2.0 extra billing addres fields (may be required by some schemas)
TDS2.billAddrCity	R	Var string..50, City.
TDS2.billAddrCountry	R	Fix num 3, country code 3166-1 numeric. For Kosovo, use Serbia’s country code
TDS2.billAddrLine1	R	Var string..50, Address line 1. Recommended to avoid special characters.
TDS2.billAddrLine2	O	Var string..50, Address line 2. Recommended to avoid special characters.
TDS2.billAddrLine3	O	Var string..50, Address line 3. Recommended to avoid special characters.
TDS2.billAddrPostCode	R	Var string 16, Zip code
TDS2.billAddrState	O	Billing address state (str 2 3166-2 country subdivision code). This value only applies to countries that have states (e.g USA). For Greece, strongly recommended to be omitted
3DS 2.0 extra shipping addres fields
TDS2.shipAddrCity	C	Var string..50, City. Recommended in case of shipping of goods.
TDS2.shipAddrCountry	C	Fix num 3, country code 3166-1 numeric. Recommended in case of shipping of goods.
TDS2.shipAddrLine1	C	Var string..50, Address line 1. Recommended in case of shipping of goods. Recommended to avoid special characters.
TDS2.shipAddrLine2	O	Var string..50, Address line 2. Recommended to avoid special characters.
TDS2.shipAddrLine3	O	Var string..50, Address line 3. Recommended to avoid special characters.
TDS2.shipAddrPostCode	C	Var string 16, Zip code. Recommended in case of shipping of goods.
TDS2.shipAddrState	O	Var str 2 3166-2 country subdivision code. Recommended in case of shipping of goods. This value only applies to countries that have states (e.g USA). For Greece, strongly recommended to be omitted
3DS 2.0 extra authentication info Information about how the 3DS Requestor authenticated the cardholder before or during the transaction.
TDS2.AIAuthMethod	O	Fix num 2: 01 = No 3DS Requestor authentication occurred (i.e. cardholder “logged in” as guest) 02 = Login to the cardholder account at the 3DS Requestor system using 3DS Requestor’s own credentials 03 = Login to the cardholder account at the 3DS Requestor system using federated ID 04 = Login to the cardholder account at the 3DS Requestor system using FIDO Authenticator (maps to threeDSReqAuthMethod)
TDS2.AIAuthTimestamp	O	Date YYYYMMDDHHMM, Date and time in UTC of the cardholder authentication. (maps to threeDSReqAuthTimestamp)
TDS2.AIAuthData	O	Var str 2048. Data that documents and supports a specific authentication process. (maps to threeDSReqAuthData)
3DS 2.0 extra authentication info Information about how the 3DS Requestor authenticated the cardholder as part of a previous 3DS transaction.
TDS2.PAIRef	O	Var sting 36. (threeDSReqPriorRef) This data element contains a ACS Transaction ID for a prior authenticated transaction
TDS2.PAIAuthMethod	O	Fir num 2. (threeDSReqPriorAuthMethod) Mechanism used by the Cardholder to previously authenticate to the 3DS Requestor. 01 = Frictionless authentication occurred by ACS 02 = Cardholder challenge occurred by ACS
TDS2.PAIAuthTimestamp	O	Date YYYYMMDDHHMM UTC. Date and time in UTC of the prior cardholder authentication.
TDS2.PAIAuthData	O	Var strr 2048. (threeDSReqPriorAuthData) Data that documents and supports a specific authentication process.
signature	R	Base64 encoded value of signature (RSA with SHA2-256) of all the field values above concatenated together having “;” semicolon in between (including trailing semicolon after the last value). signature=base64(RSA with SHA2-256(utf8bytes(value1;value2;…;value n;) ) ) If missing or mismatching error is displayed and request in not further processed. Requests are signed by merchant private key and validated with merchant Certificate (merchant certificate generation is referred to section 2.2)

2.2 Calculation of the Signature

The digest in the incoming POST and in the return POST is calculated by the following rule.
1. Concatenate all the values of all the possible fields with semicolon “;” in between (including trailing
semicolon after the last value) as listed and in same order as in the table. If a parameter is missing
(not sent) or sent value is empty string “”, then value and separator is not concatenated.
2. Calculate RSA with SHA2-256 signature of step 1 (using of UTF-8 char encoding when converting
string to bytes) using your private key.
3. Return the signature in base64 encoded form.
Notes: Never implement the signature calculation in the browser using JavaScript or similar as this way you expose
your private key to the world. Only implement it on server side executed code as (jsp/servlet/asp/php etc.).
For example:
Signature=base64(RSA with SHA2-256( utf8bytes(value1;value2;…;value n;) ) )

Example code for Java users:

java.security.PrivateKey privateKey = getPrivateKey(); //fetch your private key
java.security.Signature signature = Signature.getInstance(“SHA256withRSA”);
signature.initSign(privateKey);
signature.update(concatenatedValues.toString().getBytes(StandardCharsets.UTF_8));
byte[] sigBytes=signature.sign();
String sigStr=Base64.encode(sigBytes);

Example for .Net users:

https://docs.microsoft.com/en-us/dotnet/api/system.security.cryptography.rsacryptoserviceprovider.signdata?
view=netframework-4.7.2
See also sigexample.cs
public static string sign(string valueToSign, String privateKey)
{
byte[] keybytes= parseKey(privateKey);
byte[] toSign = System.Text.Encoding.UTF8.GetBytes(valueToSign);
RSACryptoServiceProvider RSAalg = DecodePrivateKeyInfo(keybytes);
byte[] signature=RSAalg.SignData(toSign, “SHA256”); //RSAwithSHA256
string sigStr= Convert.ToBase64String(signature);
return sigStr;
}

a) Java keytool:
keytool -genkeypair -keyalg RSA -sigalg SHA256withRSA -alias merchant -keystore merchant.p12 –
storepass mypassword -validity 1440 -keysize 2048
keytool -export -alias merchant -keystore merchant.p12 -rfc -file merchant_x509.cer
b) Or using openssl:
openssl req -sha256 -newkey rsa:2048 -nodes -keyout merchant.pem -x509 -days 1440 -out merchant_x509o.cer

2.3 Redirection to ACS

The MPI Server generates a redirection page, which includes a form that is posted to the ACS. The format of this
page depends on the channel. PAReq redirection-default templates of different channels are defined in WEBINF/templates xsl files.

2.4 Returning from MPI Server to Merchant Site

The standard method for returning control back from the MPI Server to the merchant is a redirection through the user
browser.
The standard control flow after receiving the PARes (or CPRS with condensed messages) is:
1. ACS Posts the PARes back to MPI Server via the user browser using the redirection.
2. MPI Server determines the status of the transaction and posts the status values to merchant payment page via
the user browser using the redirection.
3. Merchant server continues with authorization and after the authorization displays the confirmation page to
the user.

2.5 Parameters of return POST from MPI Server

The following table describes the parameters of the POST to okURL or failURL by Modirum MPI.

Field	Required / Optional	Description
version	R	Version of Modirum MPI HTTP POST protocol. Copied from the HTTP POST request. Currently 4.0
merchantID	R	From merchantID field of the incoming POST
xid	R	From xid field of the incoming POST
merchantTxId	C	From merchantTxId of the incoming POST if provided
mdStatus	R	End status of the transaction. mdStatus field provides all the information that is needed to determine, how to manage the transaction in the merchant system See section 2.6 Modirum MPI Transaction mdStatus
mdErrorMsg	R	Up to 128 chars alphanumeric description of the error.
veresEnrolledStatus	R	The actual value of veres enrollement status like “Y”, “N”, “U” or “-” if value is not available due errors etc. (since 4.0.2.31). Note: In case of UPOP protocol this value is always Y except status response code 77. In case of 3DS2 this is set to Y if directory is contacted.
paresTxStatus	R	The actual value of pares tx status “Y”, “N”, “U”, “A”, “R”, “C” or “-” if value is not available due errors or not enrolled. (since 4.0.2.31) Note: In case of UPOP protocol this value is equal to activateStatus (Y, A, F, L, N) if respCode is 00. – in case respcode 77 and ant other respcode cases N (not authenticated). In case of 3DS2 this is ARes or RRes transStatus whatever was latest event.
iReqCode	O	Two-digit numeric code provided by ACS indicating data that is formatted correctly, but which invalidates the request. This element is included when business processing cannot be performed for some reason. Never provided if mdStatus=0. 3-D Secure iReqCode field. Note: In case of UPOP protocol this value is equal to respCode if respCode is not 00.
iReqDetail	O	May identify the specific data elements that caused the Invalid Request Code (so never supplied if Invalid Request Code is omitted). See Table 20 on page 60 for details. Note: In case of UPOP protocol this value is equal to respMsg if respCode is not 00.
vendorCode	O	Error message describing iReqDetail error.
eci	O	Electronic Commerce Indicator With Visa cards, the value to be passed in Authorization Message (exactly 2 decimal digits). ECI fields determine the final status of the transaction See section 2.6 Modirum MPI Transaction mdStatus
cavv	O	Cardholder Authentication Verification Value Determined by ACS. Contains a 20-byte value that has been Base64 encoded, giving a 28 byte result. Some Visa regions may require that this value be included in the VIP authorization message (Visa EU is not using CAVV as of 10.10.02). Note: In case of UPOP protocol this value is equal to UPOP vcode.
cavvAlgorithm	O	A positive integer indicating the algorithm used to generate the Cardholder Authentication Verification Value. Current defined values are: 0 = HMAC (as per SET™ TransStain) 1 = CVV 2 = CVV with ATN 3 = MasterCard AAV Note that the value is copied directly from the PARes/RReq message. From MD field of the incoming POST
MD	O
PAResVerified	O	If signature validation of the return message is successful, the value is true. If PARes message is not received or signature validation fails, the value is false. (Compliance testing facility requirement). If signature validation is omitted the value will be empty In case of 2.x there is no signatures but signature valid flag is set to true for backward compability, as data is trusted from mutual TLS authentication.
PAResSyntaxOK	O	If PARes validation is syntactically correct, the value is true. Otherwise value is false. (Compliance testing facility requirement)
protocol	O	Protocol used in processing eg: 3DS1.0.2, 3DS2.1.0, SP5 Will be present if processing started. Note: new Since 4.0.1.54
cardType	O	Card type resolved by MPI if not in request or same value as in request. Note: new Since 4.0.1.54
fssScore	O	Fraud score calculated by the Modirum FSS. Present if the MPI is configured for use with the FSS, if setting fss.includeScoreInResponse has been set to true and if the score is available.
3DS 2.x general fields
TDS2.transStatus	O/C	Provided if available (means if 3DS2)
TDS2.transStatusReason	O/C	Provided if available Since 4.0.2.54
TDS2.threeDSServerTransID	O/C	Provided if available
TDS2.dsTransID	O/C	Provided if available
TDS2.acsTransID	O/C	Provided if available
TDS2.acsRenderingType	O/C	Provided if available
TDS2.acsReferenceNumber	O/C	Provided if available
TDS2.acsSignedContent	O/C	Provided if available and request deviceCategory = 5
TDS2.authTimestamp	O/C	Provided if available YYYYMMDDHHMM, 3DSServer set timestamp of authentication received in GMT (may change in future)
TDS2.messageVersion	O/C	3DS Message version used. (example 2.1.0 or 2.0.1) Since 4.0.2.54
TDS2.acsChallengeMandated	O/C	Provided if available Since 4.0.2.54
TDS2.authenticationType	O/C	Provided if available Since 4.0.2.54
TDS2.acsOperatorID	O/C	Provided if available Since 4.0.2.54
TDS2.cardholderInfo	O/C	Provided if available. If provided. Merchant shall show contents of this field to cardholder. Since 4.0.2.54
TDS2.acsUrl	O/C	Provided if available Since 4.0.2.54
TDS2.challengeCancel	O/C	Provided if available Since 4.0.2.56
TDS2.AResExtensions	O	Contains ARes.messageExtension content if it was present in message. Example: [{“name”:”name”,”id”:”id”,”criticalityIndicator”: false,”data”: {“text”:”test”}} {…}]
TDS2.RReqExtensions	O	Contains RReq.messageExtension content if it was present in message. Example: [{“name”:”name”,”id”:”id”,”criticalityIndicator”: false,”data”: {“text”:”test”}} {…}]
TDS2.threeDSRequestorDec MaxTime	O	Indicates the maximum amount of time that the 3DS Requestor will wait for an ACS to provide the results of a Decoupled Authentication transaction (in minutes). Numeric values between 1 and 10080 accepted.
TDS2.acsDecConInd	C	Indicates whether the ACS confirms utilisation of Decoupled Authentication and agrees to utilise Decoupled Authentication to authenticate the Cardholder.
TDS2.acsInfoInd	O	Comma separated list of acsInfoInd values of the range to which the pan belongs (EMVCO 3DS 2.2 or higher). Toggled by setting.
TDS2.AResBroadInfo	C	Contains ARes.broadInfo content if it was present in the message. Example: {“category”:”01″, “description”:”Variable maximum 4000 characters”, “expiryDate”:”202412″, “importance”:”02″,”recipients”:”02″,”source”:”01″} Since 4.0.2.68
signature	R	Base64 encoded value of signature (RSA with SHA2-256) of all the field values above concatenated together having “;” semicolon in between (including trailing semicolon after the last value). Signature = base64(RSA with SHA2-256(utf8bytes(value1;value2;…;value n;) ) ). If missing or mismatching, do not continue to payment as may be counterfeit or error message. Responses are signed by processor private key and validated with Processor certificate (processor certificate is referred to Section 5. page 51)

Note: In case of deviceCategory = 5 then no html is returned but name value pairs content only in application/xwww- form-urlencoded format. Response to service query also returns this set of parameters in application/x-wwwform-urlencoded format.

2.6 Modirum MPI Transaction mdStatus

mdStatus and eci fields
Modirum MPI returns many fields in the HTTP POST return interface, but there are two fields that have the most
significance from business transaction management point of view.

• mdStatus field provides all the information that is needed to determine, how to manage the transaction in
the merchant system:
➢ 0 = Not Authenticated, do not continue transaction
➢ 1 = Fully Authenticated, continue transaction
➢ 2 = Not enrolled (3DS1 only, may continue to transaction)
➢ 3 = Not enrolled cache (not used, was used in early 3DS1)
➢ 4 = Attempt (Proof of authentication attempt, may continue to transaction)
➢ 5 = U-received (grey area, continue to transaction depends schema rules)
➢ 6 = Error received (from Directory or ACS)
➢ 8 = Block by Fraud Score (used only if set up with FSS and scores configured)
➢ 9 = Pending (this code is not sent in red, internal, status only, except XML API or SDK in challenge)
➢ 50 = Execute 3DS method and continue to authentication (XML API or SOAP only
in return EnrollmentRequest(initial)).
➢ 51 = No 3DS method and continue to authentication (XML API or SOAP only in
return).
➢ 60 = Action completed, not sent only used internally for PReq result updates.
➢ 80 = Skip device case (no 3DS performed as device known not well capable)
➢ 81 = Skip challenge because requestor challenge ind (02 = No challenge requested)
➢ 88 = Skip 3DS because low risk (used only if with FSS and scores configured)
➢ 91 = Network error
➢ 92 = Directory error (read timeout)
➢ 93 = Configuration error
➢ 94 = Merchant input errors (also if merchant posted CRes not matching current tx state by RReq)
➢ 95 = No directory found for PAN/cardtype
➢ 96 = No version 2 directory found for PAN/cardtype
➢ 97 = If transaction not found on continue or service query
➢ 99 = System error (mpi unexpected error)
• eci field is relevant in Visa infrastructure, because there are certain business rules of how to fill the field into
the authorization messages. However, in Modirum MPI, eci field is filled only if the field is provided from
the ACS in the PARes message (as specified in the protocol spec). The value should then be passed to the
Visa authorization infrastructure as such.

Note the following recommendations:
– Firstly, check mdStatus to determine the final status of the transaction.
– The protocol specification requires passing the eci field as such to the authorization infrastructure if it is provided
in the PARes message (2.x ARes or PReq). Modirum MPI has value in eci field only if it has been provided in the
PARes message (2.x ARes or PReq).
Based on the current understanding of the Visa infrastructure business rules (note that this information is not
necessarily accurate and needs to be checked with Visa), the following eci values are recommended to be used in
authorization infrastructure:
• 6 = Non-participation and attempts (issuer liability).
• 9x = Service unavailable or system errors (transaction can proceed with the TLS/SSL-secured liability
rules, merchant has the liability).
• No value, if authentication or signature check fails

Fully Authenticated Transactions
In fully authenticated transactions, the issuer and cardholder are participating in the 3-D Secure protocol, cardholder
authentication has been successful and signature has been validated.
Scenarios:
• Valid PARes or CPRS message has been received with status Y and the signature has been validated
successfully. Or in 2.x ARes or PReq has transStatus Y.
Values:
• mdStatus = 1
• MPI ECI is copied as such from the PARes or 2.x ARes or PReq (often 05 for Visa and 01 for MasterCard).
• Visa authorization ECI value 5 (note that this must be verified from Visa).

Non-participation and Not Enrolled Transactions
In the case, where the card issuer or cardholder is not participating to the 3-D Secure, the transaction can still be
completed. Business rules of this case depend on the card scheme. Also, the MPI may determine the non-participation
based on the card range missing from the cache.
Scenarios:
• VERes message has been received with status N (there is no difference with the issuer not participating
compared with the cardholder not participating).
• MPI uses cache and cannot find the card range in the cache.
Values:
• mdStatus = 2 if card not participating, or mdStatus = 3 if range not in cache.
• MPI ECI is empty.
• Visa authorization ECI value 6 (note that this must be verified from Visa).

Attempts
In 3-D Secure version 1.0.2, an attempt functionality was introduced. ACS implementations may produce signed
attempt-messages even in the cases where the issuer or cardholder is not participating.
Scenarios:
• ACS has produced PARes with A status and signature validation has been successful (can be issuer specific
ACS or centralized attempt-server). In 2.x in case ARes or PReq transStatus is A.
Values:
• mdStatus = 4
• MPI ECI is copied as such from the PARes

Authentication Errors
If authentication is not successful, the transaction should not be continued in those cases where the failure is fatal.
Scenarios:
• ACS has provided PARes with status N (e.g too many false passwords or signature check has failed)
• PARes signature validation has failed.
• In case of 2.x ARes or PReq transStatus is N, R
Values:
• mdStatus = 0
• MPI ECI is empty.
• Visa authorization ECI value is not relevant, because transaction cannot be continued (note that this must be
verified from Visa).

Authentication Unavailable
In some cases, the authentication may not be available. The unavailable status may come from the directory server or
ACS or it may be related to some data communication problems.
Scenarios:
• Directory server produces VERes message with U status or 2.x ARes or PReq transStatus is U.
• Directory server produces VERes or ACS PARes message with U status (e.g mobile protocol not supported).
• No connection to the directory server.
Values:
• mdStatus = 5
• MPI ECI is empty.
• Visa authorization ECI value 7 (note that this must be verified from Visa).

3-D Secure Errors
3-D Secure related error situations are managed separately.
Scenarios:
• Invalid input field in 3-D Secure message generation
• Merchant authentication in directory server fails
• Error message received from DS or ACS
Values:
• mdStatus = 6
• MPI ECI is empty
• Visa authorization ECI value 7 (note that this must be verified from Visa)

Merchant data errors
If merchant request was invalid or incomplete then:
Values:
• mdStatus = 94
• MPI ECI is empty
• Visa authorization ECI value 7 (note that this must be verified from Visa)

System, networks or directory errors
Sometimes Modirum MPI may produce some error messages related to MPI internal errors. In most cases, it is still
recommendable to proceed with the transaction if risk is small.
Scenarios:
• File system full or system misconfigurations.
• Database connection lost.
• Directory connection fails or response times out.
Values:
• mdStatus = 99, mdStatus = 92 or mdStatus = 93
• MPI ECI is empty
• Visa authorization ECI value 7 (note that this must be verified from Visa)

Fraud Score Block
If Modirum MPI is configured to use a fraud scoring service, the score is calculated prior to attempting 3-D Secure
authentication. If the score returned exceeds the allowable threshold, then the transaction is not submitted for
authentication.
Scenario:
• Fraud score received from scoring service exceeds configured threshold
Values:
• mdStatus = 8
• MPI ECI is empty
• Visa authorization ECI value is not relevant, because transaction cannot be continued with Visa infrastructure
(note that this must be verified from Visa)

Pending Transactions
If MPI has passed the PAReq or 2.x CReq to the ACS, the browser session has also moved away from the MPI.
Sometimes, the control may never come back to the MPI, which means that there will be a pending transaction in the
database for the time beeing.
Modirum MPI does not include a timer to react to the pending transactions, but this functionality needs to be
implemented at the merchant site.
The background direct post feature in MPI Server can be used to avoid using the user browser for redirection in
return. (This won’t help any if user does not return from ACS).
The control flow using background direct post feature is:
1. ACS Posts the PARes (2.x CRes) back to MPI Server via the user browser using the redirection
2. MPI Server determines the status of the transaction and post the status values to merchant payment page
using a background session directly from MPI Server to the Merchant payment page server.
3. Merchant server continues with authorization and after the authorization displays the confirmation page to
the session opened by the Merchant Server. The Merchant Server passes the page unchanged to the user
browser as a response page to the post in step 1.

Summary
The following table summarizes the end status scenarios of the Modirum MPI. The description of ECI values should
be placed into the authorization message in the case of Visa.
MPI provides ECI value only if it receives it from the ACS. If merchant receives the ECI from the MPI, that is the
value that should be placed in the authorization message. If the ECI value received from the merchant is empty, the
merchant should fill out the value prior to sending the authorization message. The suggested values are listed in Visa
ECI column. Since these values are schema and Visa region specific, please verify the rules with your local Visa
representative. MasterCard uses only ECI values 0,1,2 etc.Especially U cases (mdStatus=5) check schema published
rules, what if the best action, default recommended to not make authorization.

Explanation	Log	mdStatus	Eci returned	Visa ECI	Other notes
Authenticated
Fully authenticated transaction	green	1	From PARes/ ARes/PReq	Use MPI value	CAVV provided
Non-participation
Issuer or cardholder not enrolled	green	2	empty	6	VERes with N (3DS1 only)
Not in cache	green	3	empty	6	Deprecated functionality. Not used.
Authentication Attempt
Attempt receipt received and signature valid	green	4	From PARes/ ARes/PReq	Use MPI value	CAVV provided, PARes/ARes/RReq with A
Authentication Unavailable
Authentication unavailable	red	5	empty	7	VERes or PARes or ARes or RReq status normally “U”
3-D Secure Error	red	6	empty	7	Invalid field in 3-D Secure message generation, Error message received or directory server fails to validate the merchant
Network error	red	91	empty	7	If connection to directory times out
Directory error	red	92	empty	7	Directory response read timeout or other failure
Configuration errors	red	93	empty	7	Service disabled, invalid configuration directory deleted before processing ended etc
Input error	red	94	empty	7	Merchant request had errors
Error no directory	red	95	empty	7	No directory server found configured for PAN/card type
Error no version 2 directory	red	96	empty	7	No version2 directory server found configured for PAN/card type and flow requires version 2 processing (eg APP)
System error	red	99	empty	7
Authentication Not Attempted
Fraud Score blocked	red	8	empty		No Visa or MasterCard processing
Authentication Failed
Authentication failed	red	0	empty	Not allowed	PARes status normally “N”,ARes,RReq in N, R
Pares Signature not valid	red	0	empty	Not allowed
Pending
Pending transaction	yellow	9			PARes or RReq yet not received
Perform 3DS method and continue to authentication		50			XML API Only: Perform 3DS method in user browser and sent referencing continue enrollment request after. (fill xid txid in from resp)
Skipped Low risk		88			If MPI with FSS ans score below configured value then authentication skipped. (merchant own risk)
Skipped on request		81			if MPI setting TDS2.doChallenge.02=false and requestor challenge ind=02 and challenge requested by issuer. (merchant own risk)

One example of the merchant implementation is as follows:

• Process transactions normally for mdStatus 1, 2(3DS1 only) and 4
• Never shall process transactions for mdStatus 0, 5,6, 8 and 9x

3 XML Interface

Another way to add 3-D Secure support to existing Merchant site is to use XML interface of the Modirum MPI.

3.1 EMVCo 3DS 2.x protocol control flow

Browser based control flow:
1. Merchant payment page asks the user all the relevant payment data, such as card number, expiry, etc.
2. Merchant payment page creates EnrollementRequest (initial) calculates signature of Message element to be
posted to Modirum MPI, sets the signature to ModirumMPI message and posts the ModirumMPI XML to
Modirum MPI with Content-Type=application/xml. Note that Merchant should set termUrl parameter in the
request message. It should represent Merchant page url, where ACS will post (via user browser) CRes message
after user authentication.
3. Modirum MPI checks the card participation from the 3-D Secure directory published ranges and then:
a. If range participates in 3DS Method merchant is returned EnrollmentResponse with mdStatus=50
(perform 3DS method and continue with enrollment request). Upon receiving such response merchant
shall take html content from field TDSMethodContent and render user an intermediate page where this
content is placed into an invisible iframe and wait about 2..3 seconds (or until 3DSMethodcompletion
but normally not longer than 5 seconds (Note: EMVCo spec says up to 10 seconds). The merchant
supplied threeDSMethodNotificationURL is notified.
b. If merchant used TDS2.threeDSMethodNotificationURL in initial request then send new
EnrollmentRequest (continue) filling in only txId, xid, transientData (cloud mode only) and
TDS2.threeDSCompInd attribute if merchant used TDS2.threeDSMethodNotificationURL on its
own.
c. If range does not participate in 3DS Method then continues directly to step 4
4. MPI returns
a. If no errors and challenge was requested then response message contains field RedirectToACSForm
filled with content. It has to be sent to user browser so that user browser posts CReq to ACS for
authentication.
b. With error or final (frictionless) authentication results, 3DS flow ends. Based on results
merchant determines if to proceed authorization or not.
5. After ACS is finished with the user authentication, ACS returns the control to the Merchant. Merchant receives
CRes to termUrl (set in initial request) and sends PAResValidationRequest to the MPI with CRes field filled
with CRes content received. The MPI Server verifies the CRes and matches it with appropriate RReq from
directory and responds to Merchant with final outcome.
6. Based on returned parameters Merchant proceeds with transaction authorization or stops the transaction in
caseof error or authentication failure.

Diagram to illustrate 3DS2 XML API browser flow. Blue lines server to server communications, green lines user
browser redirects. Dashed lines when prior authentication 3DS method is required by ACS.

3.2 XML Parameters to be posted to MPI/3DS Server

The following table describes the XML parameters to be posted from the payment page to Modirum MPI. Interface
version has been upgraded to 4.0 which utilizes a signature element instead of a digest. The software still supports 3.0 and 2.0, but it is not recommended to use versions before 3.0.

Parameters	Type	Required/ Optional/Conditional	Description
ModirumMPI	Root element	R
Message	element	R
version	attribute, xsi:string	R	Version 4.0 of Modirum MPI protocol.
messageId	attribute, xsi:string	R	Unique alphanumeric message identifier for debugging purposes
md	attribute, xsi:string	R	The MD (“Merchant Data”) field: merchant state data that must be returned to the merchant. The content of this field is passed unchanged and without assumptions about its content to the return Message. This field is used to accommodate the different ways merchant systems handle session state. If the merchant system does not maintain state for a given shopping session, the MD can carry whatever data the merchant needs to continue the session. This field must contain only ASCII characters in the range 0x20 to 0x7E; Since version 4.0.2.15 characters ‘<‘ and ‘>’ are not allowed in this parameter. If other data is needed, the field must be Base64 encoded. The size of the field (after Base64 encoding, if applicable) is limited to 254 bytes. If MD includes confidential data (such as the PAN), it must be encrypted.
merchantId	attribute, xsi:string	R	ID to identify the merchant to Modirum MPI.
lang	attribute, xsi:string	O	Message attribute to specify context language (ISO 639-1 language code en, fi, sv, el, etc..)
RequestMessage	element	R/O	either RequestMessage or ResponseMessage should be present
EnrollmentRequest	element	R/O	either EnrollmentRequest or PAResValidationRequest should be present
Parameters	element	R
cardType	xsi:string	O	Card scheme can be defined explicitly. Values with 1..2 digits are valid. The value is matched to directory server entry that is mapped to the merchant with that particular cardType. The field can also be left empty, which means that the schema/directory server is determined from the card number (see Directory profile settings, cardtypes.xml for card type mappings, and merchant settings in mpimngr to map merchants with particular DS/Acquirer based on card type).
pan	xsi:string	R/-	Card number. 13-19 digit account number. The value may be: • the account number on the card Must be missing if cardEncData field is present
expiry	xsi:string	R/-	Expiration Date supplied to the merchant by cardholder (YYMM). Note that this field is not checked in most of the production ACS installations. Must be missing if cardEncData field is present
cardEncData	xsi:string	C	A base64 encoded value, from VPOS supported Client-side encryption library. If this field is present pan and expiry must be missing.
deviceCategory	xsi:string	O	Integer length 1, Indicates the type of cardholder device. Supported values are:0 = www, 1 = mobile, 4 dtv. Most cases this value shall be allways 0 as wap phones are no longer mainstream and may not be supported by ACSes. Default value is 0
purchAmount	xsi:string	R	Max. 12-digit numeric amount in minor units of currency with all punctuation removed. Examples: Display Amount USD 123.45 Purchase Amount 12345
exponent	xsi:string	R	Exponent number length 1. The minor units of currency specified in ISO 4217. For example, US Dollars has a value of 2; Japanese Yen has a value of 0. Provided
description	xsi:string	O	Purchase description. Brief description of items purchased, determined by the merchant. Maximum size is 125 characters, but merchant should consider the characteristics of the cardholder’s device when creating the field. Note: Most Issuers do not display the description to the user.
currency	xsi:string	R	Currency. Determined by merchant. ISO 4217, 3 digit numeric.
merchantName	xsi:string	O	Length: 1-25 characters Format: any characters. Send this parameter if you want to override PAReq.Merchant.name. By default it is taken from mpi database
xid	xsi:string	R	Unique transaction identifier determined by merchant. Contains a 20 byte statistically unique value that has been Base64 encoded, giving a 28-byte result.
merchantTxId	xsi:string	C	Unique transaction identifier determined by merchant. If present, the value will be validated in the database if it is already existing for the specified merchant. An error will be returned if found. A maximum of 40 characters is allowed. The parameter is required if the merchantTxIdRequired setting is set to true.
recurFreq	xsi:string	C	Recurring frequency for PAReq Purchase.Recur.frequency (integer days, 28 means monthly). Required for recurring transactions.
recurEnd	xsi:string	C	Recurring end date for PAReq. Format YYYYMMDD. If recurFreq is present then recurEnd is required.
installments	xsi:string	C	Number of Installments for PAReq.Purchase.install integer value >1 and <=999. Install and recurring parameters can not be present at the same time. Required for transactions with installments.
termUrl	xsi:string	R	URL of the merchant that MPI will insert as termUrl in ACS redirection template (also refferred as notificationURL in 3DS2). As a result after cardholder authentication ACS will return PARes/CRes to Merchant instead of MPI. Warning: some schemes may reject that URL if contains parameters (?…)
panMode	xsi:string	O	Possible values: VPOSToken – to indicate that instead of real pan pan parameter will contain VPOS token.
txId	xsi:long	C	Required if continue from 3DS method
transientData	xsi:long	C	Required if continue from 3DS method and present in response to perform 3ds method.
TDS2Attributes	element		3DS 2 related attributes
			<Attribute name=”name”>Value</Attribute>
			Valid attribute names:
		R	TDS2_BrowserIP
		R	TDS2_Navigator_language
		C	TDS2_Navigator_javaEnabled (Required when Navigator_jsEnabled = true; otherwise Optional.)
		R	TDS2_Navigator_jsEnabled
		C	TDS2_Screen_colorDepth (Required when Navigator_jsEnabled = true; otherwise Optional.)
		R	TDS2_Screen_height
		R	TDS2_Screen_width
		C	TDS2_TimezoneOffset (Required when Navigator_jsEnabled = true; otherwise Optional.)
		R	TDS2_UserAgent
		R	TDS2_BrowserAccept
			3DS 2.x general extra fields
			TDS2.acctID
			TDS2.acctType
			TDS2.addrMatch
			TDS2.cardholderInfo
		R	TDS2.cardholderName. Greek characters not allowed.
		R	TDS2.email. Format name@domain.tld
		O	TDS2.homePhone (cc (1..3)-subscriber (max 15))
		O	TDS2.mobilePhone (cc (1..3)-subscriber (max 15))
		O	TDS2.workPhone(cc (1..3)-subscriber (max 15))
			TDS2.messageCategory
			TDS2.purchaseDate
			TDS2.transType
			TDS2.threeDSRequestor3RIInd
			TDS2.threeDSRequestorAuthenticationInd
			TDS2.threeDSRequestorChallengeInd
			3DS 2.x Merchant Risk fields
			TDS2.mriShipIndicator
			TDS2.mriDeliveryTimeframe
			TDS2.mriDeliveryEmailAddress
			TDS2.mriReorderItemsInd
			TDS2.mriPreOrderPurchaseInd
			TDS2.mriPreOrderDate
			TDS2.mriGiftCardAmount
			TDS2.mriGiftCardCurr
			TDS2.mriGiftCardCount
			3DS 2.x extra account info fields
			TDS2.chAccAgeInd
			TDS2.chAccDate
			TDS2.chAccChangeInd
			TDS2.chAccChange
			TDS2.chAccPwChangeInd
			TDS2.chAccPwChange
			TDS2.nbPurchaseAccount
			TDS2.provisionAttemptsDay
			TDS2.txnActivityDay
			TDS2.txnActivityYear
			TDS2.shipAddressUsageInd
			TDS2.shipAddressUsage
			TDS2.shipNameIndicator
			TDS2.paymentAccInd
			TDS2.paymentAccAge
			TDS2.suspiciousAccActivity
			3DS 2.x extra billing address fields
		R	TDS2.billAddrCity
		R	TDS2.billAddrCountry
		R	TDS2.billAddrLine1. Recommended to avoid special characters. string..50
		O	TDS2.billAddrLine2. Recommended to avoid special characters. string..50
		O	TDS2.billAddrLine3. Recommended to avoid special characters. string..50
		R	TDS2.billAddrPostCode
		O	TDS2.billAddrState (Billing address state (str 2 3166-2 country subdivision code). this value only applies to countries that have states (e.g USA). For Greece, strongly recommended to be omitted)
			3DS 2.x extra shipping address fields
		C	TDS2.shipAddrCity. Recommended in case of shipping of goods.
		C	TDS2.shipAddrCountry. Recommended in case of shipping of goods.
		C	TDS2.shipAddrLine1. Recommended in case of shipping of goods. Recommended to avoid special characters. string..50
		O	TDS2.shipAddrLine2. Recommended to avoid special characters. string..50
		O	TDS2.shipAddrLine3. Recommended to avoid special characters. string..50
		C	TDS2.shipAddrPostCode. Recommended in case of shipping of goods.
		O	TDS2.shipAddrState. Var str 2 3166-2 country subdivision code. Recommended in case of shipping of goods. This value only applies to countries that have states (e.g USA). For Greece, strongly recommended to be omitted.
			3DS 2.x extra authentication info Information about how the 3DS Requestor authenticated he cardholder before or during the transaction.
			TDS2.AIAuthMethod
			TDS2.AIAuthTimestamp
			TDS2.AIAuthData
			3DS 2.x extra authentication info Information about how the 3DS Requestor authenticated the cardholder as part of a previous 3DS transaction.
			TDS2.PAIRef
			TDS2.PAIAuthMethod
			TDS2.PAIAuthTimestamp
			TDS2.PAIAuthData
			See formats in redirection section or emvco spec
			3DS 2.x other
			TDS2.threeDSMethodNotificationURL – optional send only if You want to detect 3DS method completion on Your pages, else set by mpi. Request to url shall be capable update to TDS2.threeDSCompInd to Y for transaction in question.
			TDS2.threeDSCompInd – Required in continue to enrollment if TDS2.threeDSMethodNotificationURL was set by merchant in initial request, else determined by MPI.
			Service Options
			SEOPT.redirectToACSFormat , optional values HTML or DATA if missing then both either EnrollmentRequest or PAResValidationRequest should be present. This element is sent to MPI during pares/cres/acpres validation step.
PAResValidationRequest	element	O/R
pares	xsi:string	O/R	pares message, that is returned from ACS should be passed to this parameter as is. Either pares or c64s should be present. 3DS1
c64s	xsi:string	O/R	c64s message, that can be returned from ACS should be passed to this parameter as is. Either pares or c64s should be present. 3DS1
cres	Xsi:string	O/R	CRes base64 url encoded in case of 3DS2.
ds:Signature	ds:SignatureType	O	The xml signature as defined https://www.w3.org/TR/xmldsig- core/ Canonicalization http://www.w3.org/TR/2001/REC-xml-c14n- 20010315 SignatureMethod Algorithm=”http://www.w3.org/2001/04/xmldsig- more#rsa-sha256” DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha2 56″ Requests are signed by merchant private key and validated with merchant Certificate. If missing or mismatching, error is displayed and the request is not further processed. Requests are signed by merchant private key and validated with merchant Certificate (merchant certificate generation is referred to section 2.2) Responses are signed by processor private key and validated with Processor certificate (processor certificate is referred to Section 5. page 51)
StatusRequest	element	O/R	The element represents XML status request for decoupled authentication XML flow. It’s used to check the status of the decoupled transaction
txId	xsi:long	R	Transaction ID

3.3 Calculation of the Signature
Signatures shall be calculated and verified according to documentation https://www.w3.org/TR/xmldsig-core/
Canonicalization method to be used is http://www.w3.org/TR/2001/REC-xml-c14n-20010315 SignatureMethod
Algorithm=”http://www.w3.org/2001/04/xmldsig-more#rsa-sha256”
DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha256″
The signed element is Message element referenced with its ID attribute named messageId. ID attribute is an attribute
which type in schema is defined as xsd:ID.
Messages sent by the merchant will be signed by the merchant’s private key and verified by the MPI using the
merchant’s certificate.
Note that the XML documents should be handled with namespace aware xml libraries (parser/serializer).
When the Message element is serialized and canonicalized it should also contain xmlns namespace attribute.
See from next section XML message with digest example. Canonicalized message starts for example as:
<Message xmlns=”http://www.modirum.com/schemas/mpiapi” md=”C62C2F592F1BCA32A24EA877CFF7A461″
merchantId=”0000001″ messageId=”M1523010167533″ version=”4.0″>…

Example code for java:
public static byte[] sign(ModirumMPI root, Marshaller m, DocumentBuilderFactory dbf, PrivateKey
prik, java.security.cert.X509Certificate[] crts) throws Exception
{
org.apache.xml.security.Init.init();
org.w3c.dom.Document document = dbf.newDocumentBuilder().newDocument();
m.marshal(root, document);// apis.normalizeDOM(dom); dom nomralization is very slow uing instead
msg.setIdAttribute(“messageId”, true);
Element modirumMPI = document.getDocumentElement();
org.apache.xml.security.signature.XMLSignature xmlsigAp =new XMLSignature(document,
null,”http://www.w3.org/2001/04/xmldsig-more#rsa-sha256″, “http://www.w3.org/TR/2001/REC-xml-c14n20010315”);
Element sigel = xmlsigAp.getElement();
modirumMPI.appendChild(sigel);
Element msg = (Element)modirumMPI.getFirstChild();
msg.setIdAttribute(“messageId”, true); // setting id attribute instead of dom normalization
xmlsigAp.addDocument(“#” + msg.getAttribute(“messageId”),
null, “http://www.w3.org/2001/04/xmlenc#sha256”, null, null);
for(int i = 0; crts != null && i < crts.length; i++)
{
xmlsigAp.addKeyInfo(crts[i]);
}
xmlsigAp.sign(prik);
ByteArrayOutputStream bos = new ByteArrayOutputStream(4096);
TransformerFactory transfac = TransformerFactory.newInstance();
Transformer trans = transfac.newTransformer();
trans.setOutputProperty(OutputKeys.OMIT_XML_DECLARATION, “no”);
trans.setOutputProperty(OutputKeys.INDENT, “no”);
trans.setOutputProperty(OutputKeys.ENCODING, “utf-8”);
DOMSource source = new DOMSource(document);
trans.transform(source, new StreamResult(bos));
return bos.toByteArray();
}

Notes: Never calculate signature in user browser using JavaScript or other script. Or You will expose Your private key to
the world. Before passing data to SHA-256 RSA signature function ensure string data is converted to bytes using UTF- 8
character encoding. Signatures should be calculated and checked during any communication with MPI be it request or response.

3.4 XML parameters to be returned to Merchant

Parameters	Type	Required / Optional	Description
ModirumMPI	element	R
ds:Signature	ds:SignatureType xmlns:ds=”http:// www.w3.org/ 2000/09/xmldsig#”	O	The xml signature as defined https://www.w3.org/TR/xmldsig-core/ Canonicalization http://www.w3.org/TR/2001/REC-xml-c14n-20010315 Signature Method Algorithm=”http://www.w3.org/2001/04/xmldsig-more#rsa- sha256” DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha256″
Message	element	R
version	attribute, xsi:string	R	Version 4.0 of Modirum MPI protocol.
messageId	attribute, xsi:string	R	Unique alphanumeric message identifier for debugging purposes
md	attribute, xsi:string	R	The MD (“Merchant Data”) field: merchant state data that must be returned to the merchant. The content of this field is passed unchanged and without assumptions about its content to the return Message.
			This field is used to accommodate the different ways merchant systems handle session state. If the merchant system can associate the final post with the original shopping session without any further assistance, the MD field may be empty. If the merchant system does not maintain state for a given shopping session, the MD can carry whatever data the merchant needs to continue the session.
			This field must contain only ASCII characters in the range 0x20 to 0x7E; Since version 4.0.2.15 characters ‘<‘ and ‘>’ are not allowed in this parameter. If other data is needed, the field must be Base64 encoded. The size of the field (after Base64 encoding, if applicable) is limited to 254 bytes. If MD includes confidential data (such as the PAN), it must be encrypted.
merchantId	attribute, xsi:string	R	ID to identify the merchant to Modirum MPI.
lang	attribute, xsi:string	O	Message attribute to specify context language (ISO 639-1 language code en, fi, sv, el, etc..)
ResponseMessage	element	O/R	either RequestMessage or ResponseMessage should be present
Parameters	element	R
xid	xsi:string	R	xid parameter from request message
merchantTxId	xsi:string	C	merchantTxId parameter from request message if provided
mdStatus	xsi:string	R	End status of the transaction. mdStatus field provides all the information that is needed to determine how to manage the transaction in the merchant system. See section 2.6 Modirum MPI Transaction mdStatus
mdErrorMsg	xsi:string	R	Up to 128 bytes alphanumeric description of the error.
enrollmenStatus	xsi:string	O	The actual value of veres enrollement status like “Y”, “N”, “U” or “-” if value is not available due errors etc. (since 4.0.2.31). In case of 3DS 2 this is set to Y if connection to directory is established.
authenticationStatus	xsi:string	O	The actual value of PARes tx status or ARes/RReq transStatus “Y”, “N”, “U”, “A”,”R” or “-” if value is not available due errors or not enrolled. (since 4.0.2.31)
eci	xsi:string	O	Electronic Commerce Indicator With Visa cards, the value to be passed in Authorization Message (exactly 2 decimal digits). ECI fields determine the final status of the transaction See section 2.6 Modirum MPI Transaction mdStatus
cavv	xsi:string	O	Cardholder Authentication Verification Value Determined by ACS. Contains a 20 byte value that has been Base64 encoded, giving a 28 byte result. Some Visa regions may require that this value be included in the VIP authorization message.
cavvAlgorithm	xsi:string	O	A positive integer indicating the algorithm used to generate the Cardholder Authentication Verification Value. Current defined values are: 0 = HMAC (as per SET™ TransStain) 1 = CVV 2 = CVV with ATN 3 = MasterCard AAV Note that the value is copied directly from the PARes message.
PAResVerified	xsi:string	O	If signature validation of the return message is successful, the value is true. If PARes message is not received or signature validation fails, the value is false. (Compliance testing facility requirement). If signature validation is omitted the value will be empty
PAResSyntaxOK	xsi:string	O	If PARes validation is syntactically correct, the value is true. Otherwise value is false. (Compliance testing facility requirement).
iReqCode	xsi:string	O	Two digit numeric code provided by ACS indicating data that is formatted correctly, but which invalidates the request. This element is included when business processing cannot be performed for some reason. Never provided if mdStatus=0. 3-D Secure iReqCode field.
iReqDetail	xsi:string	O	May identify the specific data elements that caused the Invalid Request Code (so never supplied if Invalid Request Code is omitted). See Table 20 on page 60 for details.
vendorCode	xsi:string	O	Error message describing iReqDetail error.
txId	xsi:long	O	MPI internal transaction id if available
transientData	xsi:string	O	Returned only if cloud mode and mdStatus=50
protocol	xsi:string	O	Authentication protocol used in processing. Such as 3DS1.0.2, 3DS2.1.0 or SP5 (Since 4.0.2.54)
cardType	xsi:string	O	Same value as in request or value resolved by MPI. (Since 4.0.2.54)
fssScore	xsi:int	O	Fraud score calculated by the Modirum FSS. Present if the MPI is configured for use with the FSS, if setting fss.includeScoreInResponse has been set to true and if the score is available.
redirectToACSForm	xsi:string	O	ACS redirection form raw HTML, containing all the required parameters to be posted to ACS or SecurePlus. PAReq, termUrl, MD and ACS url itself. Form should be presented to user as is. MPI does not set this parameter in response to PAResValidationRequest step.
redirectToACSFormData	Element	O	ACS redirection form data in elements, containing all the required parameters to be posted to ACS or SecurePlus. PAReq, termUrl, MD and ACS url itself.
TDSMethodContent	Element	O	A complete html fragment that need to be rendered in user browser if 3DS method requested for a card (in initial enrollment response)
TDS2RespAttributes	element		3DS2 related response attributes
Attribute	Element [0..n]	O	<Attribute name=”name”>Value</Attribute>
			Valid attribute names provided if available and applicable basis:
			TDS2.sdkTransID (only App)
			TDS2.transStatus
			TDS2.transStatusReason
			TDS2.threeDSServerTransID
			TDS2.dsTransID
			TDS2.acsTransID
			TDS2.acsRenderingType (only App)
			TDS2.acsReferenceNumber
			TDS2.acsSignedContent (only App)
			TDS2.authTimestamp
			TDS2.messageVersion
			TDS2.acsChallengeMandated
			TDS2.authenticationType
			TDS2.acsOperatorID
			TDS2.cardholderInfo
			TDS2.acsUrl
			TDS2.challengeCancel
			TDS2.ARresExtensions (in Ares, json as is)
			TDS2.RReqExtensions (in Rreq, json as is)
			TDS2.AReqToResMillis (since 4.0.2.56 time measurement of before sending AReq to Response received)
			TDS2.acsInfoInd Comma separated list of acsInfoInd values to which the pan belongs (EMVCO 3DS 2.2 or higher). Toggled by setting

3.5 Example XML messages for EMVCo protocol 2.x browser flow

3.5.1 Initial request to MPI

<?xml version=”1.0″ encoding=”utf-8″ standalone=”no”?>
<ModirumMPI xmlns=”http://www.modirum.com/schemas/mpiapi” xmlns:ns2=”http://www.w3.org/2000/09/xmldsig#”>
<Message md=”DAC72539C87D964E6649C4E0FD12336A” merchantId=”sys1331720664552″ messageId=”M1702393329407″ version=”4.0″>
<Request>
<EnrollmentRequest>
<Parameters>
<pan>4016360000000002</pan>
<expiry>2912</expiry>
<deviceCategory>0</deviceCategory>
<purchAmount>15000</purchAmount>
<exponent>2</exponent>
<description>DVD Movies</description>
<currency>978</currency>
<termUrl>https://alphaecommerce-test.cardlink.gr:443/coffeehouse/MerchantHandler2;jsessionid=DAC72539C87D964E6649C4E0FD12336A</termUrl>
<TDS2Attributes>
<Attribute name=”TDS2_Navigator_jsEnabled”>true</Attribute>
<Attribute name=”TDS2.cardholderName”>Test Customer</Attribute>
<Attribute name=”TDS2.email”>test@cardlink.gr</Attribute>
<Attribute name=”TDS2.mobilePhone”>30-6940123456</Attribute>
<Attribute name=”TDS2.billAddrCity”>C</Attribute>
<Attribute name=”TDS2.billAddrCountry”>300</Attribute>
<Attribute name=”TDS2.billAddrLine1″>S</Attribute>
<Attribute name=”TDS2.billAddrPostCode”>12345</Attribute>
</TDS2Attributes>
<xid>WZjpyh0QU+AG4NuEl/EL+6cvPWk=</xid>
<merchantTxId>7ed4fc96-b390-4404-9053-f8a796a4c303</merchantTxId>
</Parameters>
</EnrollmentRequest>
</Request>
</Message>
<ds:Signature xmlns:ds=”http://www.w3.org/2000/09/xmldsig#”>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm=”http://www.w3.org/2006/12/xml-c14n11″/>
<ds:SignatureMethod Algorithm=”http://www.w3.org/2001/04/xmldsig-more#rsa-sha256″/>
<ds:Reference URI=”#M1702393329407″>
<ds:DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha256″/>
<ds:DigestValue>WGF/Rx7uYs7h6Ur1XzR7P3TwkRW15UKwn+4GLFGEZ4A=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
5rrF8aLDBQ/skS4QQOHDiOOnPRPyPRNseIjhIQlFEjPnPTwJGwDvKI+L/W7cHxt+YO+aC1c/MUD9
MpA1LiUNRps3R/sEZ/20Ss9bYqAT50nnGlsBGhHBJ6IuZlBGFioGw6aXM6D+j+DY/pLg2j2jn/fb
ZreC2d2mGm4Xxnr2P1qyYfAh2Vgq5yel+U5n3Jjcm5wnIQ0+QdE752ydf+hROC/RP7wLf3D8Kdgf
df3/mDZe30laYbsRa9xnePrQgq5B+dOrIlbfs36I4UOtEHprevPoPeKjLbMuCFH5oP59KQqxk6MC
dGmdou/GGLDPh0GF2/1AJ+IWP38AFc+9Dg+M3g==
</ds:SignatureValue>
<ds:KeyInfo>
<ds:X509Data>
<ds:X509Certificate>
MIIESzCCAzOgAwIBAgIJANq6Drpt8SB5MA0GCSqGSIb3DQEBCwUAMHYxCzAJBgNVBAYTAkVFMREw
…
tmcgicP7sLWd4Pu1fAx+51tgDSGjh2m0SSDz2rv7CrJ44RXIUOWAMWbC4myssyea3t+GrSvWrDGH
RLXZUNmvy+zFSB+QFWEW2nlfYI8=
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature>
</ModirumMPI>

3.5.2 Response from MPI with 3DS Method redirection form

3.5.3 Request to MPI after 3DS Method

<?xml version=”1.0″ encoding=”utf-8″ standalone=”no”?>
<ModirumMPI xmlns=”http://www.modirum.com/schemas/mpiapi” xmlns:ns2=”http://www.w3.org/2000/09/xmldsig#”>
<Message merchantId=”sys1331720664552″ messageId=”M1702393332315″ version=”4.0″>
<Request>
<EnrollmentRequest>
<Parameters>
<txId>8470001</txId>
<xid>WZjpyh0QU+AG4NuEl/EL+6cvPWk=</xid>
<merchantTxId>7ed4fc96-b390-4404-9053-f8a796a4c303</merchantTxId>
</Parameters>
</EnrollmentRequest>
</Request>
</Message>
<ds:Signature xmlns:ds=”http://www.w3.org/2000/09/xmldsig#”>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm=”http://www.w3.org/2006/12/xml-c14n11″/>
<ds:SignatureMethod Algorithm=”http://www.w3.org/2001/04/xmldsig-more#rsa-sha256″/>
<ds:Reference URI=”#M1702393332315″>
<ds:DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha256″/>
<ds:DigestValue>38TlY7uGFW1rwHRgeyM5+qTIJZJcgk6dItquolszOnA=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
yDTMhLcG1aBkjGYige4cLR14TP8prE6CvvV0UCroLiUZ/+wpOzsgS8+F5GqJ3Rc3F2lsl6I/sxHW
wk0kTQ2FU97sXQP/FB8LzrNmhIiJKXZc9Q0P6UBgyromCq8QtUwKPhWx84hxHTFN4/+QzHU/HZ7Y
4GAht9EUQeFf+mTyz4ZEM5I8/jR6tJWBbbxZPk4pSsLeOwjJWLbIm1wu4OtnUDWWO5kw7BLB7lL8
+VgB4tAq4sd+paAmHxBJPli1jQOErMfGUnVCTSnbhZZ4mNph1UaNPx+rclySHJjbmN+A3P5XjWTG
g5nLH7jmJIGQn5cG6RsifNY7k+gQsK0hpWMQpA==
</ds:SignatureValue>
<ds:KeyInfo>
<ds:X509Data>
<ds:X509Certificate>
MIIESzCCAzOgAwIBAgIJANq6Drpt8SB5MA0GCSqGSIb3DQEBCwUAMHYxCzAJBgNVBAYTAkVFMREw
…
tmcgicP7sLWd4Pu1fAx+51tgDSGjh2m0SSDz2rv7CrJ44RXIUOWAMWbC4myssyea3t+GrSvWrDGH
RLXZUNmvy+zFSB+QFWEW2nlfYI8=
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature>
</ModirumMPI>

3.5.4 Response from MPI with CReq redirection form to ACS

<?xml version=”1.0″ encoding=”UTF-8″ standalone=”no”?><ModirumMPI xmlns=”http://www.modirum.com/schemas/mpiapi” xmlns:ns2=”http://www.w3.org/2000/09/xmldsig#”><Message md=”DAC72539C87D964E6649C4E0FD12336A” merchantId=”sys1331720664552″ messageId=”M1702393332315″ version=”4.0″><Response><Parameters><xid>WZjpyh0QU+AG4NuEl/EL+6cvPWk=</xid><merchantTxId>7ed4fc96-b390-4404-9053-f8a796a4c303</merchantTxId><mdStatus>9</mdStatus><mdErrorMsg>To be redirected to ACS</mdErrorMsg><enrollmenStatus>Y</enrollmenStatus><authenticationStatus>C</authenticationStatus><txId>8470001</txId><protocol>3DS2.2.0</protocol><cardType>1</cardType></Parameters><redirectToACSForm><html class=”no-js” lang=”en” xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<META http-equiv=”Content-Type” content=”text/html; charset=utf-8″>
<meta http-equiv=”Content-Type” content=”text/html; charset=utf-8″>
<meta charset=”utf-8″>
<title>3D Secure Processing</title>
<link href=”https://alphaecommerce-test.cardlink.gr/mdpaympi/static/mpi.css” rel=”stylesheet” type=”text/css”>
</head>
<body>
<div id=”main”>
<div id=”content”>
<div id=”order”>
<h2>3D Secure Processing</h2>
<script src=”https://alphaecommerce-test.cardlink.gr/mdpaympi/static/red.js” defer>/* needed for xsl to xhtml */</script>
<div id=”spinner”>
<img src=”https://alphaecommerce-test.cardlink.gr/mdpaympi/static/preloader.gif” alt=”Please wait..”>
</div>
<img src=”https://alphaecommerce-test.cardlink.gr/mdpaympi/static/verifiedbyvisa.png” alt=”Verified by VISA”>
<div id=”formdiv”>
<div>
<form id=”webform0″ name=”red2ACSv2″ method=”POST” action=”https://3ds-acs.test.modirum.com/mdpayacs/vW-8AVIG6hg_PKD_/creq;token=293545061.1702393335.pwBrIRuiK9HT3-KALa9nfjto8RiOzk9d_dK4yg-N_xU” accept_charset=”UTF-8″>
<input type=”hidden” name=”creq” value=”ewogICAiYWNzVHJhbnNJRCIgOiAiODQ4MTEwMjAtNzY1YS00ZjU1LWFlMzctMDgwNTIwZjVkNDg4IiwKICAgImNoYWxsZW5nZVdpbmRvd1NpemUiIDogIjAzIiwKICAgIm1lc3NhZ2VUeXBlIiA6ICJDUmVxIiwKICAgIm1lc3NhZ2VWZXJzaW9uIiA6ICIyLjIuMCIsCiAgICJ0aHJlZURTU2VydmVyVHJhbnNJRCIgOiAiNjVmZmQ2MTItMzI1Yi01NDA1LTgwMDAtMDAwMDAwODEzZGYxIgp9″><input type=”hidden” name=”threeDSSessionData” value=”DAC72539C87D964E6649C4E0FD12336A”><script type=”text/javascript”>
hideAndSubmitTimed(‘webform0’);
</script>
<noscript>
<div align=”center”>
<b>Javascript is turned off or not supported!</b>
<br>
</div>
</noscript>
<input type=”submit” name=”submitBtn” id=”submitBtn” value=”Please click here to continue”>
</form>
</div>
</div>
<noscript>
<div align=”center”>
<b>Javascript is turned off or not supported!</b>
<br>
</div>
</noscript>
</div>
<div id=”content-footer”></div>
</div>
</div>
</body>
</html>
</redirectToACSForm><redirectToACSFormData actionURL=”https://3ds-acs.test.modirum.com/mdpayacs/vW-8AVIG6hg_PKD_/creq;token=293545061.1702393335.pwBrIRuiK9HT3-KALa9nfjto8RiOzk9d_dK4yg-N_xU”><field name=”creq”>ewogICAiYWNzVHJhbnNJRCIgOiAiODQ4MTEwMjAtNzY1YS00ZjU1LWFlMzctMDgwNTIwZjVkNDg4IiwKICAgImNoYWxsZW5nZVdpbmRvd1NpemUiIDogIjAzIiwKICAgIm1lc3NhZ2VUeXBlIiA6ICJDUmVxIiwKICAgIm1lc3NhZ2VWZXJzaW9uIiA6ICIyLjIuMCIsCiAgICJ0aHJlZURTU2VydmVyVHJhbnNJRCIgOiAiNjVmZmQ2MTItMzI1Yi01NDA1LTgwMDAtMDAwMDAwODEzZGYxIgp9</field><field name=”threeDSSessionData”>DAC72539C87D964E6649C4E0FD12336A</field></redirectToACSFormData><TDS2RespAttributes><Attribute name=”TDS2.transStatus”>C</Attribute><Attribute name=”TDS2.threeDSServerTransID”>65ffd612-325b-5405-8000-000000813df1</Attribute><Attribute name=”TDS2.dsTransID”>7205089f-53c0-53cb-8000-00000a54b12d</Attribute><Attribute name=”TDS2.acsTransID”>84811020-765a-4f55-ae37-080520f5d488</Attribute><Attribute name=”TDS2.acsReferenceNumber”>3DS_LOA_ACS_MOMD_020100_00061</Attribute><Attribute name=”TDS2.messageVersion”>2.2.0</Attribute><Attribute name=”TDS2.acsChallengeMandated”>N</Attribute><Attribute name=”TDS2.authenticationType”>01</Attribute><Attribute name=”TDS2.acsOperatorID”>3DS_LOA_ACS_MOMD_020100_00061</Attribute><Attribute name=”TDS2.acsUrl”>https://3ds-acs.test.modirum.com/mdpayacs/vW-8AVIG6hg_PKD_/creq;token=293545061.1702393335.pwBrIRuiK9HT3-KALa9nfjto8RiOzk9d_dK4yg-N_xU</Attribute><Attribute name=”TDS2.AReqToResMillis”>808</Attribute></TDS2RespAttributes></Response></Message><ds:Signature xmlns:ds=”http://www.w3.org/2000/09/xmldsig#”>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm=”http://www.w3.org/TR/2001/REC-xml-c14n-20010315″/>
<ds:SignatureMethod Algorithm=”http://www.w3.org/2001/04/xmldsig-more#rsa-sha256″/>
<ds:Reference URI=”#M1702393332315″>
<ds:DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha256″/>
<ds:DigestValue>aPnWCtW+f6WThQPDswl2i63Y0tdE/ur8N0YL3mvg/kY=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
PlFGtFZCWUqwWqWk94JzF4JKOTP+X31k6SjHX1JhFuuAFHkDzFoEcyVdSdsCcZaf/QmXaQ9DIlfY
7F8mDTuUY4IDV69LfQ3JbE+DC2Eu19cU2spGNFZXXO7WVhFZ1hsOcnr2tKE3YlNpHwAhVBGpvSAS
xYPgLx/0aCLOlwcjcIY6eFmGZLrEzGpfqTH7rrwv/RKMOzEBYMK+lsSJeovH8B05Pgp37Xnj5e/b
pfnEzdxiJJ2rhOozJsv9sixVqrZvQwNFK7PiAf4NvxijpEdPCvCwLzX4a6R+5Xv7Zw2pYeNA+yhV
JbWth0efqNOoZu8clDB0Nb4UHR2FtADyIelAGn8Y3/QhtAnR63BRRPSMP9C0634hrqnrEtOuvlqB
o36NTFiwnI/UAic59f2X3tQnx8+0LyBsDSSyteq1N0WLhzhfZzL8LJQrOmR6fxW5i/OjS0Pv6at5
gu+3ibmikmPPl+VriNYXXJ5Ub6hnuquvxXpwKg2Dp9fSYqrFmOSEZ4xK
</ds:SignatureValue>
<ds:KeyInfo>
<ds:X509Data>
<ds:X509Certificate>
MIIEVTCCAr0CBGQm1T4wDQYJKoZIhvcNAQELBQAwbzEfMB0GA1UEAxMWQ2FyZGxpbmtNZXNzYWdl
…
uU46fkKXexUD92aI/d/F/Vv/LZORZ8Wt4eIEmpmWW08Xww7LEqDpzHyGZ5BNuHf6r5Yb1rmS1Z/L
PRu+VcI4Hy8081eP5rAcvjUTCjp6A9EwbDKsjH5K
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature></ModirumMPI>

3.5.5 Request to MPI with CRes

<?xml version=”1.0″ encoding=”utf-8″ standalone=”no”?>
<ModirumMPI xmlns=”http://www.modirum.com/schemas/mpiapi” xmlns:ns2=”http://www.w3.org/2000/09/xmldsig#”>
<Message md=”DAC72539C87D964E6649C4E0FD12336A” merchantId=”sys1331720664552″ messageId=”M1702393332315″ version=”4.0″>
<Request>
<PAResValidationRequest>
<cres>ewogICJhY3NUcmFuc0lEIiA6ICI4NDgxMTAyMC03NjVhLTRmNTUtYWUzNy0wODA1MjBmNWQ0ODgiLAogICJtZXNzYWdlVHlwZSIgOiAiQ1JlcyIsCiAgIm1lc3NhZ2VWZXJzaW9uIiA6ICIyLjIuMCIsCiAgInRocmVlRFNTZXJ2ZXJUcmFuc0lEIiA6ICI2NWZmZDYxMi0zMjViLTU0MDUtODAwMC0wMDAwMDA4MTNkZjEiLAogICJ0cmFuc1N0YXR1cyIgOiAiWSIKfQ</cres>
</PAResValidationRequest>
</Request>
</Message>
<ds:Signature xmlns:ds=”http://www.w3.org/2000/09/xmldsig#”>
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm=”http://www.w3.org/2006/12/xml-c14n11″/>
<ds:SignatureMethod Algorithm=”http://www.w3.org/2001/04/xmldsig-more#rsa-sha256″/>
<ds:Reference URI=”#M1702393332315″>
<ds:DigestMethod Algorithm=”http://www.w3.org/2001/04/xmlenc#sha256″/>
<ds:DigestValue>lJ9hxva3kAv1P6pbJQQ0XRp8uPWeSu8JwJe4rabhxGw=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>
SRfxtIHV+j8jM0eIvhnSpjsPqbg0nKWSc2H9QWHJ+/mbOmB3UJom8w8hFEnJzGtwPl1g8FD9Jbms
xqRHFPmOgVT0cLTZK2qzXATSwVZO/uQNBPlYCEPYmfZKEX57661Zr7GKhuQyBs0wU3dot0lEQGPo
ne9Oi+p+1r410GhoGvwGXQIDFxtJfmw9nvGNstiyNJ3ni7M8qUcdnzUEbmCCzsRnJPrY7Ys79/Ov
c13X7tEXVsSHo5Gt70q0ecmIpRGDCClNhHQPEnzN3lDWmVxCvETuz/h263lTOcu3Oi2u4hw1Y4vp
EAS0EwqlE8to5mLDgAGFIXuzur6AdzuIyqnq3Q==
</ds:SignatureValue>
<ds:KeyInfo>
<ds:X509Data>
<ds:X509Certificate>
MIIESzCCAzOgAwIBAgIJANq6Drpt8SB5MA0GCSqGSIb3DQEBCwUAMHYxCzAJBgNVBAYTAkVFMREw
…
tmcgicP7sLWd4Pu1fAx+51tgDSGjh2m0SSDz2rv7CrJ44RXIUOWAMWbC4myssyea3t+GrSvWrDGH
RLXZUNmvy+zFSB+QFWEW2nlfYI8=
</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
</ds:Signature>
</ModirumMPI>

3.5.6 Final response from MPI