This field is case sensitive.
Example: getAccessToken

The value of this parameter is provided to you by Merchant Warrior.
Example: 123456789abcd

The value of this parameter is provided to you by Merchant Warrior.
Example: 1a3b5c

The amount must be formatted to have two decimal places. Any amounts without two decimal places or amounts less than one cent will be rejected.
Example: 10.00

One of the following: AUD, CAD, EUR, GBP, JPY, NZD, SGD, USD. This is provider dependant. Please check with MW before attempting to process transactions in any currency other than AUD. This field is case insensitive.
Example: AUD

Asynchronous POST notifications will be sent to this URL.
Example: https://www.example.com/notify.php

The urlHash field is a combination of your API Passphrase, Merchant UUID and notifyURL. See Web URL Hash for information on how to construct the hash correctly.
Example: 511999e54b9ad51ce4c28d7f0550ac81
Valid Length: 32 characters

The verification hash is a combination of the MD5 of your API Passphrase, and specific parameters sent in the transaction. See Transaction Type Hash for information on how to construct the hash correctly.
Example: e9ddc296b76b3398934bfc06239073df
Valid length: 32 characters

This field is case sensitive.
Example: checkEnrollment

The accessToken obtained in Step 1.
Example: 2783a265a0

One of the following: AUD, CAD, EUR, GBP, JPY, NZD, SGD, USD. This is provider dependant. Please check with MW before attempting to process transactions in any currency other than AUD. This field is case insensitive.
Example: AUD

The amount must be formatted to have two decimal places. Any amounts without two decimal places or amounts less than one cent will be rejected.
Example: 10.00

A product (or sale) id or description. We recommend using an order/product id. This field’s primary purpose is to help the transaction be identifiable for reporting and accounting purposes.
Example: ABC4321
Valid length: Up to 255 characters. Some Acquirers limit this field to 40 characters.

Do not send separators with the card number (e.g. 1234-5678… or 1234 5678).
Example: 5123456789012346 or 4557012345678902
Valid length: Between 13 and 16 digits

This must be MMYY format. The month must be zero padded if it is less than 10.
Example: 0513
Valid length: 4 digits

This must contain at the very least a space and no less than two characters. Only alphanumeric characters, hyphens, spaces and full stops are allowed.
Example: Mr. Example Person or MR E PERSON or Example Person
Valid length: Between 3 and 255 characters

Asynchronous POST notifications will be sent to this URL.
Example: https://www.example.com/notify.php

This field is case sensitive.
Example: checkTDSAuth
Required: Yes

The accessToken obtained in Step 1.
Example: 2783a265a0
Required: Yes

The amount must be formatted to have two decimal places. Any amounts without two decimal places or amounts less than one cent will be rejected.
Example: 10.00
Required: Yes

One of the following: AUD, CAD, EUR, GBP, JPY, NZD, SGD, USD. This is provider dependant. Please check with MW before attempting to process transactions in any currency other than AUD. This field is case insensitive.
Example: AUD
Required: Yes

A product (or sale) id or description. We recommend using an order/product id. This field’s primary purpose is to help the transaction be identifiable for reporting and accounting purposes.
Example: ABC4321
Valid length: Up to 255 characters. Some Acquirers limit this field to 40 characters.
Required: Yes

Do not send separators with the card number (e.g. 1234-5678… or 1234 5678).
Example: 5123456789012346 or 4557012345678902
Valid length: Between 13 and 16 digits
Required: Yes

This must be MMYY format. The month must be zero padded if it is less than 10.
Example: 0513
Valid length: 4 digits
Required: Yes

This is also known as the CVN or CVV/2. This is required by some Acquirers if the transaction is initiated by the customer. Please contact Merchant Warrior for more information.
Example: 123
Valid length: Between 3 and 4 characters
Required: Yes

