🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!
Guides & Tutorials October 22, 2026

How to Take Merchant Warrior Card Payments in Gravity Forms

GravityExtra
How to Take Merchant Warrior Card Payments in Gravity Forms

Taking a card payment on a WordPress form sounds simple until you think about what you are really taking on. Card numbers are some of the most sensitive data a website can touch. If they pass through your server, you inherit security work you did not plan for. If the payment status can be changed by a browser, someone will eventually try it. This guide shows how to take card payments with Merchant Warrior from a Gravity Forms form in a way that keeps the card away from your site and does not trust anything a browser says.

Why Merchant Warrior and Gravity Forms

Merchant Warrior is an Australian payment gateway used by tour operators, clubs, schools, trades and online shops that bank in Australian or New Zealand dollars. Gravity Forms is the form builder many of those businesses already use for bookings, quotes, enrolments and orders. Putting the two together means one form can collect the details, work out the total with product, quantity, discount and postage fields, and send the customer to pay, all without a separate checkout plugin.

The Gravity Forms Merchant Warrior Payment Gateway Premium Add-on does that with the hosted payment page of Merchant Warrior. The customer is sent to a page on the gateway, types the card there and is sent back. Your site only ever handles the amount, a reference and the result.

What You Need

  • Gravity Forms 2.9 or newer and WordPress 6.5 or newer.
  • A Merchant Warrior account. In Barracks, under Settings and Direct API, you find the Merchant UUID, the API Key and the API Passphrase. The sandbox has its own set.
  • The add-on and its license key.
  • A site on HTTPS.

There is no partner contract and no approval step. The add-on is self-serve: you type your own credentials, and it talks to Merchant Warrior and to your own site.

Step by Step: Your First Test Payment

  1. Install the add-on, activate the license and open Forms, Settings, Merchant Warrior.
  2. Leave the environment on Sandbox and paste the sandbox merchant UUID, API key and passphrase. Save. The add-on asks Merchant Warrior to accept all three, and it refuses to keep a set that is wrong.
  3. Build a form: name, email, one or two product fields and a Total field. Set the currency of Gravity Forms to AUD.
  4. In the form settings, add a Merchant Warrior feed. Map the name and email of the customer and choose a payment reference with merge tags.
  5. Open the form on your site, fill it in and press the button. You land on the Merchant Warrior page. Pay with a sandbox test card.
  6. Back on your site you see the confirmation. Open the entry: the status is Paid, and the Merchant Warrior box shows the transaction, the authorisation code and a sandbox badge.
The Merchant Warrior settings in Gravity Forms: sandbox or live, merchant UUID, API key and passphrase fields, currency check, connection status, a Test connection button and the notification address
One settings page: both environments, a connection check and the notification address.

What Happens Behind the Scenes

When the form is submitted, the add-on works out the amount on the server from the entry, and never from a hidden field. It then asks Merchant Warrior for a one-time access token. That request is signed with a hash made from your passphrase, the merchant UUID, the amount and the currency, so a stranger who learns your UUID and key still cannot ask for tokens. The token, the amount and your return and notification addresses are put into a small form, and the customer’s browser posts it to the hosted payment page. The passphrase is not in that form. Neither is the API key.

On the payment page, the customer types the card. Merchant Warrior takes the payment and sends the customer back to your site with a status, a transaction id and a hash. The hash is made with your passphrase and with a random salt that your site made for this one payment, so nobody can forge a return link for another entry. Merchant Warrior may also post a notification to your site.

Why the Add-on Asks Again

Return links and notifications arrive from the outside, so the add-on treats them as hints. After checking the hash, it asks Merchant Warrior for the transaction with a hashed query and compares the transaction id, your reference, the amount and the currency. Only if all of them match is the entry marked as Paid, and it happens once, however many times the same news arrives. The customer coming back, the notification and the five-minute status check can all arrive in any order, and the entry still ends up in the right state.

