Accept.js by Authorize.net - Revision history

SarahK: /* Migrating to Accept.js */

2022-09-28T19:30:57Z

‎Migrating to Accept.js

SarahK: /* Adding the Accept.js by Authorize.net Payment Gateway */

2022-09-28T19:30:03Z

‎Adding the Accept.js by Authorize.net Payment Gateway

SarahK: /* Adding the Accept.js by Authorize.net Payment Gateway */

2022-09-07T20:06:26Z

‎Adding the Accept.js by Authorize.net Payment Gateway

SarahK: /* Migrating to Accept.js */

2022-04-18T15:04:56Z

‎Migrating to Accept.js

SarahK at 20:35, 18 March 2022

2022-03-18T20:35:59Z

AlexN at 10:57, 21 September 2021

2021-09-21T10:57:56Z

SarahK at 16:03, 4 August 2020

2020-08-04T16:03:38Z

SarahK at 16:42, 18 May 2020

2020-05-18T16:42:25Z

John at 12:15, 11 March 2020

2020-03-11T12:15:23Z

John at 12:05, 11 March 2020

2020-03-11T12:05:21Z

@@ Line 54: / Line 54: @@
 # Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''.
-# Ensure that you have activated the Accept.js module.
+# Ensure that you have activated the Accept.js module. If you have not, go to the appropriate location for your version of WHMCS and activate it:
 # Select the '''Deactivate''' link for your previous merchant gateway provider.
 # When the system prompts you, select ''Accept.js''.

@@ Line 21: / Line 21: @@
 # Ensure that you have installed a valid SSL certificate for your site and have configured your system URL in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[General Settings]]''' (or '''Setup > General Settings''' prior to WHMCS 8.0) to [[Configuration|serve pages over SSL]]. Your system URL should begin with <tt>https</tt> and visitors should be able to navigate your site without security acceptance prompts.
 # Go to the appropriate location for your version of WHMCS:
-#* For WHMCS 8.6 and later, go to '''Addons > [[Apps and Integrations|Apps & Integrations]]''' or '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > Apps & Integrations'''.
+#* For WHMCS 8.0 and later, go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > Apps & Integrations''' or '''Addons > [[Apps and Integrations|Apps & Integrations]]'''.
-#* For WHMCS 8.0 to 8.6, go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' and choose '''All Payment Gateways'''.
+#* For WHMCS 7.10 and earlier, go to '''Setup > Products/Services > [[Payment Gateways]]''' and choose '''All Payment Gateways'''.
 # Click '''Authorize.net Accept.js'''.
 # Check '''Show on Order Form''' to display this payment method in the Client Area during checkout.

@@ Line 20: / Line 20: @@
 # Ensure that you have installed a valid SSL certificate for your site and have configured your system URL in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[General Settings]]''' (or '''Setup > General Settings''' prior to WHMCS 8.0) to [[Configuration|serve pages over SSL]]. Your system URL should begin with <tt>https</tt> and visitors should be able to navigate your site without security acceptance prompts.
-# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Payment Gateways'''.
+# Go to the appropriate location for your version of WHMCS:
-# Choose the '''All Payment Gateways''' tab.
+#* For WHMCS 8.6 and later, go to '''Addons > [[Apps and Integrations|Apps & Integrations]]''' or '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > Apps & Integrations'''.
 # Click '''Authorize.net Accept.js'''.
 # Check '''Show on Order Form''' to display this payment method in the Client Area during checkout.

@@ Line 52: / Line 52: @@
 To migrate all of your credit card processing to Accept.js, follow the steps below:
-# Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''.
+# Navigate to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''.
 # Ensure that you have activated the Accept.js module.
 # Select the '''Deactivate''' link for your previous merchant gateway provider.

@@ Line 1: / Line 1: @@
 {{gateways
 | type = token
@@ Line 8: / Line 15: @@
 | AddPayMethod API = no
 }}
