1. Batch
Merchant Warrior API 2.0
  • API
    • Getting Started
    • Guides
      • Xero Connection
      • Xero Custom URL
      • wooCommerce PayID
      • Middleware
      • Hostaway
    • Direct API
      • getAccessToken
      • processCard
      • processAuth
      • processCapture
      • processBatch
      • retrieveBatch (CSV)
      • retrieveBatch (JSON Response)
      • retrieveBatch (JSON Notify)
      • refundCard
      • queryCard
      • processDDebit
      • processDDebitAuth
      • processVoid
      • verifyCard
      • queryDD
      • queryBIN
      • getSettlement
      • checkEnrollment
      • checkPARes
      • addBlacklistedCard
      • removeBlacklistedCard
      • queryBlacklistedCard
      • simulateNotify
      • getSurcharge
    • 3DS 2.0
      • Introduction
      • 3DS 2 Authentication Flows
      • Step 3 - 3DS Method Data
      • Step 5 - Challenge
      • Step 1 - getAccessToken
      • Step 2 - checkEnrollment
      • Step 4 - checkTDSAuth
      • Step 6 - checkPARes
      • Step 7 - processCard
      • Authorization Only processCard
    • PayLink
      • Introduction
      • Generate PayLink
    • PayID
      • Introduction
      • Create
      • Transaction
      • Get
      • Update
      • Status
      • List
      • Refund
    • PayTo
      • Introduction
      • Simulator
      • Certification
      • Actions and Statuses
      • Agreements
        • Agreements
        • Notifications
        • Create Agreement
        • Get Agreement
        • Amend Agreement
        • Amend Agreement Status
        • Recall Agreement Action
      • Payments
        • Payments
        • Notifications
        • Create Payment
        • Get Payment
        • Get Payment Status
        • Search Payments
    • Confirmation of Payee
      • Introduction
      • Sandbox Simulations
      • Validate
    • POS
      • Introduction
      • processPOS
      • refundPOS
      • voidPOS
      • deregisterPOS
    • Web SDK
      • Introduction
      • Usage
      • getAccessToken
      • Options
      • Initiate
      • Payframe Functionality
      • Middleware
      • addCard
    • Payframe
      • Introduction
      • Usage
      • Constructor
      • tdsCheck
      • Additional Functions
      • Styling
      • processCard
      • processAuth
    • Digital Wallets
      • Apple Pay Prerequisites
      • Google Pay Prerequisites
      • Web SDK
      • Manual Integration
      • processCard
      • addCard
      • getMerchantSession
      • decryptApplePayToken
    • Token Payments
      • Introduction
      • Key Management
      • addCard
      • removeCard
      • cardInfo
      • changeExpiry
      • processCard
      • processAuth
    • Batch
      • Introduction
      • Card Batches
      • Token Batches
      • Direct Debit Batches
    • Forter
      • Introduction
      • Testing
    • Payouts
      • Introduction
      • Sandbox Simulations
      • Notifications
      • Create Payouts
      • Get Payout Status
      • Resend Notifications
      • Get Payout Transaction Status
      • Get Payout Transaction Notify
    • Partner API
      • Introduction
      • addMerchant
      • updateMerchant
      • checkMerchant
    • Notifications
      • Notifications
  • Hosted Payment Page
    • processCard
  1. Batch

Direct Debit Batches

Sample batch files for direct debits can be found here.

Request CSV Parameters#

ParameterDescription
transactionProductA product (or sale) ID or description. We recommend using an order or product ID. This field's primary purpose is to help identify the transaction for reporting and accounting purposes.

Example: ABC4321
Valid length: Up to 255 characters.
customerNameCan contain only alphanumeric characters and the following characters: full stop (.), comma (,), apostrophe ('), ampersand (&), space, and hyphen (-).

Example: Mr. Example Person
Valid length: Between 2 and 255 characters.
customerPhoneThe customer's phone number. Any character other than +, -, spaces, and digits (0-9) will be stripped.

Example: 0401234567 or 61731234567
Valid length: Up to 25 characters.
customerEmailThe customer's email address.

Example: person@example.com
Valid length: Up to 255 characters.
customerCountryTwo-letter ISO 3166-1 alpha-2 country code.

Example: AU
Valid length: 2 characters.
customerStateFree-form field. Keep values consistent for your records and reporting.

Example: Queensland
Valid length: Up to 75 characters.
customerCityFree-form field. Keep values consistent for your records and reporting.

Example: Brisbane
Valid length: Up to 75 characters.
customerAddressFree-form field.

Example: 123 Test Street
Valid length: Up to 255 characters.
customerPostCodeSupports ZIP and postal codes for international transactions.

Example: 4000
Valid length: Between 4 and 10 characters.
transactionTypeThe type of transaction being performed. Must be ddebit for direct debit batches.
transactionAmountThe transaction amount. It must contain exactly two decimal places. Amounts without two decimal places, or amounts less than one cent, will be rejected.

Example: 10.00
transactionCurrencyThe transaction currency. Supported values are provider-dependent. Check with Merchant Warrior before processing transactions in any currency other than AUD. This field is case-insensitive.

Possible values: AUD, NZD
Example: AUD
custom1Free-form field. Returned as <custom1> in the response.

Valid length: Up to 500 characters.
custom2Free-form field. Returned as <custom2> in the response.

Valid length: Up to 500 characters.
custom3Free-form field. Returned as <custom3> in the response.

Valid length: Up to 500 characters.
paymentAccountBSBMust contain exactly 6 digits.

Example: 011123
Valid length: 6 digits.
paymentAccountNumberMust be a valid account number.

Example: 123456789
Valid length: Between 4 and 10 digits.
paymentAccountNameMust contain at least one space and no fewer than two characters. Only alphanumeric characters, hyphens, spaces, and full stops are allowed.

Example: Mr. Example Person, MR E PERSON, or Example Person
Valid length: Between 3 and 32 characters.
transactionReferenceIDThe merchant's unique reference ID for a transaction sent to Merchant Warrior. Its primary purpose is to verify the transaction through the queryCard method when a valid response is not received.

Example: 0e26df01-1460-4565-894b-e3a16dd53c7a
Valid length: Up to 40 characters.
Required: No.
Modified at 2026-07-17 00:49:46
Previous
Token Batches
Next
Introduction
Built with