Difference between revisions of "Accept.js by Authorize.net"
From WHMCS Documentation
m |
|||
| 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 | + | 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== | ==Setup== | ||
| − | # Ensure that you have installed a valid SSL certificate for your site and that your system URL in ''Setup >> General Settings'' | + | |
| − | + | To set up this module: | |
| − | # | + | |
| − | # | + | # 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. |
| − | + | # Activate the '''Accept.js''' module in '''Setup > Payments > Payment Gateways'''. | |
| − | # Customise the Display Name | + | # 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>. |
| + | # Click '''Save Changes''' to complete the setup process. | ||
Accept.js is now active and ready for use. | Accept.js is now active and ready for use. | ||
| − | <div class="docs-alert- | + | <div class="docs-alert-danger"> |
| + | <span class="title">Warning</span><br /> | ||
| + | The Accept.js gateway module is not compatible with the ''Modern'' or ''Boxes'' order form templates. | ||
| + | </div> | ||
==Payment Workflow== | ==Payment Workflow== | ||
| − | + | ||
| − | + | This workflow supports automated recurring and on-demand billing. | |
| − | + | ||
| − | + | 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. | |
| − | + | ||
| − | + | * Within this workflow, customers never leave your WHMCS installation during checkout or when updating their card. | |
| − | + | * The system submits personal card information directly to Accept.js and never stores it on your local WHMCS installation. | |
| − | + | ||
| + | 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 | + | 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 | + | 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: | 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 | + | # 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 | + | # 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"> | + | <div class="docs-alert-info"> |
| + | <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> | ||
Revision as of 16:42, 18 May 2020
Supported Features
| Type | One Time | Recurring | Refunds | 3D Secure |
|---|---|---|---|---|
| Token | Yes | Yes | Yes | No |
| Remote Update Card | Remote Delete Card | AddPayMethod API |
|---|---|---|
| Yes | Yes | No |
The WHMCS Official Accept.js by Authorize.net module was introduced in WHMCS 7.3.
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
To set up this module:
- 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 serve pages over SSL. Your system URL should begin with https and visitors should be able to navigate your site without security acceptance prompts.
- Activate the Accept.js module in Setup > Payments > Payment Gateways.
- 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.
- Customise the Display Name. We recommend Accept by Authorize.net.
- Click Save Changes to complete the setup process.
Accept.js is now active and ready for use.
Warning
The Accept.js gateway module is not compatible with the Modern or Boxes order form templates.
Payment Workflow
This workflow supports automated recurring and on-demand billing.
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.
- Within this workflow, customers never leave your WHMCS installation during checkout or when updating their card.
- The system submits personal card information directly to Accept.js and never stores it on your local WHMCS installation.
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
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 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.
- Ensure that you have activated the Accept.js module.
- Select the Deactivate link for your previous merchant gateway provider.
- When the system prompts you, select Accept.js.
- Click OK to complete the process.
Note