-The WHMCS Official Accept.js by <nowiki>Authorize.net</nowiki> module was introduced in WHMCS 7.3.
+To set up the Accept.js by Authorize.net payment gateway in WHMCS:
-−
-Accept.js is a tokenised gateway. As a result, Accept.js stores customers' submitted personal credit card information remotely. We recommend using a tokenised gateway for security and reduced liability.
+# Ensure that you have installed a valid SSL certificate for your site and have configured your system URL in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[General Settings]]''' (or '''Setup > General Settings''' prior to WHMCS 8.0) to [[Configuration|serve pages over SSL]]. Your system URL should begin with <tt>https</tt> and visitors should be able to navigate your site without security acceptance prompts.
+# Go to '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' or, prior to WHMCS 8.0, '''Setup > Products/Services > Payment Gateways'''.
-==Setup==
+# Choose the '''All Payment Gateways''' tab.
+# Click '''Authorize.net Accept.js'''.
-To set up this module:
+# Check '''Show on Order Form''' to display this payment method in the Client Area during checkout.
+# Enter the '''API Login ID''' and '''Transaction Key''' values. You can find these in your Authorize.net account at '''Account > Security Settings > API Credentials & Keys'''.
-# Ensure that you have installed a valid SSL certificate for your site and that you have configured your system URL in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings''' (or '''Setup > General Settings''' prior to WHMCS 8.0) to [[Configuration|serve pages over SSL]]. Your system URL should begin with <tt>https</tt> and visitors should be able to navigate your site without security acceptance prompts.
+# Enter your '''Public Client Key''' value. You can find this in your Authorize.net account at '''Account > Security Settings > Manage Public Client Key'''.
-# Activate the '''Accept.js''' module in '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''.
+# Click '''Save Changes'''.
 <div class="docs-alert-danger">
@@ Line 30: / Line 33: @@
 </div>
-==Payment Workflow==
+== Payment Workflow ==
 This workflow supports automated recurring and on-demand billing.
@@ Line 41: / Line 44: @@
 The system uses the Accept.js API for obtaining transaction information, and uses the Accept.js.js library for payments and card updates.
-==Migrating to Accept.js==
+== Migrating to Accept.js ==
 Our Accept.js module supports migrating credit card details from WHMCS to the Accept.js tokenisation system. This allows for a seamless transition from another merchant gateway provider to Accept.js.
@@ Line 58: / Line 61: @@
 <span class="title">Note</span><br />
 The system will send existing locally-stored credit card details to Accept.js and convert them to a token the first time that the client attempts a payment using the Accept.js module. Until that time, locally-stored credit card details will remain within WHMCS.</div>

@@ Line 6: / Line 6: @@
 | deletecc = yes
 | refunds = yes
 }}

@@ Line 8: / Line 8: @@
 }}
-The WHMCS Official Accept.js by Authorize.net module was introduced in WHMCS 7.3.
+The WHMCS Official Accept.js by <nowiki>Authorize.net</nowiki> module was introduced in WHMCS 7.3.
-Accept.js is a tokenised gateway. As a result, customers personal credit card information is submitted to and stored remotely by Accept.js. Using a tokenised gateway is recommended for security and reduced liability.
+Accept.js is a tokenised gateway. As a result, Accept.js stores customers' submitted personal credit card information remotely. We recommend using a tokenised gateway for security and reduced liability.
 ==Setup==
