Difference between revisions of "Pay Methods"
(Created page with "==Introduction== In WHMCS, a Pay Method is a method of payment belonging to a client. A Pay Method can represent a credit card or a bank account and a client can have multipl...") |
|||
| Line 31: | Line 31: | ||
* Delete Encrypted Credit Card Data - Text goes here... | * Delete Encrypted Credit Card Data - Text goes here... | ||
| − | + | ==Tokenization of Pay Methods== | |
| − | + | ===Introduction=== | |
Tokenization is a process in which sensitive payment details are stored remotely by a payment gateway processor. This is intended to reduce the security burden and limit the liability on you as a business. Examples of payment gateways that support tokenization include Authorize.net, Stripe, Quantum Gateway, etc... | Tokenization is a process in which sensitive payment details are stored remotely by a payment gateway processor. This is intended to reduce the security burden and limit the liability on you as a business. Examples of payment gateways that support tokenization include Authorize.net, Stripe, Quantum Gateway, etc... | ||
| Line 41: | Line 41: | ||
In such scenarios, the ability to use a given Pay Method with other payment gateways will be restricted. This will become apparent during checkout when switching between payment methods (also referred to as payment gateways) and the list of available Pay Methods changing. | In such scenarios, the ability to use a given Pay Method with other payment gateways will be restricted. This will become apparent during checkout when switching between payment methods (also referred to as payment gateways) and the list of available Pay Methods changing. | ||
| − | === | + | ===Tokenization Migration=== |
Text goes here... | Text goes here... | ||
| − | + | ===Enforcing Tokenization=== | |
Text goes here... | Text goes here... | ||
Revision as of 10:23, 22 July 2019
Contents
Introduction
In WHMCS, a Pay Method is a method of payment belonging to a client. A Pay Method can represent a credit card or a bank account and a client can have multiple Pay Methods associated with their account.
Client can choose any of their available Pay Methods during checkout both for new orders and payment of invoices.
Each Pay Method can also have a different billing address associated with it if required.
Default Pay Method
There must always be a default Pay Method and this is the Pay Method that is used by default for all automatic recurring payment attempts.
In certain conditions, the default Pay Method may not be applicable for a given invoice, for example when the default Pay Method is tokenized with a specific payment gateway and the invoices payment method is a different gateway. In this scenario, the first applicable Pay Method in order of display order is used.
Managing Pay Methods
Admin Area
Text goes here...
Client Area
Text goes here...
Related Settings
- Allow Client CC Removal - Text goes here...
- Delete Encrypted Credit Card Data - Text goes here...
Tokenization of Pay Methods
Introduction
Tokenization is a process in which sensitive payment details are stored remotely by a payment gateway processor. This is intended to reduce the security burden and limit the liability on you as a business. Examples of payment gateways that support tokenization include Authorize.net, Stripe, Quantum Gateway, etc...
When a tokenization payment gateway is in use, the details for a Pay Method are stored remotely by a given payment gateway and therefore the Pay Method is restricted for use only by the given payment gateway.
In such scenarios, the ability to use a given Pay Method with other payment gateways will be restricted. This will become apparent during checkout when switching between payment methods (also referred to as payment gateways) and the list of available Pay Methods changing.
Tokenization Migration
Text goes here...
Enforcing Tokenization
Text goes here...