Unreferenced Refunds

Overview

An unreferenced refund is a refund operation that is not linked to an original payment transaction.

Unlike referenced refunds, Oracle Payments does not validate whether the refund relates to a legitimate customer purchase or prior payment activity.

Because of this, unreferenced refunds are considered a high-risk payment operation.

Warning: Oracle strongly recommends against enabling unreferenced refunds. These should only be enabled where there is a legitimate operational business requirement.

Risk Acknowledgement and Liability

By requesting enablement and use of unreferenced refunds, you (Customer of Oracle Payments) acknowledges and accepts the operational, financial, fraud, and compliance risks associated with this functionality.

You understand and agree that:

You are solely responsible for refund activity initiated by your employees or authorized users
You bear responsibility for fraud, abuse, misuse, operational loss, or unauthorized refund activity
Oracle Payments does not validate whether an unreferenced refund relates to a legitimate customer purchase
Oracle Payments cannot prevent insider fraud, social engineering, or operational mistakes within the merchant organization
You are responsible for implementing operational controls and approval workflows
You are responsible for restricting refund capabilities to authorized personnel

Important: Failure to maintain appropriate operational controls may increase exposure to fraud, financial loss, compliance issues, and audit findings of which Oracle will not assume liability for.

Risks Associated with Unreferenced Refunds

Unreferenced refunds may increase exposure to:

Social engineering attacks
Vishing (voice phishing)
Insider fraud
Refund abuse
Human error
Unauthorized refund activity
Misuse outside standard payment flows

Before Enabling Unreferenced Refunds

Before enabling unreferenced refunds, merchants should ensure that appropriate operational controls are in place.

Employee Training

Ensure employees are trained on:

Social engineering awareness
Vishing (voice phishing) and impersonation scenarios
Refund approval procedures
Escalation handling

Access Controls

Restrict refund capabilities to authorized personnel only, such as:

Managers
Supervisors
Finance administrators

Reconciliation Processes

Implement reconciliation procedures to validate:

Refund activity
Refund approvals
Refund-to-sales relationships
Refund exceptions

Approval Procedures

Maintain documented:

Refund approval workflows
Escalation procedures
Audit processes
Exception handling policies

Important Considerations

Unreferenced refunds require explicit enablement by Oracle Payments
Some payment methods do not support unreferenced refunds
Additional fraud monitoring and operational oversight are strongly recommended
Reporting and reconciliation are more complex than referenced refunds