This must contain at the very least a space and no less than two characters. Only alphanumeric characters, hyphens, spaces and full stops are allowed.
Example: Mr. Example Person or MR E PERSON or Example Person
Valid length: Between 3 and 255 characters
Required: Yes

The mobile phone number provided by the Cardholder.
Required: No

Exact content of the HTTP accept headers as sent to the 3DS Requestor from the Cardholder’s browser.
Required: Yes

Boolean that represents the ability of the cardholder browser execute JavaScript.
Required: Yes

Boolean that represents the ability of the cardholder browser execute JavaScript.
Required: Conditional, on if browserJavascriptEnabled is true

Required if browserJavascriptEnabled is true

Value representing the bit depth of the colour palette for displaying images, in bits per pixel. Obtained from Cardholder browser using the screen.colorDepth property. In case the actual value does not exist in the allowed values, use the closest lower value.
Required: Conditional, on if browserJavascriptEnabled is true

Value representing the browser language as defined in IETF BCP47. Returned from navigator.language property.
Required: Yes

Total height of the Cardholder’s screen in pixels. Value is returned from the screen.height property.
Required: Conditional, on if browserJavascriptEnabled is true

Total width of the cardholder’s screen in pixels. Value is returned from the screen.width property.
Required: Conditional, on if browserJavascriptEnabled is true

Time-zone offset in minutes between UTC and the Cardholder browser local time. Note that the offset is positive if the local time zone is behind UTC and negative if it is ahead.
Required: Conditional, on if browserJavascriptEnabled is true

Exact content of the HTTP user-agent header. Note: If the total length of the User-Agent sent by the browser exceeds 2048 characters, truncate the excess portion.
Required: Conditional, on if browserJavascriptEnabled is true

Date and time of the purchase expressed in UTC.
Required: Yes

First line of the street address or equivalent local portion of the Cardholder billing address associated with the card used for this purchase.
Required: Yes

The city of the Cardholder billing address associated with the card used for this purchase.
Required: Yes

The ISO 3166-2 state or province of the Cardholder billing address associated with the card used for this purchase.
Required: Yes

Two letter ISO 3166-1 alpha-2 country code.
Required: Yes

ZIP or other postal code of the Cardholder billing address associated with the card used for this purchase.
Required: Yes

Indicates whether the 3DS Method (fingerprinting) successfully completed. This is either provided in Step 2 or determined in Step 3.
Required: Yes

Indicates the type of Authentication request. This data element provides additional information to the ACS to determine the best approach for handing an authentication request.
Required: Yes

• 01 Payment transaction
• 02 Recurring transaction
• 03 Instalment transaction
• 04 Add card
• 05 Maintain card
• 06 Cardholder verification as part of EMV token ID&V

This is an optional field that indicates whether or not you would like to perform or have a preference to request a challenge flow.
Required: No

• 01 No preference
• 02 No challenge requested
• 03 Challenge requested: 3DS Requestor Preference
• 04 Challenge requested: Mandate

Your website URL that a customer can use to identify your business.
Required: Yes

Universally unique transaction identifier assigned by the 3DS Server to identify a single transaction.
Required: Yes

Asynchronous POST notifications will be sent to this URL.
Example: https://www.example.com/notify.php

This field is case sensitive.
Example: checkPARes

The accessToken obtained in Step 1.
Example: 2783a265a0

This is the cres obtained in Step 5.
Example: eJzNWVmvm9iy/it

This field is case sensitive.
Example: processCard

The accessToken obtained in Step 1.
Example: 2783a265a0

One of the following: AUD, CAD, EUR, GBP, JPY, NZD, SGD, USD. This is provider dependant. Please check with MW before attempting to process transactions in any currency other than AUD. This field is case insensitive.
Example: AUD

The amount must be formatted to have two decimal places. Any amounts without two decimal places or amounts less than one cent will be rejected.
Example: 10.00