-# Ensure that you have installed a valid SSL certificate for your site and that your system URL in ''Setup >> General Settings'' is configured to serve pages over SSL.
-#* Your system URL should begin with "https" and visitors should be able to navigate your site without security acceptance prompts.
+To set up this module:
-# Begin by activating the '''Accept.js''' module in ''Setup > Payments > Payment Gateways''
-# Accept.js uses API keys for authentication. Upon activation, you will be asked to enter the API Login ID, Transaction Key, and Public Client Key.
+# Ensure that you have installed a valid SSL certificate for your site and that you have configured your system URL in '''Setup >> General Settings''' to [[Configuration|serve pages over SSL]]. Your system URL should begin with <tt>https</tt> and visitors should be able to navigate your site without security acceptance prompts.
-#* These can be found or generated inside the Authorize.net portal under ''Account > Security Settings > API Credentials & Keys''
+# Activate the '''Accept.js''' module in '''Setup > Payments > Payment Gateways'''.
-# Customise the Display Name as desired, we recommend ''Accept by Authorize.net''
+# When the system prompts you after activation, enter the '''API Login ID''', '''Transaction Key''', and '''Public Client Key'''. Accept.js uses API keys for authentication. You can find or generate these inside the Authorize.net portal under '''Account > Security Settings > API Credentials & Keys'''.
-# Click '''Save Changes''' to complete the setup
+# Customise the '''Display Name'''. We recommend <tt>Accept by Authorize.net</tt>.
 Accept.js is now active and ready for use.
-<div class="docs-alert-warning">'''Warning:''' The Accept.js gateway module is not compatible with the Modern or Boxes order form templates.</div>
+<div class="docs-alert-danger">
 ==Payment Workflow==
-# Automated recurring and on-demand billing is supported.
-# When making a payment, customers are able to select to use a previously stored card or enter a new one.
+This workflow supports automated recurring and on-demand billing.
-# Customers can update their credit card at any time from the client area.
-# Admin level users with the necessary permissions can also perform card updates from the admin area.
+When they pay, customers can choose to use a previously-stored card or enter a new one and can update their card at any time from the client area. Admin level users with the necessary permissions can also perform card updates from the admin area.
-# Customers never leave your WHMCS installation during checkout or updating their card.
-# Personal card information is submitted directly to Accept.js and is never stored in your local WHMCS installation.
+* Within this workflow, customers never leave your WHMCS installation during checkout or when updating their card.
-# The Accept.js API is used for obtaining transaction information.
+* The system submits personal card information directly to Accept.js and never stores it on your local WHMCS installation.
-# The Accept.js.js library is used for payments and card updates.
 ==Migrating to Accept.js==
-Our Accept.js module supports migrating credit card details stored locally within WHMCS to the Accept.js tokenisation system.  This allows for a seamless transition from another merchant gateway provider to Accept.js.
+Our Accept.js module supports migrating credit card details from WHMCS to the Accept.js tokenisation system. This allows for a seamless transition from another merchant gateway provider to Accept.js.
-Migration of existing clients' locally stored credit card data occurs during the next payment process per client. The first time a payment capture is attempted for an invoice using Accept.js, the credit card details will be submitted to Accept.js and a token created and stored. Any card details stored locally for that client will be removed.
+Migration of existing clients' locally-stored credit card data occurs during the next payment process for each client. The first time the system attempts a payment capture for an invoice using Accept.js, the system will submit credit card details to Accept.js and create and store a token. The system will remove any locally-stored card details for that client.
 To migrate all of your credit card processing to Accept.js, follow the steps below:
-# Navigate to ''Setup > Payments > Payment Gateways''
+# Navigate to '''Setup > Payments > Payment Gateways'''.
-# Ensure the Accept.js module has been activated
+# Ensure that you have activated the Accept.js module.
-# Select the '''Deactivate''' link for your previous merchant gateway provider
+# Select the '''Deactivate''' link for your previous merchant gateway provider.
-# When prompted to choose a replacement gateway to switch users of the previous gateway module to, select Accept.js
+# When the system prompts you, select ''Accept.js''.
-# Click '''OK''' to complete the process
+# Click '''OK''' to complete the process.
-<div class="docs-alert-info">'''Note:''' Existing credit card details stored locally will be sent to Accept.js and converted to a token the first time a payment is attempted for a client using the Accept.js module. Until that time, credit card details will remain stored locally within WHMCS.</div>
+<div class="docs-alert-info">

← Older revision		Revision as of 12:15, 11 March 2020
Line 1:		Line 1:
−	~~<div class="docs-alert-info"><i class="fa fa-info-circle"></i> This page describes a feature available in version 7.3 and above.</div>~~
	{{gateways		{{gateways
	\| type = token		\| type = token