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.

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

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

Follow these steps to enable Authorize.net payment collection:

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

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

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

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.

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.

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:

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.

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

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

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.

Confirm that:

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.

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.

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.