This field is case sensitive.
Example: addCard

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

Example: 5123456789012346 or 4557012345678902
Valid length: Between 13 and 16 digits

This must be MM format. The month must be zero padded if it is less than 10.
Example: 05
Valid length: 2 digits

This must be YY format.
Example: 13
Valid length: 2 digits

The value of this parameter is provided to you by Merchant Warrior.
Example: 123456789abcd
Required: If accessToken is not used.

The value of this parameter is provided to you by Merchant Warrior.
Example: 1a3b5c
Required: If accessToken is not used.

A single use access token, used in place of your merchant credentials.
Example: 82cea7c4f7
Required: If merchantUUID and apiKey is not used.

This parameter is used to indicate if the card details (cardNumber, cardExpiry and optionally the paymentCardCSC) should be verified automatically before being tokenized. Its value must be 0 or 1.
Example: 1

This is also known as the CVN or CVV/2. If you are verifying the card number during your addCard request we highly recommend you submit this value in your request.
Example: 123
Valid length: Between 3 and 4 characters

This field is case sensitive.
Example: removeCard

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

A unique alphanumeric string returned by addCard, used to identify a specific card.
Example: NUFM56937091

A string used as an encryption/decryption key. This should be unique on a per-card basis. It’s used to encrypt the card when we store it. Every time we receive a process card request, the correct cardkey must also be provided – which is known only to you.
Example: a84JI2cA12ziZ3Fx
Valid length: 16 characters

This field is case sensitive.
Example: cardInfo

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

A unique alphanumeric string returned by addCard, used to identify a specific card.
Example: NUFM56937091

A string used as an encryption/decryption key. This should be unique on a per-card basis. It’s used to encrypt the card when we store it. Every time we receive a process card request, the correct cardkey must also be provided – which is known only by you.
Example: a84JI2cA12ziZ3Fx
Valid length: 16 characters

This field is case sensitive.
Example: changeExpiry

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

A unique alphanumeric string returned by addCard, used to identify a specific card.
Example: NUFM56937091

This must be MM format. The month must be zero padded if it is less than 10.
Example: 05
Valid length: 2 digits

This must be YY format.
Example: 13
Valid length: 2 digits

A string used as an encryption/decryption key. This should be unique on a per-card basis. It’s used to encrypt the card when we store it. Every time we receive a process card request, the correct cardkey must also be provided – which is known only by you.
Example: a84JI2cA12ziZ3Fx
Valid length: 16 characters

This field is case sensitive.
Example: processCard

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

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 field can only contain alphanumeric characters, as well as the full stop, comma, aposprophe, 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

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

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

A unique alphanumeric string returned by addCard, used to identify a specific card.
Example: NUFM56937091

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 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 parameter is used to indicate if a transaction will be marked as recurring. Its value must be 0 or 1.
Example: 1

This parameter is used to indicate if a transaction has been authenticated. Its value is returned by checkPARes method.

Anything other than +,-, space and 0-9 will be stripped.
Example: 0401234567 or 61731234567
Valid length: Up to 25 characters

Sending this optional parameter is highly recommended.
Example: [email protected]
Valid length: Up to 255 characters

Any valid IPv4 or IPv6 address is accepted. Sending this optional parameter is highly recommended.
Example: 123.456.789.012 or 2001:0db8:85a3:0000:0000:8a2e:0370:7334
Valid length: Up to 39 characters

The value of this field is the merchant's store name. Please note that you need to contact Merchant Warrior to enable the storeID feature before you can use this parameter.
Example: Test store name

A string used as an encryption/decryption key. This should be unique on a per-card basis. It's used to encrypt the card when we store it. Every time we receive a process card request, the correct cardkey must also be provided - which is known only by you.
Example: a84JI2cA12ziZ3Fx
Valid Length: 16 characters

This will replace cardKey for subsequent requests for the cardID if the transaction is run successfully (meaning accepted by Merchant Warrior, not necessarily approved by the bank). This cannot be the same as the last 10 cardKey's used for the cardID, and it has to follow the same guidelines as cardkey (16 character alphanumeric string, etc). See the explanation under "Request Parameter" for more information.
Example: mbnGHOq86sXTjQgd
Valid Length: 16 characters

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

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

This field is case sensitive.
Example: processAuth

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

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 field can only contain alphanumeric characters, as well as the full stop, comma, aposprophe, 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

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

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

A unique alphanumeric string returned by addCard, used to identify a specific card.
Example: NUFM56937091

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 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 parameter is used to indicate if a transaction has been authenticated. Its value is returned by checkPARes method.

Anything other than +,-, space and 0-9 will be stripped.
Example: 0401234567 or 61731234567
Valid length: Up to 25 characters

Sending this optional parameter is highly recommended.
Example: [email protected]
Valid length: Up to 255 characters

Any valid IPv4 or IPv6 address is accepted. Sending this optional parameter is highly recommended.
Example: 123.456.789.012 or 2001:0db8:85a3:0000:0000:8a2e:0370:7334
Valid length: Up to 39 characters

The value of this field is the merchant's store name. Please note that you need to contact Merchant Warrior to enable the storeID feature before you can use this parameter.
Example: Test store name

A string used as an encryption/decryption key. This should be unique on a per-card basis. It’s used to encrypt the card when we store it. Every time we receive a process card request, the correct cardkey must also be provided – which is known only by you.
Example: a84JI2cA12ziZ3Fx
Valid Length: 16 characters

This will replace cardKey for subsequent requests for the cardID if the transaction is run successfully (meaning accepted by Merchant Warrior, not necessarily approved by the bank). This cannot be the same as the last 10 cardKey’s used for the cardID, and it has to follow the same guidelines as cardkey (16 character alphanumeric string, etc). See the explanation under “Request Parameter” for more information.
Example: mbnGHOq86sXTjQgd
Valid Length: 16 characters

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

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