Setup
Registration for Merchant Warrior is available through their website.Connector configuration
After signing up with Merchant Warrior, you can configure the connector in Gr4vy using one of the following methods:- Flow - Configure payment routing rules through your Gr4vy dashboard
- API integration - Specify the
payment_service_idwhen creating transactions to explicitly route payments to this connector
Credentials
Configure the following credentials in the Gr4vy dashboard, which are obtained from your Merchant Warrior dashboard:- Merchant UUID - Your unique merchant identifier
- API Key - Your API authentication key
- API Passphrase - Your API authentication passphrase
Features
Merchant Warrior supports the following features:- Delayed capture - Authorize a payment and capture it at a later time
- Partial capture - Capture a portion of the authorized amount
- Partial refunds - Refund a portion of the captured amount
- Refunds - Refund a captured payment
- Void - Cancel an authorized transaction before capture
- Zero auth - Verify a card without charging it
- Digital wallets - Support for Apple Pay, Google Pay, and other wallet integrations
- Network tokens - Network tokenization is enabled by default
- 3-D Secure - Pass-through 3DS authentication
Supported countries
Merchant Warrior supports transactions from buyers in the following countries:| Country code | Country code | Country code | Country code |
|---|---|---|---|
AU | GB | HK | IN |
NZ | SG | US |
Supported currencies
Merchant Warrior supports processing payments in the following currencies:| Currency code | Currency code | Currency code | Currency code | Currency code |
|---|---|---|---|---|
AUD | CAD | CHF | EUR | GBP |
HKD | JPY | NZD | SGD | USD |
Limitations
The following features are not supported by this connector:- Over capture - Capturing more than the authorized amount is not supported
- Partial authorization - Partial authorization is not supported
- Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
- Transaction sync - Transaction status synchronization is not supported
- Dynamic statement descriptors - Statement descriptors passed through the API are not sent to Merchant Warrior. Ensure you have a suitable descriptor configured with Merchant Warrior directly.
Integration
To accept card payments with Merchant Warrior, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:- Embed - A pre-built, customizable payment form that handles the complete payment flow
- Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
- Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
payment_service_id parameter.
Required fields
Merchant Warrior requires the following buyer information for all transactions:- First name
- Last name
- Email address
- Billing address (including line 1, city, state, postal code, and country)
NA for address fields and
NA@example.com for email). However, it’s highly recommended to provide actual
values when available.