Before you start #
On the Plugin settings page, make sure you’ve entered your Merchant UUID and API Key – these can be found on the Settings page in Barracks. You’ll also need to enter your Endpoint – see the Setup page for information.
Collect Data #
You will need to collect:
- Transaction ID or Transaction Reference ID from the original transaction
- Hash – we’ll cover how to generate this below.
Create a Workflow #
Create a Workflow, and add the “MW – Token Payments: Process Card” action from the “Plugins” tab of the Actions list.
Each parameter in the action settings matches a parameter in the Merchant Warrior documentation.
Transaction Identifier #
You must provide one of these two options:
transactionID #
The transactionID returned for the initial transaction.
Example: 1-a1c340c8-7c30-11de-8888-000c29753ad4
transactionReferenceID #
The transactionReferenceID sent for the initial transaction. This is a merchant’s reference ID for a transaction request sent to Merchant Warrior.
Example: A257240023321
hash #
The verification hash is a combination of the MD5 of your API Passphrase, and specific parameters sent in the transaction. See Query Type Hash for information on how to construct the hash correctly.
Example: e9ddc296b76b3398934bfc06239073df
Valid length: 32 characters
Parse Response #
The response will contain:
responseCode #
| Code | Meaning |
|---|---|
| < 0 | MW validation error |
| 0 | Transaction/Operation was successful |
| > 0 | Transaction/Operation was declined or delayed by the provider or service |
responseMessage #
If the responseCode is not 0, this will provide basic insight into the reason for failure.
transactionID #
Long-form string with the ID of the overall transaction.
authCode #
6-digit authorisation code
receiptNo #
Receipt number for the payment
authMessage #
Response to card verification, eg. “Approved”
authResponseCode #
Authorisation response code as per Merchant Warrior’s documentation. Anything other than 0 is a fail.
authSettledDate #
The date this payment will settle into your bank account from Merchant Warrior.
transactionAmount #
The amount for which the transaction was charged.
transactionCurrency #
The currency in which the transaction was charged.
custom1/2/3 #
As entered in the original transaction.
transactionType #
The type of transaction this query has polled – eg. purchase, refund
customHash #
Custom Hash as generated by Merchant Warrior.
transactionProduct #
As entered in the original transaction.
transactionReferenceID #
As entered in the original transaction.
customerName #
As entered in the original transaction.
customerCountry #
As entered in the original transaction.
customerCity #
As entered in the original transaction.
customerAddress #
As entered in the original transaction.
customerPostcode #
As entered in the original transaction.
customerPhone #
As entered in the original transaction.
customerEmail #
As entered in the original transaction.
cardName #
As entered in the original transaction.
cardNumberFirst #
The first 4 digits of the card number in the original transaction.
cardNumberLast #
The last 4 digits of the card number in the original transaction.
cardType #
The type of card used, rendered in lowercase. eg. visa
transactionProcessed #
DateTime format of when the original transaction was processed.
Next Actions #
We recommend adding a step with an “only when” of “…’s authResponseCode is not 0” that deals with the error. Otherwise, passing the variables you need to a Thing and/or to an Element, would be the logical next step.
