1. PayTo
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. PayTo

Introduction

PayTo is an Australian modern digital payment solution offering a fast, easy and secure way to pay. It gives consumers more visibility and control over their payments, and enables merchants and businesses to initiate real-time payments from their customers’ bank accounts.
The PayTo payment system in Australia is currently adapting and improving based on insights uncovered. As the product progresses towards a stable state, modifications may be made to this documentation.
The illustrations and accompanying explanations provided here offer an overview of the PayTo procedure, which encompasses everything from establishing an agreement to the processing of a payment.

Establishing an Agreement#

[[MW-PAYTO-AGREEMENT-FLOW]]
Authorization Request
You initiate an authorization request (Create Agreement) to debit your customer's bank account.
This request includes details such as the payment amount, frequency, and other terms.
The authorization request is sent to your customer's bank.
Payer Review and Approval
Your customer receives the authorization request via their internet banking app.
They review the terms and decide whether to approve or decline.
If approved, your customer provides consent for future debits.
Agreement Confirmation
A notification (Agreement Notification) is dispatched to you in near real-time when the customer actions the agreement.
Upon approval, an agreement is established between the customer and your business.
The agreement specifies the terms for future payments (or a one-off payment).

Requesting a Payment#

[[MW-PAYTO-PAYMENT-FLOW]]
Payment Creation
With an active agreement, you can request a payment from your customer's bank account.
Payments are generated within the agreed-upon terms (e.g., specific dates, amounts).
You submit a request for payment (Create Payment) to the customer's bank.
Near real-time response
When the customer’s bank receives your payment request, it commences the process of transferring funds to your business.
You receive a synchronous response indicating the status of your payment request (Create Payment).
An asynchronous response (Payment Resolution Notification) is delivered to you when the bank has successfully transferred the funds to your business.
Modified at 2026-08-04 07:37:52
Previous
Refund
Next
Simulator
Built with