Merchant Warrior

Merchant Warrior: Payment Acceptance Overview For Merchants

Merchant Warrior is an Australian payments platform that provides merchant payment acceptance across online, phone, and in-person contexts through a mix of APIs, hosted checkout components, and operational tooling. The product set spans card payments, bank-account based payment rails used in Australia, and auxiliary capabilities such as tokenization, fraud tooling, notifications, and payouts to Australian bank accounts.

Merchant Warrior At A Glance

Merchant Warrior is operated by SR Global Solutions Pty Ltd trading as Merchant Warrior and is described as a privately owned fintech company founded in 2009 and based in Brisbane, Australia. Its platform positioning centers on providing payment acceptance and billing tools for merchants, including card and bank-account based transaction processing, multi-currency support, reporting capabilities, and 24-hour support coverage.

Merchant Warrior combines:

• API-first payment processing for cards and other transaction types
• Hosted and embedded checkout options for browser-based payments
• A virtual terminal for MOTO and manual payment entry use cases
• Support for in-person POS processing via dedicated endpoints
• Asynchronous status updates and reporting files via notifications
• A payouts API for sending funds to Australian bank accounts

Payment Acceptance Channels

Merchant Warrior supports multiple payment acceptance channels, with different integration paths depending on the channel.

Online Payments (Web)

Merchants can accept web payments via:

• Direct API endpoints for server-side processing flows (including purchase and authorization-style flows).
• Hosted Payments and hosted checkout experiences where card data entry can occur in hosted components rather than on the merchant’s servers.
• Embedded iFrame checkout via MW Payframe, a hostable payment iframe that returns tokens that merchants submit server-side for processing.
• Web SDK for frontend integration patterns, including Payframe, 3DS handling, token generation, and digital wallets.
• Payment links via PAY.Link, which generates a unique payment link that can be shared through channels such as email or SMS.

MOTO And Virtual Terminal

Merchant Warrior provides a Virtual Terminal designed for manual payments taken by email or phone, and it is described as applicable for recurring payments and store-based payments with hand-keyed card entry scenarios.

POS

Merchant Warrior includes a POS product in its documentation with dedicated endpoints for processing and managing POS transactions (including refund and void operations). This supports in-person payment use cases where a POS integration is required.

Payment Methods Supported

Merchant Warrior’s platform supports card payments plus several Australia-centric bank payment rails and related workflows.

Card Payments

Card processing is core to the platform and is referenced across its API and checkout products. Merchant Warrior’s Payframe documentation indicates support for multiple card schemes including Visa, Mastercard, American Express, Diners, Discover, and JCB (with some schemes requiring explicit configuration).

Common card processing capabilities include:

• Purchase (sale) transactions
• Authorization and capture style flows (where supported by the relevant endpoints)
• Refund and void operations
• Card verification
• Batch processing options

Digital Wallets

Merchant Warrior’s Web SDK supports Apple Pay and Google Pay as digital wallet options. The Web SDK also includes configuration controls such as allowed authentication methods and allowed card networks for wallet payments, and it can optionally invoke 3DS logic when liability shift has not occurred on a Google Pay transaction.

Bank Account Payments And Real-Time Payments

Merchant Warrior references multiple bank-payment capabilities used in Australia:

• PayID payments are described as instant and available 24/7/365, with funds settling instantly.
• PayTo is supported with an agreement-based workflow where customers approve mandates via their banking app, followed by near real-time payment processing and notifications.
• EFT bank transfers are supported with notification outputs (including daily notification files for cleared transactions).
• Direct Debit is supported and described as taking effect after bank clearance, with status progression from pending to approved or declined over the following days.
• BPAY is supported, with settlement timing described as same-day and with notification flows for cleared BPAY transactions.

Payouts (Outbound)

Merchant Warrior also offers a Payouts API for sending funds to nominated Australian bank accounts. The documented flow funds payouts via PayTo debits and then initiates payouts via NPP, with fallback behavior if issues occur during NPP transfer.

Checkout And Billing Flows

Merchant Warrior supports several checkout and billing patterns that matter for conversion, token reuse, and recurring revenue models.

