Authorize.net Integration

Retreat Manager and Retreat Portal require authorize.net to perform any financial transactions involving credit cards or checks (eChecks).

Getting an authorize.net account

If you don't already have an authorize.net account, then you can get one by going to the following site: https://www.authorize.net/sign-up/pricing.html

There are two options. The option on the right (Payment Gateway Only) is likely what you want as you probably already have a merchant account through your bank. The merchant account is also where you would negotiate your per-transaction fees.

Creating a login for DKD Software Support

It is strongly recommended to create a login for DKD Software Support. The email to use is support@dkdsoftware.com. You may choose any username you like. On rare occasion our support staff may log in to your authorize.net account to investigate transactions and to assist with completing payments.

Creating a Client Key

For Retreat Portal to process financial transactions a Client Key is required.

Log in to authorize.net.

Go to Account > Account and API Settings > API Credentials and Keys

If you already have a Client Key, then you can reuse that. Otherwise click the button to request one to be created. *Do not disable the old key if you already have one.*

Please copy and send the client key to support@dkdsoftware.com - note in the image below the client key is highlighted, but also obscured for security purposes.

Creating API Credentials & Keys

To process financial transactions the API Credentials and Keys must be shared with support@dkdsoftware.com

Log in to authorize.net.

Go to Account > Account and API Settings > API Credentials and Keys

Copy the API Login ID (highlighted, but obfuscated in the image below) and send it to support@dkdsoftware.com.

If you already have a Transaction Key, then it must be sent to support@dkdsoftware.com as well. If you don't know your Transaction Key, then things get much more complicated. There is a good chance you have other software services using the Transaction Key and, as authorize.net states, the current key will be disabled if a new one is created. Contact support@dkdsoftware.com for assistance on how to ensure a smooth migration.

Disable High-Volume Fraud Filters

If you think you may get bursts of registrations at the same time (e.g. you have a popular program and guests all try to register early in the day the program is available), then we recommend disabling the following filters.

Account > Account and API Settings > Advanced Fraud Detection Suite Settings

Tools > Fraud Detection Suite. Disable the 'Card Testing Settings' filters.

Click on the Configure button for each filter.

Uncheck 'Enable Filter' and click Save.

Or, if you want to keep the filter, the be sure to set the allowed quantity to something larger than you would reasonably expect. AND be sure to set the action to 'Decline the transaction'. If you do not decline the transaction, then you must manually decline the transaction in Authorize.net and remove the transaction from Retreat Manager and Retreat Portal.

Disable Required Fields

Under Payments > Payment Settings > Payment Form > Form Fields

Ensure all of the fields have 'Required' unchecked. These are the fields that Authorize.net enforces as mandatory and if one is chosen that does not match what is required in Retreat Portal, then payments can fail. Do not require the security code field either.