Connecting to Authorize.net

Set up Authorize.net to collect payments from recipients after they sign your contracts.

April 23, 2026

What is Authorize.net payment collection?

GetAccept integrates with Authorize.net to automatically collect payments from recipients after they sign your contracts. When a recipient completes the signing process, a payment window can appear, allowing you to collect credit card information securely through Authorize.net. This streamlines the sales-to-payment workflow by eliminating the need for separate invoicing or manual payment collection steps.

Prerequisites and plan requirements

To use Authorize.net payment collection with GetAccept, you need:

• An active Authorize.net account with merchant credentials
• A GetAccept Professional or Enterprise Plus plan
• Admin access to GetAccept settings
• Your Authorize.net API Login ID and Transaction Keys

If you do not have an Authorize.net account, you must create one directly with Authorize.net before connecting to GetAccept.

How to connect Authorize.net to GetAccept

Follow these steps to enable Authorize.net payment collection:

1. Log in to GetAccept and click your profile image in the top-right corner
2. Select Settings
3. Navigate to Integrations
4. Scroll down to find Authorize.net
5. Click Settings next to Authorize.net
6. A configuration window will open

Configuring Authorize.net credentials and settings

In the Authorize.net settings window, you will be prompted to enter the following information:

• API Login ID , Your Authorize.net API credentials for authentication
• Transaction Keys , Unique keys required to process payments securely
• Payment landing page URL , Where recipients are redirected after completing payment (optional but recommended for confirmation pages)
• Payment delay timing , How many seconds after signing the payment window should appear (configurable from immediate to delayed)

Enter all required credentials accurately. When you are finished, click the Save button to complete the connection.

Note: You must be on the Professional or Enterprise Plus plan to enable Authorize.net payment collection.

How payment collection works in the signing workflow

Once Authorize.net is connected, payment collection operates as follows:

• A contract is sent with a deal value greater than zero
• The recipient signs the contract using the standard signing process
• After the recipient completes all signatures, a payment window automatically appears (after the delay period you configured)
• The recipient enters their credit card information directly in the Authorize.net payment form
• The payment is processed securely through Authorize.net
• The recipient receives confirmation of payment

Important: The payment window only appears on contracts with a deal value greater than zero. Ensure you set a deal value before sending the contract if you want to collect payment.

Payment amounts and currency

GetAccept automatically attempts to charge the recipient the deal value you specified when creating or sending the contract. The first payment processed equals the deal value set on the send-out. You can configure additional payment structures or recurring charges directly within your Authorize.net account after the initial payment is collected.

Currency is determined by your GetAccept entity settings. Verify your entity's default currency is correct before sending contracts with payment collection enabled.

Using restricted API keys for enhanced security

To increase security, you can use Authorize.net restricted API keys instead of your full API credentials. Restricted keys limit the permissions available to GetAccept, reducing risk if credentials are ever compromised.

If you choose to use a restricted API key, it must have the following minimum permissions:

• Charges: Write
• Customers: Write
• Disputes: Read

Generate a restricted key in your Authorize.net account and enter it in the GetAccept Authorize.net settings window the same way you would enter your standard API Login ID.

Verifying successful payment collection

After a recipient completes payment, you can verify the transaction in two places:

• Authorize.net dashboard , Log into your Authorize.net merchant account to view all transactions, settlements, and payment details
• GetAccept document timeline , Open the signed contract in GetAccept and review the Timeline tab to confirm payment was processed

The recipient will receive an email confirmation of the payment. You can also check your bank account or merchant settlement reports for deposit confirmation.

Troubleshooting common connection issues

Connection fails or credentials are rejected

Verify that your Authorize.net API Login ID and Transaction Keys are correct and active. Check your Authorize.net account settings to confirm the credentials have not expired. If using a restricted key, ensure it has all required permissions listed above.

Payment window does not appear after signing

Confirm that:

• The contract has a deal value greater than zero
• Authorize.net integration is saved and enabled in Settings → Integrations
• The recipient's browser allows pop-ups (payment window appears as a pop-up)
• The configured payment delay has elapsed since signing completion

Payment declines or processing errors

Payment processing errors are typically returned by Authorize.net based on the recipient's card or account status. The recipient will see the error message from Authorize.net. Check the Authorize.net dashboard for detailed decline codes and contact Authorize.net support if needed.

Recipient email bounces or payment confirmation not received

Verify the recipient's email address is correct. Check your email provider's spam folder. If emails consistently bounce, review your entity's email settings and communication templates in GetAccept Settings.

Data security and compliance

GetAccept does not store recipient credit card information. All payment data is transmitted directly to Authorize.net and processed securely. Your Authorize.net account is responsible for maintaining PCI DSS compliance and protecting stored payment records.

Protect your Authorize.net API credentials the same way you protect banking information. Never share credentials with unauthorized users. Regularly rotate API keys and use restricted keys when possible to minimize exposure.