Difference between revisions of "PayPal"

From WHMCS Documentation
 
(13 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
{{gateways
+
According to PayPal® research, 49% of PayPal users abandon their purchases if PayPal isn’t a payment option. WHMCS’s supported payment gateway modules include several options for accepting payments through PayPal, helping you maximize your business and offer the options that your customers want most.
−
| onetime = yes
 
−
| recurring = yes
 
−
| refunds = yes
 
−
| reversals = yes
 
−
}}
 
−
 
 
−
[http://paypal.com PayPal] is one of the most popular and widely recognised online payment processors.
 
−
 
 
−
==Setup==
 
−
<html><a href="https://www.youtube.com/watch?v=L0B6KbPaGKE&hd=1" class="docs-video-tutorial"><em>Watch the video tutorial for this feature</em><span>&nbsp;<img src="https://assets.whmcs.com/icons/youtube.png">&nbsp;</span></a></html>
 
−
 
 
−
Begin by activating the payment gateway under '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > Payment Gateways''' or, prior to WHMCS 8.0, '''Setup > Payments > Payment Gateways'''. Choose PayPal from the Available Gateways dropdown.
 
−
 
 
−
Once activated, you can then enter the configuration details explained below. By default clients can chose between one-time and subscriptions payments and enter their own billing details on the PayPal site, the following options allow this behaviour to be changed.
 
−
 
 
−
===PayPal Email===
 
−
Enter the email address associated with your PayPal account, this is the only required field and all others are optional.
 
−
If you have more than one email address associated with your PayPal account, you may add as many of those as you like, comma-delimited. You must next configure [[#Instant_Payment_Notification_.28IPN.29|Instant Payment Notifications]].
 
−
 
 
−
===Force One Time Payments===
 
−
When ticked clients will only be able to make one-time payments (subscriptions disabled). For recurring services they will be required to login and pay each invoice.
 
−
 
 
−
===Force Subscriptions===
 
−
When enabled clients will only be able to make subscription payments when applicable (one-time payments disabled). This means future payments will be sent automatically without the need for manual intervention. There are some [[#PayPal_Subscriptions.2FRecurring_Billing|caveats explained below]].
 
−
 
 
−
===Require Shipping Address===
 
−
Ticking this option will require clients to provide a shipping address on the PayPal website and will be associated with their payment at PayPal, useful when selling physical products and for PayPal's Seller Protection.
 
−
 
 
−
===Client Address Matching===
 
−
The details the client provides in WHMCS upon ordering (name, address, phone number etc) will be used associated with their payment at PayPal, they will not be given the opportunity to provide different details on the PayPal website. Clients can update their profile via the WHMCS client area, your staff can use the Profile tab.
 
−
 
 
−
===API Fields===
 
−
Used for issuing refunds within WHMCS (saving the need to login at PayPal).
 
−
 
 
−
These credentials can be accessed with the '''API Credentials''' tool found in the '''Tools > All Tools''' section of the PayPal Business dashboard. Alternatively, they can be accessed directly by navigating to https://www.paypal.com/businessmanage/credentials/apiAccess
 
−
 
 
−
For more information refer to [[#Automated_Refunds|Automated Refunds]]
 
−
 
 
−
===Sandbox Mode===
 
−
Ticking the Sandbox Mode checkbox will make the module connect to PayPal's sandbox environment. In order to use this you will need to create a Sandbox account at https://developer.paypal.com/
 
 
   
 
   
−
If your sandbox credentials differ from that of your live account then the PayPal Email, API Username, and API Password settings will need to be updated to reflect this. Once testing has concluded you will want to replace these settings with those of your live account.
+
You can enable payment gateways, including the PayPal options below, at '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > [[Apps_and_Integrations|Apps & Integrations]]''' (in WHMCS 8.6 and later) or '''Configuration (<i class="fa fa-wrench" aria-hidden="true"></i>) > System Settings > [[Payment Gateways]]''' (in WHMCS 8.5 and earlier).
−
 
 
−
==Instant Payment Notification (IPN)==
 
−
 
 
−
[[File:paypalipn2.png|thumb|PayPal IPN Setup]]
 
−
 
 
−
For PayPal invoices to be automatically marked paid when you receive a payment you need to enable IPN inside your PayPal account.
 
−
 
 
−
# Navigate to '''Profile > Profile and Settings > My Selling Tools > Instant Payment Notifications '''
 
−
# Click the '''Choose IPN Settings''' button
 
−
# Enter in your WHMCS System URL eg. https://www.yourdomain.com/whmcspath/
 
−
# Select the '''Enabled''' option
 
−
# Click '''Save'''
 
−
 
 
−
===Charset Configuration===
 
−
 
 
−
[[File:paypalcharset.png|thumb|PayPal Charset Configuration]]
 
−
 
 
−
PayPal defaults the charset used for most accounts to windows-1252. Whilst this is acceptable and will not cause an issue for most users, on occasion, accented characters can be returned incorrectly through the IPN causing the IPN Handshake Invalid message. Setting the charset in your PayPal account to match your WHMCS installation is a recommended setting to ensure this issue does not occur. The default value is '''UTF-8'''.
 
−
 
 
−
This is done via the '''Language Encoding''' page https://www.paypal.com/cgi-bin/customerprofileweb?cmd=_profile-language-encoding. Once here, click on '''More Options''' and choose your charset from the dropdown and ensure the radio option is set to '''Yes'''. Click on '''Save''' and your configuration is completed.
 
−
 
 
−
==PayPal Subscriptions/Recurring Billing==
 
−
 
 
−
Unless disabled in the PayPal gateway config, when a user views an invoice for a recurring product or service they will be shown a PayPal Subscribe button.  This allows the user to subscribe so that their payment for that product or service is sent to you automatically each month/quarter/etc... and automatically applied to the appropriate renewal invoices by WHMCS.
 
−
 
 
−
There are three conditions that must be met for the PayPal subscribe button to appear:
 
−
 
 
−
# The invoice's Due Date must be in the future
 
−
# The invoice must contain at least 1 recurring product (ie. domains, billable items or addons on their own won't create subscriptions)
 
−
# The 'Force One Time Payments' option is UNticked on the payment gateway configuration page.
 
−
 
 
−
If an invoice contains both a product, and addons or domains, then any which '''match the products''' billing cycle will '''also be included''' as part of the subscription.  For example, if an invoice contained a product, an addon & a domain, all of which recur on an annual basis, then the PayPal subscription that gets created by WHMCS would be for the total amount of all 3 items so that the '''subscription would cover everything''' and pay the renewal invoice in full automatically.  What isn't possible however is to create a subscription that has different amounts recurring on different recurring terms, ie. $x Monthly + $Y Annually.  PayPal doesn't offer an option for that at the current time.
 
−
 
 
−
===Customising Invoice Emails for Subscriptions===
 
−
 
 
−
When a subscription is created, the Subscription ID number that gets issued by PayPal is stored by WHMCS in the Subscription ID field for the product. Similarly when a subscription is cancelled the Subscription ID gets removed again. Therefore it is possible to use that ID value to determine if a subscription exists and therefore customise the text shown to the customer in the invoice related emails based on that.
 
−
 
 
−
For example, one might customise the "Invoice Created" email template to show different instructions to the customer if a subscription exists (meaning no manual action is required), compared with if one doesn't (meaning the client needs to login and pay the invoice manually), for example:
 
−
 
 
−
{if $invoice_subscription_id}
 
−
As you have a PayPal Subscription setup, payment will be taken automatically within the
 
−
next few days. Please ensure you have enough funds in your PayPal account to cover it.
 
−
{else}
 
−
You can login to your client area to view and pay the invoice at {$invoice_link}
 
−
{/if}
 
−
 
 
−
===Automatic Subscription Management===
 
 
   
 
   
−
If the Automatic Subscription Management feature is enabled on the installation, then WHMCS will attempt to automatically cancel PayPal subscriptions where applicable.
+
== PayPal Gateway Comparison ==
 
   
 
   
−
For details regarding the Automatic Subscription Management feature please refer to the [[Invoice_Tab#Automatic_Subscription_Management|Configuration]] section of the documentation.
+
Each PayPal payment gateway includes features to help you accept and manage payments:
−
 
+
−
==Automated Refunds==
+
<table class="table table-striped table-condensed">
−
 
+
    <tr>
−
You can issue refunds for PayPal payments directly from within WHMCS.  Before you can do this however, you need to setup PayPal API access.  The steps for doing this are as follows:
+
      <th>Feature</th>
−
 
+
      <th>PayPal Payments</th>
−
[[File:PP_API1_rev2.png‎|thumb|PayPal API Step 1]]
+
      <th>PayPal Card Payments</th>
−
[[File:PP_API2_rev2.png‎|thumb|PayPal API Step 2]]
+
      <th>PayPal Checkout</th>
−
*Login to PayPal
+
      <th>PayPal Basic</th>
−
*Go to '''Tools > All Tools > API credentials > NVP/SOAP API integration (Classic)'''
+
      <th>PayPal Pro Reference Payments</th>
−
*Click '''Manage API Credentials''' - under the "NVP/SOAP API integration (Classic)" heading
+
      <th>PayPal Website Payments Pro</th>
−
* From there, you can generate a new set of credentials, view the current credentials, or remove them and create a new set
+
      <th>PayFlow Pro</th>
−
*Copy the username, password and signature that get provided and then click Done
+
    </tr>
−
*Enter the details from the previous step into the WHMCS Payment Gateways config screen where requested
+
    <tr>
−
 
+
      <td>Recommended for New PayPal Merchants</td>
−
You will now be able to enter a refund and have it sent from PayPal at the same time from within the WHMCS admin area invoice management screen.
+
      <td>✓</td><td>✓</td><td>✖️</td><td>✖️</td><td>✖️</td><td>✖️</td><td>✖️</td>
−
 
+
    </tr>
−
==Error Messages==
+
    <tr>
−
===Invalid Receiver Email===
+
      <td>Gateway Type</td>
−
WHMCS validates the payment receiver email value against the details specified under Setup > Payments > Payment Gateways so this error means the two do not match. If multiple PayPal accounts are used to receive payment, or a single PayPal account has multiple email addresses associated with it ,they must all be listed in a comma separated list eg. email1@mycompany.com,email2@mycompany.com.
+
      <td>''Token''</td><td>''Token''</td><td>''Third-Party''</td><td>''Third-Party''</td><td>''Token''</td><td>''Merchant''</td><td>''Merchant''</td>
−
 
+
    </tr>
−
The first email you specify will then be the email used for new payments, but any email in the field will be accepted as an invoice payment.
+
    <tr>
−
 
+
      <td>One-Time<br/>Payments</td>
−
===Not Supported===
+
      <td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td>
−
This Result will appear when an action occurs that does not require any action on WHMCS' behalf, for example a txn_type value of "subscr_failed" mean a subscription payment failed or "subscr_eot" means End of Subscription Term. You will see these entries under normal operation and is not a problem.
+
    </tr>
−
 
+
    <tr>
−
===Unrecognised Currency===
+
      <td>Recurring<br/>Payments</td>
−
This error in the Gateway Log means an invalid currency code has been entered under Setup > Payments > Currencies. A currency code must use the ISO 4217 standard as explained on the [[Currencies]] page. For example EURO is not valid, but EUR is valid.
+
      <td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td>
−
 
+
    </tr>
−
This could also be caused by a blank space at the beginning or end of the currency code, so edit the code to ensure there are none.
+
    <tr>
−
 
+
      <td>PayPal<br/>Subscriptions</td>
−
===IPN Handshake Invalid===
+
      <td>✖️</td><td>✖️</td><td>✓</td><td>✓</td><td>✖️</td><td>✖️</td><td>✖️</td>
−
Getting this message in your Gateway Log would mean that WHMCS is unable to verify that the callback occurring has come from PayPal.
+
    </tr>
−
This is to stop any false payments being applied to your account, however, on occasion, some valid payments can generate this error.
+
    <tr>
−
Follow the instructions above for setting the [[#Charset_Configuration|Charset]] of your IPN to stop this.
+
      <td>Refunds</td>
−
 
+
      <td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td>
−
===IPN Handshake Error===
+
    </tr>
−
Getting this message in your Gateway Log indicates that whilst the IPN from PayPal was received, WHMCS was unable to verify the IPN data. The verification process involves connecting to PayPal's callback verification service at https://www.paypal.com/cgi-bin/webscr. This error will be observed if that connection fails. It can fail if the cURL connection made does not use the required protocols, transport Layer Security version 1.2 (TLS 1.2) and Hypertext Transfer Protocol version 1.1 (HTTP/1.1) are mandatory for communication with PayPal. You can test whether or not your server is connecting with the required protocols using cURL from your servers command line, for example:
+
    <tr>
−
 
+
      <td>Reversals<br/>(in WHMCS)</td>
−
<source lang="php">curl https://tlstest.paypal.com</source>
+
      <td>✓</td><td>✓</td><td>✖️</td><td>✓</td><td>✖️</td><td>✖️</td><td>✖️</td>
−
 
+
    </tr>
−
If successful, this response will be shown:
+
    <tr>
−
 
+
      <td>Disputes<br/>(in WHMCS)</td>
−
<source lang="php">PayPal_Connection_OK</source>
+
      <td>✓</td><td>✓</td><td>✓</td><td>✖️</td><td>✖️</td><td>✖️</td><td>✖️</td>
−
 
+
    </tr>
−
If unsuccessful, this error will be shown:
+
    <tr>
−
 
+
      <td>3D Secure</td>
−
<source lang="php">ERROR! Connection is using TLS version lesser than 1.2. Please use TLS1.2</source>
+
      <td>N/A</td><td>✓</td><td>✖️</td><td>✖️</td><td>✓</td><td>✓</td><td>✓</td>
−
 
+
    </tr>
−
The WHMCS PayPal module does not specify a particular cryptographic protocol when communicating with PayPal. This means that cURL on your server should automatically negotiate the best protocol to use. Should you encounter the error above, it means your server is trying to negotiate a secure connection using one of the cryptographic protocols that PayPal no longer support. In that situation it would be necessary to work with your system administrator to ensure TLS 1.2 or greater is the default protocol on the server.
+
    <tr>
−
 
+
      <td>View Balances<br/>(in WHMCS)</td>
−
If the cURL test response is successful, it would be necessary to check a successful connection to PayPal's callback verification service at https://www.paypal.com/cgi-bin/webscr can be made.  
+
      <td>✓</td><td>✓</td><td>✖️</td><td>✖️</td><td>✓</td><td>✓</td><td>✓</td>
−
 
+
    </tr>
−
This can again be checked using cURL from your servers command line, for example:
+
</table>
−
 
+
−
<source lang="php">curl -I https://www.paypal.com/cgi-bin/webscr</source>
+
== Our PayPal Gateways ==
−
 
+
−
Any errors shown can again be referred to your server administrator to review and resolve.  
+
We support the following PayPal payment gateways and ship them by default for all supported installations:
−
 
+
−
===Things don't appear to be working at the moment===
+
=== PayPal Payments ===
−
Upon reaching the PayPal website, the error is displayed '''Things don't appear to be working at the moment. Please try again later'''.
+
−
 
+
<div class="docs-alert-info">
−
This message indicates invalid details being sent to PayPal. It could be invalid client details (eg. address, postcode) or a misconfiguration in the WHMCS settings (eg. an invalid currency code - it should be a three letter ISO-4217 format).
+
We '''strongly''' recommend the PayPal Payments module to all new PayPal merchants. For steps to activate and configure '''PayPal Payments''', see [https://help.whmcs.com/a/1782848 Start Using PayPal Payments].
−
 
+
</div>
−
Return to the client area invoice, view the page source and examine the PayPal payment button HTML code. Look for any variables which could be invalid. Then edit the client's profile or system settings to correct it.
+
−
 
+
'''PayPal Payments''' uses PayPal’s latest secure tokenization system and lets your clients make payments with PayPal, including credit and debit card transactions. It ensures the security of your customers’ stored payment details with merchant-level vaulting through PayPal Vault, now available for PayPal merchant accounts in [[PayPal_Payments#Vaulting|PayPal-supported countries]]. It also supports [[Disputes|disputes]], and you can view your current merchant account balance at '''Billing > [[Transactions]]'''.
−
 
+
−
{{modules}}
+
When you activate '''PayPal Payments''', the system also activates '''PayPal Card Payments''' (below). This module augments PayPal Payments, allowing you the option to visually separate the PayPal checkout experience from credit and debit card payments.
 +
 +
For more information, see [[PayPal Payments]].
 +
 +
=== PayPal Card Payments ===
 +
 +
'''PayPal Card Payments''' works with the '''PayPal Payments''' module to add an unbranded credit and debit card option that uses PayPal Advanced Checkout. When you activate '''PayPal Payments''', the system automatically activates '''PayPal Card Payments''' with it, with both modules using the account details that you configure for '''PayPal Payments'''.
 +
 +
Display '''PayPal Card Payments''' on your Client Area order form to visually separate the PayPal checkout experience from credit and debit card payments. Like '''PayPal Payments''', '''PayPal Card Payments''' also supports [Disputes|disputes]], and you can view your current merchant account balance at '''Billing > [[Transactions]]'''.
 +
 +
For more information, see [[PayPal Card Payments]].
 +
 +
=== PayPal Checkout ===
 +
 +
'''PayPal Checkout''' gives your customers a simplified and secure checkout experience, with the option to use '''Express Checkout''' to complete the transaction. '''Express Checkout''' appears automatically as a payment option for any product that uses a ''One-Time'', ''Biennial'', or ''Triennial'' billing cycle.
 +
 +
'''PayPal Checkout''' allows you to accept one-time and recurring payments through PayPal (including PayPal Subscriptions), process refunds, and handle [[Disputes|disputes]] from within WHMCS.
 +
 +
For more information, see [[PayPal Checkout]].
 +
 +
=== PayPal Basic ===
 +
 +
'''PayPal Basic''' allows you to accept one-time and recurring payments through PayPal (including PayPal Subscriptions), process refunds, and handle payment reversals. In WHMCS 8.2 and later, you can view payment gateway balances for '''PayPal Basic''' at '''Billing > [[Transactions]]''' in the WHMCS Admin Area. This lets you check your financial details sooner and stay aware of trends and changes.
 +
 +
For more information, see [[PayPal Basic]].
 +
 +
=== PayPal Pro Reference Payments ===
 +
 +
'''PayPal Pro Reference Payments''' allows you to store cards with a secure tokenization system for better PCI compliance. It can process one-time and recurring payments and send refunds.
 +
 +
This module does '''not''' support adding or updating card data via the Admin Area. Instead, you can do this by paying an invoice on behalf of a client.
 +
 +
For more information, see [[Payflow_Pro|PayPal Pro Reference Payments]].
 +
 +
=== PayPal Website Payments Pro ===
 +
 +
'''PayPal Website Payments Pro''' allows you to accept one-time and recurring payments with locally-stored credit cards, process refunds, and handle payment reversals.
 +
 +
For more information, see [[PayPal Website Payments Pro]].
 +
 +
=== PayFlow Pro ===
 +
 +
'''Payflow Pro''' includes one-time and recurring payments with locally-stored credit cards and process refunds. You will need to enable the PayFlow Pro API in order to use this payment gateway.
 +
 +
For more information, see [[Payflow Pro]].

Latest revision as of 20:15, 22 March 2024

According to PayPal® research, 49% of PayPal users abandon their purchases if PayPal isn’t a payment option. WHMCS’s supported payment gateway modules include several options for accepting payments through PayPal, helping you maximize your business and offer the options that your customers want most.

You can enable payment gateways, including the PayPal options below, at Configuration () > Apps & Integrations (in WHMCS 8.6 and later) or Configuration () > System Settings > Payment Gateways (in WHMCS 8.5 and earlier).

PayPal Gateway Comparison

Each PayPal payment gateway includes features to help you accept and manage payments:

Feature PayPal Payments PayPal Card Payments PayPal Checkout PayPal Basic PayPal Pro Reference Payments PayPal Website Payments Pro PayFlow Pro
Recommended for New PayPal Merchants ✓✓✖️✖️✖️✖️✖️
Gateway Type TokenTokenThird-PartyThird-PartyTokenMerchantMerchant
One-Time
Payments		 ✓✓✓✓✓✓✓
Recurring
Payments		 ✓✓✓✓✓✓✓
PayPal
Subscriptions		 ✖️✖️✓✓✖️✖️✖️
Refunds ✓✓✓✓✓✓✓
Reversals
(in WHMCS)		 ✓✓✖️✓✖️✖️✖️
Disputes
(in WHMCS)		 ✓✓✓✖️✖️✖️✖️
3D Secure N/A✓✖️✖️✓✓✓
View Balances
(in WHMCS)		 ✓✓✖️✖️✓✓✓

Our PayPal Gateways

We support the following PayPal payment gateways and ship them by default for all supported installations:

PayPal Payments

We strongly recommend the PayPal Payments module to all new PayPal merchants. For steps to activate and configure PayPal Payments, see Start Using PayPal Payments.

PayPal Payments uses PayPal’s latest secure tokenization system and lets your clients make payments with PayPal, including credit and debit card transactions. It ensures the security of your customers’ stored payment details with merchant-level vaulting through PayPal Vault, now available for PayPal merchant accounts in PayPal-supported countries. It also supports disputes, and you can view your current merchant account balance at Billing > Transactions.

When you activate PayPal Payments, the system also activates PayPal Card Payments (below). This module augments PayPal Payments, allowing you the option to visually separate the PayPal checkout experience from credit and debit card payments.

For more information, see PayPal Payments.

PayPal Card Payments

PayPal Card Payments works with the PayPal Payments module to add an unbranded credit and debit card option that uses PayPal Advanced Checkout. When you activate PayPal Payments, the system automatically activates PayPal Card Payments with it, with both modules using the account details that you configure for PayPal Payments.

Display PayPal Card Payments on your Client Area order form to visually separate the PayPal checkout experience from credit and debit card payments. Like PayPal Payments, PayPal Card Payments also supports [Disputes|disputes]], and you can view your current merchant account balance at Billing > Transactions.

For more information, see PayPal Card Payments.

PayPal Checkout

PayPal Checkout gives your customers a simplified and secure checkout experience, with the option to use Express Checkout to complete the transaction. Express Checkout appears automatically as a payment option for any product that uses a One-Time, Biennial, or Triennial billing cycle.

PayPal Checkout allows you to accept one-time and recurring payments through PayPal (including PayPal Subscriptions), process refunds, and handle disputes from within WHMCS.

For more information, see PayPal Checkout.

PayPal Basic

PayPal Basic allows you to accept one-time and recurring payments through PayPal (including PayPal Subscriptions), process refunds, and handle payment reversals. In WHMCS 8.2 and later, you can view payment gateway balances for PayPal Basic at Billing > Transactions in the WHMCS Admin Area. This lets you check your financial details sooner and stay aware of trends and changes.

For more information, see PayPal Basic.

PayPal Pro Reference Payments

PayPal Pro Reference Payments allows you to store cards with a secure tokenization system for better PCI compliance. It can process one-time and recurring payments and send refunds.

This module does not support adding or updating card data via the Admin Area. Instead, you can do this by paying an invoice on behalf of a client.

For more information, see PayPal Pro Reference Payments.

PayPal Website Payments Pro

PayPal Website Payments Pro allows you to accept one-time and recurring payments with locally-stored credit cards, process refunds, and handle payment reversals.

For more information, see PayPal Website Payments Pro.

PayFlow Pro

Payflow Pro includes one-time and recurring payments with locally-stored credit cards and process refunds. You will need to enable the PayFlow Pro API in order to use this payment gateway.

For more information, see Payflow Pro.

Retrieved from "http://3.17.75.209/index.php?title=PayPal&oldid=34499"