That also covers the awkward cases. If the customer closes the tab after paying, the notification or the status check finds the approved payment. If the notification never comes, the status check does the work. If somebody edits the status in the address bar, nothing changes. If the gateway reports a different amount than the entry expects, the entry is not paid, and a note tells you to look in Barracks.

A Gravity Forms entry paid through Merchant Warrior, with payment details, a Merchant Warrior box showing the transaction, authorisation code, card and a refund field, and entry notes
The entry shows the transaction, the authorisation code, the masked card and a refund box.

Declined Cards

A declined card is part of life. By default the customer stays on the Merchant Warrior page after a decline and can try another card, and your site only hears about the payment that succeeds. If you prefer to bring the customer back after a decline, switch that option off in the feed, and the entry is marked as failed with a note, and your failure notification is sent. Payments that are never approved are closed as failed a day later, so no entry waits forever.

The Merchant Warrior feed settings in Gravity Forms: payment reference, keep the customer on the payment page after a declined card, payment page ID and hold notifications until the payment is approved
One feed per form: the reference, declined card behaviour and the payment page ID.

Customer Details and the Reference

Merchant Warrior accepts a customer name, email, phone and address with the payment, and they make your reports in Barracks easier to read. Map them in the feed. The add-on only sends valid values: it cleans the name, checks the email, keeps the phone to digits, plus, minus and spaces, requires a post code of four to ten characters and turns a country name into the two letter code. The payment reference, with merge tags, is shown on the payment page and stored with the transaction.

Refunds From the Entry Screen

Open an entry and use the Merchant Warrior box. Type an amount and press Refund. The refund request is signed with the hash of the original amount, a unique reference is sent with it, and the entry changes to Partially Refunded or Refunded with a note and the Gravity Forms refund notification. Each refund carries a one-time request id, so a double click cannot refund twice, and if Merchant Warrior refuses, you see its message and nothing changes. A refund made in Barracks is picked up when you press Refresh status.

Keeping Your Credentials Safe

  • The API key and passphrase are stored encrypted and are never shown again.
  • They are used on the server only and are never sent to a browser, a form or a log.
  • Saving checks all three values with Merchant Warrior, and a wrong set is refused.
  • A Test connection button repeats the check whenever you like.
  • Sandbox and live have separate sets, and an entry remembers which environment it was paid in.

Practical Setups

  • A tour or class booking form that holds the booking notification until the card is approved.
  • A club membership or event ticket form where only paying members reach the next step, with conditional logic on the feed.
  • A donation form with a payment reference that shows the campaign in Barracks.
  • A quote form where an accepted quote links to a second form that takes the deposit.
  • A school or camp enrolment form that adds the parent to your email list only after the payment is completed.

In every case the entry tells the story: a note when the customer was sent to the payment page, a note when the payment was approved with the transaction and the authorisation code, and a note for every refund. Your staff can answer a question about a payment without opening Barracks.

Going Live

When the sandbox payments look right, enter the live merchant UUID, API key and passphrase, select Live and save. The add-on checks the live values with the live gateway before it keeps them. Make one real payment of a small amount, check the entry and refund it from the entry screen, and you are done. Remember that Merchant Warrior asks you to check with them before you charge in a currency other than the Australian dollar.

Questions People Ask

Does the card number touch my website?

No. The card is typed on the Merchant Warrior page. Your site receives a status, a transaction id and the last digits of the card.

Can I take recurring payments or bank direct debit?

Not in version 1.0.0. It takes one-time card payments. Those other methods need bank or card details to pass through your server or a stored card token, and they are only planned if they can be done without that.

Will it work with conditional logic and other add-ons?

Yes. Conditional logic on the feed decides which submissions go to the payment page, and feeds of other add-ons can wait until the payment is completed.

To see every option, read the Merchant Warrior setup guide, or visit the Gravity Forms Merchant Warrior Payment Gateway Premium Add-on page.

See the Merchant Warrior add-on

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr