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 the following:
- Card ID – you’ll want to retrieve this from a Thing
- Expiry Month (2 digits)
- Expiry Year (2 digits)
We recommend storing the expiry month and year in a Thing directly from the input fields when parsing the response, as they are not passed back by Merchant Warrior. This will help with managing expiring cards.
Create a Workflow #
Create a Workflow, and add the “MW – Token Payments: Change Expiry” action from the “Plugins” tab of the Actions list.
cardID #
A unique alphanumeric string returned by the Add Card action, used to identify a specific card.
Example: NUFM56937091
cardExpiryMonth #
This must be MM format. The month must be zero padded if it is less than 10.
Example: 05
Valid length: 2 digits
cardExpiryYear #
This must be YY format. Example: 13 Valid length: 2 digits
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.
cardID #
Passed back to confirm the card that was updated.
Next Actions #
We recommend adding a step with an “only when” of “…’s responseCode is not 0” that deals with the error.
We recommend passing the expiry month and year from the frontend inputs, into a Thing, to help manage future expiry.
