Accept.js by

From WHMCS Documentation

Revision as of 17:03, 3 November 2017 by Chance (talk | contribs) (Payment Workflow)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

This page describes a feature available in version 7.3 and above.

Supported Features

Type One Time Recurring Refunds 3D Secure
Token Yes Yes No No
Remote Update Card Remote Delete Card
Yes Yes

The WHMCS Official Accept.js by 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.


  1. 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.
  2. Begin by activating the Accept.js module in Setup > Payments > Payment Gateways
  3. 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.
    • These can be found or generated inside the portal under Account > Security Settings > API Credentials & Keys
  4. Customise the Display Name as desired, we recommend Accept by
  5. Click Save Changes to complete the setup

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

  1. Automated recurring and on-demand billing is supported.
  2. When making a payment, customers are able to select to use a previously stored card or enter a new one.
  3. Customers can update their credit card at any time from the client area.
  4. Admin level users with the necessary permissions can also perform card updates from the admin area.
  5. Customers never leave your WHMCS installation during checkout or updating their card.
  6. Personal card information is submitted directly to Accept.js and is never stored in your local WHMCS installation.
  7. The Accept.js API is used for obtaining transaction information.
  8. 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.

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.

To migrate all of your credit card processing to Accept.js, follow the steps below:

  1. Navigate to Setup > Payments > Payment Gateways
  2. Ensure the Accept.js module has been activated
  3. Select the Deactivate link for your previous merchant gateway provider
  4. When prompted to choose a replacement gateway to switch users of the previous gateway module to, select Accept.js
  5. Click OK to complete the process
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.