Payment Links

PAY.Link is designed to create a unique payment link that a merchant can share with customers. This is useful for remote collection scenarios such as invoices, SMS-based collection, and email billing.

Embedded Checkout (iFrame)

MW Payframe is a hostable iframe that returns a payframeToken and payframeKey for downstream server-side processing, or can add a card to the Merchant Warrior vault. This approach can help merchants avoid directly handling raw card data entry fields in their own frontend.

Tokenization And Saved Cards

Merchant Warrior’s Token Payments service provides a vault concept (MW Vault) where cards can be stored and referenced via token identifiers for subsequent transactions. The documentation frames tokenization as a way to perform subsequent transactions without sending cardholder data to the platform more than once, and it explicitly notes reduced PCI scope when merchants are not storing PAN data.

Recurring Billing

Merchant Warrior describes recurring payments as a supported use case in the context of its Virtual Terminal and its tokenization and authorization patterns. For recurring models, a typical implementation combines tokenization (for saved cards) with scheduled server-side charges, plus asynchronous status notifications.

Fraud, Risk, And Dispute Handling

Merchant Warrior presents multiple layers of risk tooling:

• 3DS 2 support, including frictionless and challenge flows, and fallback behaviors where applicable.
• Fraud detection tooling, described as part of a fraud detection suite, with optional enablement of Forter as an additional fraud prevention and risk management capability.
• Blacklisting utilities in the API surface, including the ability to add and remove blacklisted cards.
• Chargeback notifications via callback mechanisms so merchants can receive structured updates when chargebacks occur, supporting operational response and reconciliation.

Developer Experience And Integration Options

Merchant Warrior’s documentation is structured around multiple integration surfaces:

• Direct API endpoints for backend processing and transaction management.
• Web SDK for frontend implementations, including Payframe, token generation, 3DS support, and wallets.
• MW Payframe for embedded iFrame checkout and token return patterns.
• Notifications for callback-based updates, including support for JSON notifications as a replacement for legacy CSV formats.
• Sandbox tooling and simulators for testing, plus code samples across multiple languages (including cURL, Ruby, Python, PHP, C#, VB.NET, and Java).

This combination enables merchants to choose between a more hands-on API implementation or a more component-based approach where sensitive entry fields are handled in hosted or embedded components.

Settlement And Reconciliation

Settlement behavior depends on the payment rail:

• PayID is described as instant settlement.
• PayTo includes synchronous status responses plus asynchronous resolution notifications when funds transfer completes.
• BPAY is described as settling same-day.
• Direct Debit depends on bank clearance, with transaction status updates over subsequent days.

For reconciliation, Merchant Warrior’s notification framework provides scheduled callback files for cleared transactions (for example, direct debit and BPAY notifications) and includes transaction-level fields such as settlement dates, fees, and identifiers. This can be paired with API-based querying and settlement retrieval endpoints where applicable.

Supported Markets And Currencies

Merchant Warrior is headquartered in Australia and its documentation emphasizes Australian payment rails (including PayID, PayTo, BPAY, NPP, and direct entry fallback behavior in payouts). It also supports multi-currency processing with a published list of supported currencies, including major currencies such as AUD, USD, EUR, and GBP along with a broader set of additional currencies.

Who Merchant Warrior Is Typically Used By

Based on the feature set described, Merchant Warrior is a fit for merchants that need one or more of the following:

• Card payments plus Australia-specific bank payment rails (PayID, PayTo, BPAY, and direct debit)
• Multiple checkout implementation options, including hosted, embedded iFrame, and full API
• Saved cards and token-based recurring billing
• MOTO workflows using a virtual terminal
• Operational notifications for reconciliation and dispute awareness
• Outbound payouts to Australian bank accounts via API

Conclusion

Merchant Warrior is an Australia-based payment acceptance platform that combines card processing with bank payment rails used in Australia, plus multiple integration approaches spanning direct APIs, embedded payment components, payment links, and POS endpoints. Its documentation emphasizes tokenization, 3DS 2 support, callback notifications for operational visibility, and a payouts capability for sending funds to Australian bank accounts.