Setup GIACT eCheck Verification

GIACT uses gVERIFY®, which provides real-time status updates for business or customer accounts to validate them before approving a deposit or accepting payment.

Getting Started

Before you begin running eCheck Verifications for Merchant transactions, you’ll want to set up a GIACT eCheck Verification Fee and apply it to the Merchant or add the Merchant to an existing Group with the fee set up.

Setting Up a GIACT eCheck Verification Fee to apply on a Merchant

Set up a new Group to apply the GIACT eCheck Verification Fee:

Step 1: On the Groups page, click ADD GROUP, enter the group name, then, click CREATE GROUP.

---

Apply the GIACT eCheck Verification Fee to the existing Group:

Step 2: From the Group Profile, click the Fees tab, then click ADD FEES to open an Add Fees lightbox.

Step 3: Set “When to trigger a fee?” to “GIACT eCheck Verification”, add the required info and click ADD.

Step 4: Return to the Group Profile, click ADD MEMBERS, select the Merchant, and click SAVE.

You can read more about Fee setups in the articles below:

The selected root page could not be found.

Now that you’re set up to apply the GIACT eCheck Verification Fee, you can begin running policy checks on transactions to apply automated risk decisions based on eCheck verification responses.

Reviewing GIACT Check Alerts for Merchants

API Request - Policy Run Summary

We have created the new endpoint (below) to run a GIACT policy check on a given transaction or set of transactions.

Query Parameter	Type	Required	Notes
{txn-id}	string	Required	Valid values are transactions that have taken place on the platform and follow the alphanumeric string format. Example: t1_txn_12a3bc4de56f789012gh3ij Note: The Transaction ID entered here will also appear in the subject field of your API call response within the results object.

The {txn-id} needs to be replaced with the given transaction ID which needs to be verified if GIACT was called and the response of GIACT call.

Tip: To run this call in the Sandbox, simply update the base URL to https://apiv2.stage.payrix.com/risk/v2. See Policy Run Summary Sandbox Testing below for more information.

Policy Run Summary Response Parameters

The expandable content below gives more in-depth information about the specific parameters available and required in the response body:

Policy Run Summary Response Body Example

{
    "uuid": "XXX7c-038a-4881-af7d-7c029e022bbd",
    "policyUuid": "XXX90c-6b40-40fe-90e7-406da5d70852",
    "subject": " {txn-id} ",
    "action": "BLOCK",
    "results": [
        {
            "decisionType": "GiactTxnInquiry",
            "result": "BLOCK"
        }     
    ] 
}

GIACT Alerts in the Portal

The GIACT Check alerts will be shown in the Alerts section of the Merchant Profile page of the Merchant performing the transaction.

Note: Only Facilitators can view the GIACT “Code” field from this page. Referrers and Merchants are unable to view the specific GIACT Check block code. Additionally, Payrix is not permitted to disclose the nature or reason for a GIACT response to Merchants or Referrers.

Below are the possible GIACT Inquiry Check response messages and the descriptions.

Message	Description
SKIP	The data submitted did not the meet initial requirements to begin a GIACT review.
BLOCK	The transaction data was reviewed with GIACT and has been declined with an assessed fee. If a BLOCK is issued from a GIACT Inquiry Check, the Adverse Action Notice Requirement Message (shown below) will be displayed.
PASS	The transaction data was reviewed with GIACT and approved with an assessed fee.

Handling Unsuccessful eCheck (GIACT) Transaction

API Response - GIACT Transaction Status

Below is an example of the Status in Transaction Response for a failed transaction.

"city": "Pompano Beach",
"state": "FL",
"zip": "33069",
"country": "USA",
"phone": "0005290475",
"mid": "010495182",
"status": 2,
"refunded": 0,

Portal

For end-users, the transaction will initially be attempted. If the transaction is unsuccessful they will have to correct any incorrect or invalid data and try the transaction again.

Policy Run Summary Sandbox Testing

Creating a test transaction to execute a Policy Run Summary is done in two parts:

1. Create a new Transaction using testing trigger payment method values.

Process a POST request using the /txns endpoint, with the following values in the payment object within:

"payment": {
    "method": 9,
    "number": "0000000004",
    "routing": "122105278"
  }

"payment": {
    "method": 9,
    "number": "0000000009",
    "routing": "122105278"
  }

"payment": {
    "method": 9,
    "number": "0000000001",
    "routing": "122105278"
  }

"payment": {
    "method": 9,
    "number": "0000000003",
    "routing": "122105278"
  }

2. Use the returned id response value to execute the Policy Run Summary

Result: You’ve now successfully created a test GIACT action response to either Block, Hold, or Reserve funds for a transaction, as well as allowing the transaction to process as normal, being marked for further review at a later time.

Example Response:

{
    "uuid": "XXX7c-038a-4881-af7d-7c029e022bbd",
    "policyUuid": "XXX90c-6b40-40fe-90e7-406da5d70852",
    "subject": "t1_txn_12a3bc4de56f789012gh3ij",
    "action": "BLOCK",
    "results": [
        {
            "decisionType": "GiactTxnInquiry",
            "result": "BLOCK"
        }     
    ] 
}