Log into Sandbox

## Why this product?

Tax refunds have been increasingly targeted by fraudsters, leading to risks for both financial institutions and their customers. In the absence of an efficient solution, manual review of transactions becomes necessary, which can be time-consuming and error-prone. Payment screening is designed to automate this process to help in preventing suspicious activity,and also ensure that genuine transactions are not unnecessarily delayed or returned due to criteria failures.

## What this means to you

In case your Operations team is engaged in the process of manually reviewing tax transactions for name matching, the outlined capability facilitates reduction of the manual effort, therefore driving saving of Operational cost.

Galileo offers the flexibility to let you choose whether to manage transactions flagged for review, post payment screening in-house, or have Galileo Fraud Operations manage it, on your behalf.

## What this means to your customers

The automated receiver-name matching for tax refunds is designed to enable good transactions to continue processing without the need for manual review, so the funds can post to the account without the additional delay.

## Key capabilities

  • You can post the transaction (per settlement date) after manual review, or force-post it to bypass the load-limit review.

  • Return transactions with the appropriate return code.

  • Mark a transaction for additional review to indicate that a first review has occurred, but that an additional review needs to occur before a decision is made.

  • Generate reports for transactions being sent to manual review and include the actions taken.

## What you provide

Work with your relationship manager (RM) to assess the channel of integration.

## What Galileo provides

Galileo offers two methods to perform manual review: using the Customer Service Tool (CST) or our Program API ([Get Pending Deposits](🔗) and [Modify Pending Deposits](🔗)) to perform manual review.

## How it works

Incoming tax refunds are automatically inspected for a match on the receiver name, and any refunds that contain a mismatch are flagged for manual review. This is an example of how it can be set up to help identify suspicious tax refunds, which uses source identification and name matching.

### Example scenario: A questionable tax refund



  1. Payment screening automatically inspects incoming ACH transactions and determines if they are a federal deposit or a tax return from a particular state (source identification).

  2. The payment screening function proceeds to compare the name in the incoming ACH transaction to the name in Galileo's system (name-matching).

    1. If name-matching is a **success**, the transaction is processed as normal and validated against other controls, such as amount-threshold checks and load-limit checks (if set for the program).

    2. If name-matching **fails**, the transaction is sent to manual review, where it requires further action from the operations manager (either on your side or Galileo's). The category of the transaction is flagged as `RNM`. See the workflow below for more details.

## Managing transactions under review

### Via CST

Review queued transactions from the Customer Service Tool (CST) on the Payment Posts & Returns page. Reach out to your Galileo representative for access to the guide.

### Via Program API

When using the Program API, this workflow consists of three simple steps:

  1. Call the [Get Pending Deposits](🔗) endpoint to retrieve a list of incoming ACH credits pending manual review.

  2. Look for transactions with the `RNM` category code (name mismatch).

  3. Call the [Modify Pending Deposit Status](🔗) endpoint with the decision to approve or reject each `RNM` transaction.

    1. If you reject the transaction, use the return code R17 to indicate that the entry was initiated under questionable circumstances. This return code is available only to programs that use Payment Screening for tax refunds.

## Viewing Incoming ACH Transactions

Request the [Incoming ACH](🔗) <<glossary:CDF>>, which contains all of the incoming ACH transactions from the previous day.