Deprecation note: The Docebo for Authorize.net SIM Integration has reached its End of Support on October 1, 2020, and its End of Life on January 1, 2021. Authorize.net Accept Hosted is a replacement for Authorize.net SIM with notable advantages.
Introduction
The Authorize.net payment gateway is an authorized payment method that can be used with the e-commerce features of your platform. The Docebo integration with Authorize.net is based on the Accept Hosted payment form (opens in a new tab).
Prerequisites
The Authorize.net integration is available on the platform with the e-commerce pack. Contact your Docebo representative for information about how to obtain it.
- To configure this integration, you will need a valid merchant account on Authorize.net.
Requirements and limitations
- Some currencies supported by Docebo may not be accepted by Authorize.net, so remember to check if your currency is supported by both systems before proceeding. Check out the complete list of the currencies supported by Docebo.
- When working with the Extended Enterprise, configure the settings of Authorize.net in the root domain. If some domains require a different configuration, apply the configuration locally, in the E-Commerce tab of the Extended Enterprise app.
Configuring Authorize.net Accept Hosted in Docebo
In order to configure Authorize.net Accept Hosted, log into your platform as the Superadmin, then access the Navigation menu > Configuration (spanner icon) > E-commerce > Authorize.net.
Activate the Enable Authorize.net payment gateway toggle to enable this payment gateway in your platform. Then, use the corresponding text boxes to fill in the Login ID and the Transaction key. These values authenticate you as an authorized merchant when submitting transaction requests.
You can test the configuration before using the real environment, by selecting the option to enable the sandbox mode. Press Save changes when finished.
Obtaining the Login ID and the Transaction Key
The Login ID is a complex value that is at least eight characters in length, includes uppercase and lowercase letters, numbers, and/or symbols, and identifies your account to the payment gateway. It is not the same value as your login ID for logging into the Merchant Interface, as the two values perform different functions. The Login ID is used by Docebo to communicate with the payment gateway to submit transactions. It is only used for Docebo's connection to the payment gateway.
The Transaction Key is a 16-character alphanumeric value that is randomly generated in the Merchant Interface. It works in conjunction with your Login ID to authenticate you as an authorized user of the Authorize.Net Payment Gateway when submitting transactions from Docebo.
In order to obtain these values, log in to the Merchant Interface at https://account.authorize.net, select Settings under the Account area in the main menu and click on API Credentials & Keys in the Security Settings section.
If you have not already obtained a Login ID and Transaction Key for your account yet, you will need to enter the secret answer to the secret question you configured during the account activation process. Press Submit to terminate.
Please Note! The Transaction Key for your account is displayed on a confirmation page. Once you navigate away from the confirmation page, there is no other way to access the Transaction Key in the your merchant interface.
You will have to generate a new Transaction Key. It is highly recommended that you create a new Transaction Key regularly (i.e. every six months) to strengthen the security of your payment gateway account. You then need to save the new Transaction Key in the corresponding area in your platform to update the integration code. Failure to do so will result in a disruption in transaction processing.
Configuring the relay response URL in Authorize.net
Finally, configure the Response URL. To do so, access the Account tab. In the Transaction format settings, click on Response/Receipt URLs. Set the Default Receipt URL by pressing Edit in the corresponding line and by entering the URL of your platform; this configuration is mandatory. The Default Relay Response URL is optional but we suggest you configure it if the business logic you implemented in Authorize.net allows you to do so. Remember that once you enter Default Relay Response URL, you will not be able to modify it.
For those using the 7.0 theme with a custom domain, remember to insert your custom domain URL. For those using the 6.9 theme, always use the docebosaas URL. Use the examples below for guidance (note that anything in brackets will need to be replaced with your own LMS information):
-
Custom domain:
https://[custom_domain]/ecommerce/v1/authorizedotnet/relay_response -
Standard domain:
https://[mylms].docebosaas.com/ecommerce/v1/authorizedotnet/relay_response -
Extended Enterprise:
https://[mylms].docebosaas.com/[extendedenterprisedomainfoldername]/ecommerce/v1/authorizedotnet/relay_response
Note on the MD5 Hash end of life
Authorize.net introduced the SHA2 encryption algorithm on January 29, 2019, and deprecated the MD5 Hash algorithm at the end of June 2019. For existing integrations, your integration continues working without any interruptions at this time, and your Signature Algorithm will be set to MD5. Existing keys will still be encrypted with MD5 Hash, but we suggest you switch to SHA2 as soon as possible. Please note that even if the Docebo interface allows you to roll back to MD5 after switching to SHA2, Authorize.net does not, and the rollback would cause a key mismatch.
Best practices
- When selecting Authorize.net as the payment gateway for an e-commerce transaction, the sum of the characters typed in Address 1 and Address 2 fields in the Billing Information panel when finalizing the payment cannot exceed 59. And the characters typed in the City field cannot exceed 40. Authorize.net does not handle addresses or city names with more than these characters.
- Remember that the Invoice field of Authorize.net is populated with a unique Docebo internal invoice number for every transaction performed in Docebo Learn to prevent the creation of duplicated transactions
- When a user pays through Authorize.net but closes the browser tab before returning to the platform’s confirmation page, the administrator will need to manually verify the transaction in the Authorize.net portal.