A product (or sale) id or description. We recommend using an order/product id. This field’s primary purpose is to help the transaction be identifiable for reporting and accounting purposes.
Example: ABC4321
Valid length: Up to 255 characters. Some Acquirers limit this field to 40 characters.

This is a merchant’s unique reference ID for a transaction sent to Merchant Warrior. The main purpose of this ID is to verify the transaction via the queryCard method in the event a valid response is not received.
Example: A257240023321
Valid length: Up to 40 characters

This field can only contain alphanumeric characters, as well as the full stop, comma, apostrophe, ampersand, space and hyphen characters.
Example: Mr. Example Person
Valid length: Between 2 and 255 characters

Two letter ISO 3166-1 alpha-2 country code.
Example: AU
Valid length: 2 characters

Freeform field, keep consistent for your records and reporting.
Example: Queensland
Valid length: Up to 75 characters

This can also accommodate ZIP/Post codes for international transactions.
Example: 4000
Valid length: Between 4 and 10 characters

Freeform field, keep consistent for your records and reporting.
Example: Brisbane
Valid length: Up to 75 characters

Freeform field.
Example: 123 Test Street
Valid length: Up to 255 characters

Freeform field. Returned as <custom1> in the XML response.
Valid length: Up to 500 characters

Freeform field. Returned as <custom2> in the XML response.
Valid length: Up to 500 characters

Freeform field. Returned as <custom3> in the XML response.
Valid length: Up to 500 characters

Obtained from Step 4

Obtained from Step 4

Obtained from Step 4 if frictionless was used, or Step 6 if challenge flow was used

This field is case sensitive.
Example: processCard

The accessToken obtained in Step 1.
Example: 2783a265a0

One of the following: AUD, CAD, EUR, GBP, JPY, NZD, SGD, USD. This is provider dependant. Please check with MW before attempting to process transactions in any currency other than AUD. This field is case insensitive.
Example: AUD

The amount must be formatted to have two decimal places. Any amounts without two decimal places or amounts less than one cent will be rejected.
Example: 10.00

A product (or sale) id or description. We recommend using an order/product id. This field’s primary purpose is to help the transaction be identifiable for reporting and accounting purposes.
Example: ABC4321
Valid length: Up to 255 characters. Some Acquirers limit this field to 40 characters.

This is a merchant’s unique reference ID for a transaction sent to Merchant Warrior. The main purpose of this ID is to verify the transaction via the queryCard method in the event a valid response is not received.
Example: A257240023321
Valid length: Up to 40 characters

This field can only contain alphanumeric characters, as well as the full stop, comma, apostrophe, ampersand, space and hyphen characters.
Example: Mr. Example Person
Valid length: Between 2 and 255 characters

Two letter ISO 3166-1 alpha-2 country code.
Example: AU
Valid length: 2 characters

Freeform field, keep consistent for your records and reporting.
Example: Queensland
Valid length: Up to 75 characters

This can also accommodate ZIP/Post codes for international transactions.
Example: 4000
Valid length: Between 4 and 10 characters

Freeform field, keep consistent for your records and reporting.
Example: Brisbane
Valid length: Up to 75 characters

Freeform field.
Example: 123 Test Street
Valid length: Up to 255 characters

Freeform field. Returned as <custom1> in the XML response.
Valid length: Up to 500 characters

Freeform field. Returned as <custom2> in the XML response.
Valid length: Up to 500 characters

Freeform field. Returned as <custom3> in the XML response.
Valid length: Up to 500 characters

The electronic commerce indicator returned after the 3D Secure authentication attempt.
Example: 05

The 3D Secure transaction identifier.
Example: 2d1752a3-7564-4e1b-88f8-197a3f670e9c

The cardholder authentication value returned after the 3D Secure authentication attempt.
Example: e1E3SN0xF1lDp9js723iASu3wrA=

The status of the 3D Secure authentication attempt.
Example: Y

The version that was used during the 3D Secure authentication attempt.
Example: 2.2.0