Quick Reference: Refunding a Merchant Payment
- Meaning: Refunding a merchant payment is a card based refund flow connected to an original merchant payment, with a travel rule approach that relies on card number traceability in the transfer message.
- Key requirement: For refunding merchant payments, the transfer message must include the card number.
- Important nuance: AUSTRAC lists refunding merchant payments as an exception for including payer information and the payee’s full name in the transfer message.
What Refunding a Merchant Payment Means
Refunding a merchant payment is a card based refund flow that is connected to an original merchant payment. For travel rule purposes, AUSTRAC treats it similarly to how a merchant payment is treated, which means the information obligations differ from those that apply to standard push payments. The transfer message does not need to include payer information or the payee full name. However, the card number must be included in the transfer message. Traceability in these transfers is achieved through the card number rather than through the standard payer and payee identity fields.
This is a deliberate design in the travel rule framework. Because the refund is linked to an original card based transaction, the card number provides a traceable path back to the originating payment. This substitutes for the fuller information requirements that would otherwise apply.
The Core Obligation You Need to Understand
The transfer message for a refunding merchant payment must include the card number. This is the minimum content AUSTRAC expects. Without it, the transfer message does not meet the travel rule requirements for this payment type.
AUSTRAC explicitly lists refunding a merchant payment as an exception for including payer information and the payee full name in the transfer message. This exception applies specifically because of the card number traceability approach. It does not create a general low obligation category for card based refunds. The exception is narrow and the card number requirement remains firm.
How This Applies Across Different Institution Types
Ordering institutions are responsible for correctly classifying the payment as a refund of a merchant payment and ensuring the card number is included in the transfer message before it is sent.
Intermediary institutions are required to pass on the card number as the transfer moves through the payment chain. Dropping or stripping the card number at any point in the process creates a compliance gap.
Beneficiary institutions are permitted to reject a transfer or apply their AML and CTF policies where required information, including the card number, is missing from the transfer message. Evidence of that decision making should be retained.
A Practical Example
A customer returns a purchase to a retailer. The retailer initiates a refund to the customer’s card. The institutions involved in processing that refund are required to pass on the card number in the transfer message and to keep records of the transfer. The refund does not need to carry payer identity fields or the customer full name, but the card number must travel with the message and be retained for record keeping purposes.
What Gets Missed in Practice
Misclassifying the payment type is one of the more consequential errors in this area. If a card based refund is incorrectly classified as a standard push payment, the institution may either over engineer the message with fields that are not required or, more seriously, apply the wrong compliance controls altogether. Classification should be deliberate and documented.
Treating all card based refunds as operationally routine creates audit trail gaps. The fact that refunds are frequent and low friction does not reduce the compliance obligation. The card number must be present, it must be passed on, and the process must be evidenced.
Losing the link between the refund message and the original transaction reference in internal systems is a common operational failure. Where the card number cannot be retrieved or matched back to the originating payment, the audit trail breaks down and the institution cannot demonstrate compliance if queried.
Best Practice Controls for Refunding Merchant Payments
First, classify the refund correctly before processing. Determine whether the transaction is a refund of a merchant payment and apply the corresponding travel rule treatment. Do not default to the standard push payment framework without considering whether an exception applies.
Second, make card number retention and retrieval a documented control. AUSTRAC expects the card number to be present in the transfer message and to be monitored for. This should be an active compliance checkpoint, not an assumption.
Third, maintain the audit trail between the refund transfer message and the original transaction reference. Internal systems should be capable of linking the two, and that linkage should be verifiable on request.
Fourth, evidence your decision making when information is missing. If the card number is absent from an inbound transfer message, document why the transfer was rejected or what steps were taken under your AML and CTF policies.
How Tranche Two Consultants Can Help
Tranche Two Consultants works with regulated entities on AML and CTF compliance, including travel rule readiness and obligations mapping. If your institution is working through how the travel rule applies to specific payment types, including refunding merchant payments, we can help you interpret the framework, review your controls, and build practical compliance processes. Our published AML terms library supports compliance teams with plain language explanations of regulatory concepts, and our consulting work translates those concepts into operational controls.
Explore our AML terms library for related definitions, read our blog for practical compliance guidance, or get in touch to discuss your travel rule obligations directly.
“Bookmakers sit at a natural convergence point for cash, speed and anonymity. AUSTRAC’s focus reflects the reality that wagering platforms can be misused as value transfer mechanisms if risk controls are not actively applied.”
Common Questions About This Payment Type
Does the transfer message need to include payer information when refunding a merchant payment?
No. AUSTRAC lists refunding a merchant payment as an exception for payer information in the transfer message. The card number takes the place of the standard payer identity fields in this payment type.
What is the minimum information the transfer message must contain?
The card number must be included in the transfer message for a refunding merchant payment. That is the minimum content AUSTRAC requires for this payment type.
Does the payee full name need to be included?
No. The exception that applies to refunding a merchant payment covers both payer information and the payee full name. Neither is required in the transfer message, provided the card number is present.
What happens if the card number is missing from the transfer message?
A beneficiary institution may reject the transfer or apply its AML and CTF policies. The absence of the card number means the minimum travel rule requirements for this payment type have not been met.
Is this exception available for all card based refunds?
The exception applies specifically to refunds of merchant payments. It is not a general exception for card based transactions. Classification matters, and the payment must genuinely be a refund connected to an original merchant payment for the exception to apply.
Want an Expert Eye on Your Compliance Framework?
We have worked across ordering, intermediary, and beneficiary institutions. We know where things go wrong.
