The Refund API allows merchants to process card-not-present refunds for integrated EFTPOS transactions. Refunds are performed as referenced refunds, meaning they require a reference to the original transaction. This ensures refunds are always applied directly back to the customer’s original payment method — without requiring the card to be re-presented.
- Funds return to the original payment method – Refunds are always credited back to the same card or account used for the original payment, not as cash or to another card.
- Card-not-present refunds – Customers do not need to present their card again at the terminal.
- Partial refunds – Supports multiple partial refunds, provided that the total refunded amount does not exceed the original transaction amount.
- Simpler reconciliation – Every refund references the original transaction, giving you a complete audit trail across full and partial refunds.
- Fraud protection – By tying refunds to the original payment method, the API reduces risks such as receipt fraud, stolen merchandise returns, or cross-retailer return fraud.
- Effective date: Refunds are available only for transactions made on or after 28 March 2025.
- Supported transactions: Only POS integrated transactions are eligible. Online/eCommerce transactions are not currently supported.
- Currency support: Only transactions settled in AUD are supported at this time.
- Pre-authorizations not supported: Refunds cannot be processed against pre-authorized transactions.
- Unsupported payment methods: Refunds for Alipay transactions are not supported.
- Required identifier: You must pass the IntegratedTransactionID generated by the POS at the time of sale.
- Uniqueness considerations: Some POS providers do not guarantee globally unique IntegratedTransactionIDs. In these cases, it is best practice to also include the RRN (Retrieval Reference Number) with the refund request to ensure accurate matching.