Learn about how to use as your payment processing gateway with GiveGab Enterprise.

Ashleigh Alldredge avatar
Written by Ashleigh Alldredge
Updated over a week ago

The following best practices are GiveGab Enterprise recommendations only and you should verify if they are the correct approach for your specific needs prior to implementing them. 

Authorize Overview

Authorize AIM and Authorize CIM are Payment Gateways that are compatible with GiveGab Enterprise. Transaction options available through include: Advance Payment, Recurring Payments, Installment Plans, and ACH Transfers. Credentials Required to use include: API Login ID and Transaction Key. 

Important: Credential information is highly confidential and should not be communicated to GiveGab Enterprise via email. The most secure way to provide this information is over the telephone directly to GiveGab Enterprise Support. Call them at 512-474-4447 and choose option 1. 

Authorize AIM vs. CIM

Advanced Integration Method (AIM)

AIM accounts do not store financial information, such as credit card information. This prevents using recurring payments and advanced payments.

Customer Information Manager (CIM)

CIM accounts store customers' sensitive payment information on secure servers. This allows for easier payment processing for returning customers, recurring payments, and advanced payments.

eChecks (ACH) payments available

ACH payments, also known as e-checks, are made directly from the donor/registrant's checking account. If you want to start accepting ACH payments, verify that your gateway account is configured to allow checking account transactions and then notify GiveGab Enterprise support so we can configure your gateway appropriately.

What information does GiveGab Enterprise need?

GiveGab Enterprise needs your Transaction Key and your API Login ID to set up as your gateway processor. Your API Login ID and Transaction Key are unique pieces of information specifically associated with your payment gateway account. However, the API login ID and Transaction Key are NOT used for logging into the Merchant Interface. They are used by the payment gateway to authenticate that GiveGab Enterprise is authorized to submit transactions on your behalf.

Your Transaction Key is not visible in your Merchant Interface after it is initially assigned because it contains sensitive account information. If you need help finding this information, contact support.

Transaction Key

The Transaction Key is a 16-character alphanumeric value that is randomly generated in the Merchant Interface and is used as an additional layer of authentication when submitting transaction requests from your website.

API Login ID

The API Login ID is a complex value that identifies your account to the payment gateway when submitting transaction requests from your website. While not valid for logging into the Merchant Interface, its purpose is similar to a login ID—it's like your website logging onto the payment gateway. The API Login ID is at least eight characters in length, includes uppercase and lowercase letters, numbers, and/or symbols.

Did this answer your question?