Difference between revisions of "Pay Methods"

From WHMCS Documentation

(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...")
 
 
(21 intermediate revisions by 5 users not shown)
Line 1: Line 1:
==Introduction==
+
In WHMCS, a Pay Method is a payment method that belongs to a client. It can represent a credit card or a bank account. Clients can choose any of their available payment methods during checkout for new orders and for payment of invoices. Each individual payment method has an associated '''[[Payment Gateways|Payment Gateway]]''' and can also have a different associated billing address.
  
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.
+
<div class="docs-alert-info">
 +
The following settings in the '''[[Security Tab|Security]]''' tab at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > General Settings''' affect payment method behavior:
  
Client can choose any of their available Pay Methods during checkout both for new orders and payment of invoices.
+
* '''Allow Client Pay Method Removal'''
 
+
* '''Delete Encrypted Credit Card Data'''
Each Pay Method can also have a different billing address associated with it if required.
+
* '''Delete Encrypted Bank Account Data'''
 +
</div>
  
 
==Default Pay Method==
 
==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.
+
Clients must always have a default payment method. This is the payment method that all new automatic recurring payment attempts use by default.
  
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.
+
In some scenarios, the default payment method may not be valid for a specific invoice (for example, when the default payment method is tokenized with a specific payment gateway and the invoice's payment method uses a different payment gateway). If this occurs, the system uses the client's first applicable payment method.
  
<div class="docs-alert-info">'''Please Note:''' At this time, it is not possible to set a different default Pay Method on a per service basis, although this functionality is planned to be delivered in a future update.</div>
+
<div class="docs-alert-warning">
 +
* You cannot set a different default payment method on a per-service basis.
 +
* Changing the default payment method will not change the payment method that existing unpaid invoices use.
 +
</div>
  
 
==Managing Pay Methods==
 
==Managing Pay Methods==
Line 19: Line 24:
 
===Admin Area===
 
===Admin Area===
  
Text goes here...
+
You can manage client payment methods from the '''[[Clients:Summary_Tab|Summary]]''' tab of the client profile.
 +
 
 +
[[File:Paymethod-admin-area-v3.png]]
  
 
===Client Area===
 
===Client Area===
  
Text goes here...
+
Clients can view and manage payment method at '''Billing > Payment Methods''' in the Client Area.
 
 
==Related Settings==
 
  
* Allow Client CC Removal - Text goes here...
+
[[File:payment-methods.png|400px]]
  
* Delete Encrypted Credit Card Data - Text goes here...
+
Clients can view all of their saved payment methods, update their descriptions and expiry dates, delete them (if you enable this), and change the default payment method for automated recurring payment attempts.
  
===Tokenization of Pay Methods==
+
<div class="docs-alert-warning">
 +
If you use tokenized and non-tokenized payment gateways, customers can choose the desired payment method when adding one via the Client Area. This determines whether to store the card locally, encrypted in the WHMCS database, or remotely with the tokenized payment gateway.
 +
</div>
  
====Introduction====
+
==Processing Payments==
  
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...
+
The system attempts recurring charges for capture automatically using the client's default payment method. If no payment method exist for a client, the client will receive an email informing them that the system could not attempt an automated payment and that they must log in and pay the invoice manually.
  
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.
+
=== Changing Payment Methods ===
  
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.
+
To use a different card, clients can log in to the Client Area and pay the unpaid invoice manually.
  
====Migration====
+
=== Capturing Payment Using a Stored Payment Method ===
  
Text goes here...
+
Admins can also attempt to capture payment at any time using a stored payment method.  
  
====Enforcing Use====
+
To do this:
  
Text goes here...
+
# Go to the desired invoice in the [[Admin Area]].
 +
# Click '''Attempt Capture'''. If '''Attempt Capture''' does not appear or is disabled, check the invoice's assigned payment method in the '''Options''' tab.
 +
# Choose the desired payment method to use.
 +
# Optionally, enter the CVV number for the card.
 +
# Click '''Attempt Capture''' to attempt the payment.

Latest revision as of 12:55, 19 December 2023

In WHMCS, a Pay Method is a payment method that belongs to a client. It can represent a credit card or a bank account. Clients can choose any of their available payment methods during checkout for new orders and for payment of invoices. Each individual payment method has an associated Payment Gateway and can also have a different associated billing address.

The following settings in the Security tab at Configuration () > System Settings > General Settings affect payment method behavior:

  • Allow Client Pay Method Removal
  • Delete Encrypted Credit Card Data
  • Delete Encrypted Bank Account Data

Default Pay Method

Clients must always have a default payment method. This is the payment method that all new automatic recurring payment attempts use by default.

In some scenarios, the default payment method may not be valid for a specific invoice (for example, when the default payment method is tokenized with a specific payment gateway and the invoice's payment method uses a different payment gateway). If this occurs, the system uses the client's first applicable payment method.

  • You cannot set a different default payment method on a per-service basis.
  • Changing the default payment method will not change the payment method that existing unpaid invoices use.

Managing Pay Methods

Admin Area

You can manage client payment methods from the Summary tab of the client profile.

Paymethod-admin-area-v3.png

Client Area

Clients can view and manage payment method at Billing > Payment Methods in the Client Area.

Payment-methods.png

Clients can view all of their saved payment methods, update their descriptions and expiry dates, delete them (if you enable this), and change the default payment method for automated recurring payment attempts.

If you use tokenized and non-tokenized payment gateways, customers can choose the desired payment method when adding one via the Client Area. This determines whether to store the card locally, encrypted in the WHMCS database, or remotely with the tokenized payment gateway.

Processing Payments

The system attempts recurring charges for capture automatically using the client's default payment method. If no payment method exist for a client, the client will receive an email informing them that the system could not attempt an automated payment and that they must log in and pay the invoice manually.

Changing Payment Methods

To use a different card, clients can log in to the Client Area and pay the unpaid invoice manually.

Capturing Payment Using a Stored Payment Method

Admins can also attempt to capture payment at any time using a stored payment method.

To do this:

  1. Go to the desired invoice in the Admin Area.
  2. Click Attempt Capture. If Attempt Capture does not appear or is disabled, check the invoice's assigned payment method in the Options tab.
  3. Choose the desired payment method to use.
  4. Optionally, enter the CVV number for the card.
  5. Click Attempt Capture to attempt the payment.