Account validation with giact

When accepting ACH Direct Debit payments, Nacha requires you to validate that the shopper's bank account details are correct, if it is a consumer account. To make this validation easier for you, we have partnered with giact gVERIFY.

When you use giact gVERIFY, you can validate account details in real time. This reduces the chance that transactions are reversed because it turns out, for example, that the routing number is incorrect or the account has been closed.

Requirements

How it works

1. The shopper selects ACH Direct Debit on your payment form.

2. You collect the required details from the shopper:

   • Bank account number
   • ACH routing number

     Alert your shoppers that some banks have different routing numbers for different transfers. Shoppers should not provide their wire transfer routing number.

   • Bank account type: checking or savings.

     The account type is not verified by giact. But you need to specify it when you make a payment request for the actual amount. This avoids unnecessary chargebacks due to account type mismatches.

   • Account owner's name
   • Account owner's address

3. You send a zero-value authorization request with the details that the shopper provided.

4. We send the details to giact gVERIFY and return the outcome in the zero-value authorization response.

5. Based on the the zero-value authorization response, you decide on your next step: make a payment request for the actual amount, or ask the shopper to provide correct details or use a different payment method.

Validate using zero-value authorization

After you have gathered the shopper's account details, verify those details as follows:

1. From your server, make a /payments request, specifying:

   • paymentMethod.type: ach
   • paymentMethod.bankAccountNumber: the bank account number.
   • paymentMethod.bankAccountType: the type of bank account. Allowed values: checking, savings.
   • paymentMethod.bankLocationId: the ACH routing number of the account.
   • paymentMethod.ownerName: the name on the bank account.
   • billingAddress (Optional): the account owner's address information.
   • amount.currency: USD
   • amount.value: 0

2. In the zero-value authorization response, check the following parameters:

   • additionalData.bankVerificationResultRaw: the details of the validation as reported by giact. See the table with validation result values.
   • additionalData.bankVerificationResult: indicates if the account passed the validation. Possible values: Passed or Failed.

3. Based on the response, determine your next step.

   • If the account passed validation, make a payment request for the actual amount with the same account details that you provided in the zero-value request.
   • If the account didn't pass validation, ask the shopper for the correct account details or for a different payment method.

Validation result values

In the zero-value authorization response, the additionalData.bankVerificationResultRaw parameter can include the following information.

Test and go live

giact gVERIFY is only available in the live environment.

Testing:

• To test a successful validation, make a zero-value authorization request with a valid bank account and routing number. The account will not be charged because the payment amount is USD 0.00.
• To test a failed validation, make a zero-value authorization request with an invalid bank account and routing number.

See also