PayPal transactions can be tested in the PayPal Sandbox before accepting live payments on your site. See the PayPal sandbox testing guide for more details.
Once the WooCommerce PayPal Payments plugin has been installed and activated, it needs to be connected to your PayPal account.
The integrated onboarding connects a PayPal account via login credentials (email and password) without the need for API credentials. The onboarding automatically creates a new REST application in the PayPal developer site, registers the webhooks, and enables relevant features such as Vaulting. If desired, the account can also be connected manually.
The setup process is thoroughly explained in the video below. Keep in mind that the settings pages in the latest version of PayPal Payments have been updated for improved user experience, so they may differ from what is shown in the video.
If preferred, the PayPal account can also be connected manually with API credentials.
Clicking Toggle to manual credential input
reveals the input fields. A REST application must be created on the PayPal developer site to retrieve the API credentials needed to connect the account. The steps below describe how to find the required PayPal Merchant ID, Client ID, and Secret Key.
PayPal Payments requires the Merchant ID, a unique ID for every PayPal account. The Merchant ID helps to protect your identity.
When using PayPal Payments your Merchant ID will be used instead of your primary email address to create the payment buttons. This way your email address won’t be visible to spammers.
Here’s how to locate the Merchant ID for your PayPal business account:
More information and instructions for personal PayPal accounts are available here: How do I find my Secure Merchant ID on my PayPal account?
Sandbox accounts can also view the Merchant ID from the same page on the corresponding sandbox.paypal.com website, or from the PayPal developer site (the Merchant ID may be listed as Account ID for sandbox accounts on the PayPal developer site).
The Client ID & Secret Key can only be obtained from the PayPal Developer Website.
This video explains how to create a REST App on the PayPal developer website. Please note PayPal is continuously improving the developer website and experience.
The plugin configuration is explained in the sections below.
The Connection tab displays all the necessary information for the plugin to connect with your PayPal account. This includes your API credentials, activation status for advanced features, webhook status, and more.
After following the steps outlined in Connect a PayPal account, the REST API credentials for the connected PayPal account are displayed in this section.
Toggle the Sandbox checkbox to switch from live to sandbox accounts for testing purposes.
To connect a different PayPal account, click Disconnect Account and connect your account via the onboarding wizard.
The Advanced feature availability & sign-up section displays the activation status for advanced features for the connected PayPal account.
Advanced features could be signed up for from this page if the account was not already enabled.
The integration configuration includes the configuration for the invoice prefix and logging.
When using a PayPal seller account on multiple websites, a distinct prefix should separate those installations, as PayPal only accepts unique invoice numbers by default.
Enabling Logging
helps to diagnose issues when transactions fail or for general troubleshooting purposes.
PayPal Payments uses webhooks to communicate events with and from PayPal, replacing the previous reliance on IPN. The onboarding wizard will automatically configure necessary webhooks. To manually connect REST API credentials, manual webhook registration is required through the Webhooks Status section, which allows webhook simulation and resubscription without visiting the PayPal developer site.
For optimal performance and to resolve potential issues with WooCommerce order status or PayPal refunds, it’s recommended to click the Resubscribe button in the Webhooks Status section. This will ensure that the plugin is using the latest webhooks. After resubscribing, run a Simulate test to verify the successful receipt of the webhooks. If the simulation results in an error, follow the troubleshooting steps outlined.
Webhooks are an essential component in the functioning of the plugin. Especially for Alternative Payment Methods, as the buyer’s payment is only captured after receiving a webhook confirmation.
PayPal Payments stores settings and other related data in your database. However, there may be times when you wish to uninstall the plugin and remove all related data.
By default, uninstalling the plugin will not delete these settings. Your configurations will be saved in case you decide to reinstall the plugin in the future.
PayPal Payments provides an option for removing all plugin-related data upon uninstallation by checking the Remove PayPal Payments data from Database on uninstall setting.
Additionally, it is possible to reset the plugin to its initial state without uninstalling the plugin:
The Clear now button from the Remove PayPal Payments data from Database setting will delete all current data related to the plugin and return it to the state it was in immediately after the initial installation.
Be aware that this action is irreversible; once clicked, all your saved settings will be lost, and the plugin will revert to its default configuration.
The button preview serves as a tool to help you style the buttons for your shop, however, the payment buttons displayed to customers may differ based on factors such as their location, eligibility, or the button configuration.
PayPal Payments implements the PayPal Smart Button styling options as demonstrated in this video:
The Pay Later tab provides a configuration interface for the Pay Later option, which is only available to customers in eligible countries. In this section, you can enable or disable the Pay Later button and Pay Later messaging and customize their appearance for individual locations.
Pay Later messages are dynamic, enabling you to show your customers their specific Pay Later offer, based on the contents of their shopping cart.
The messaging can be configured in the text format with these settings
Pay Later messaging customization options are explained here.
Permission required
Get PayPal account permission to use Advanced Card Processing payment functionality by following the guide here.
After completing the onboarding process for Advanced Card Payments, follow these steps to navigate to the Advanced Card Processing settings:
The following settings can be configured for Advanced Card Processing:
Read Advanced Card Processing – Advanced Credit and Debit Card payments for more information about advanced card payments.
Permission required
Get PayPal account permission to use OXXO payment functionality by contacting PayPal at: (+52) 800-925-0304
This gateway only appears for merchants with their store location in Mexico.
Permission required
Get PayPal account permission to use Pay upon Invoice payment functionality by following the guide here.
Read Pay upon Invoice – Rechnungskauf for more information about the Pay upon Invoice requirements and configuration. After completing the onboarding process for Pay upon Invoice, follow these steps to navigate to the Pay upon Invoice settings:
The customer experience:
This process reduces the amount of data entry required by the customer, streamlining the checkout experience.
*PayPal obtains order authorization for an amount up to 150% of the subtotal to account for taxes and shipping costs, capped at $75. The original subtotal is used if no taxes or shipping costs apply, otherwise the updated total is used.
By default, PayPal does not transmit the buyer’s phone number from their PayPal account to the Checkout page.
To enable this functionality, log into your PayPal account and navigate here for Live accounts and here for Sandbox accounts: Account Settings > Website payments > Website preferences
Scroll down to the section Contact telephone number and set it either to On (optional field) or On (required field) depending on your Checkout page configuration.
By default, WooCommerce is configured to handle separate billing and shipping details for your orders.
When utilizing the Express Checkout buttons, PayPal, by default, only transmits the buyer’s shipping details to WooCommerce. Depending on the WooCommerce Checkout configuration, the shipping details will be inserted into the billing details on the WooCommerce Checkout page.
PayPal on the Checkout page
The PayPal buttons on the WooCommerce Checkout page take the place of the “Place order” button. Customers must complete all required form fields before making a payment. When a smart button is clicked, the form fields are checked on the server before creating the PayPal order. If necessary, this form field validation can be turned off with a filter to avoid compatibility issues with third-party code. The WooCommerce form field validation occurs after the PayPal order has been created. If the WooCommerce validation fails, the customer will not be charged and no WooCommerce order will be created.
Depending on customer eligibility and plugin configuration, Alternative Payment Methods are automatically presented in the PayPal Payments Checkout gateway.
Advanced Card Processing offers fully customizable “hosted fields” on your website, allowing you to accept credit card payments while keeping your site’s branding consistent. The hosted fields can be styled with your website’s theme or custom CSS.
Available for business accounts in select countries, this solution enables your customers to make debit and credit card payments without requiring a PayPal account. With Vaulting, customers can store their card details for future purchases or subscription renewals.
Note
If you don’t have a PayPal business account yet or have not been evaluated, you can sign up for the Advanced Credit and Debit Card features by visiting PayPal’s website. For a list of countries where this feature is available, see the PayPal documentation on Advanced credit and debit country and currency availability.
The Standard Card Processing option provides a simple solution for accepting credit card payments. When enabled during onboarding, this option displays a PayPal-branded debit or credit card smart button on the checkout page, allowing buyers to pay without a PayPal account. However, in certain circumstances, such as when the Vaulting feature is enabled, buyers may need to log in to an existing PayPal account or create a new one in order to complete the payment with a card.
The pre-built experience provided by the branded smart button makes it clear that PayPal is the payment processor for the transaction. You can hide the branded credit/debit card smart button with the Hide Funding Source(s) setting or switch to the Advanced Card Processing gateway for a fully customizable payment experience.
These settings in the Standard Payments tab determine various features and functionality of the card button.
The Advanced Card Processing offers enhanced functionality compared to the standard credit card smart button. Here are some examples:
Sandbox accounts must follow the same sign-up process to activate advanced card functionality: PayPal documentation: Enable your account for advanced debit and credit card processing
Unlock advanced credit card features by visiting the Advanced Card Processing tab in the plugin settings and enabling the gateway. The standard credit/debit card button on the Checkout page will be replaced by a dedicated and customizable payment gateway for card payments.
With the Vaulting feature enabled, customers can save their credit cards for easier and quicker future transactions.
This new gateway is unbranded and can be fully customized with CSS to integrate seamlessly into your native Checkout page while keeping your site’s branding consistent.
Customize the appearance of the hosted fields from the Advanced Card Processing with CSS. The default style of the fields is based on the active theme, but you have the option to modify them to match your website’s design.
Note
Customizing the hosted fields with custom CSS in the WordPress customizer may not display the changes instantly. For the updated styling to be reflected, ensure to save your modifications and reload the page or add an !important
attribute.
FIELD | SELECTOR |
Button wrapper #id | #ppcp-hosted-fields |
Button class | #ppcp-dcc-order-button |
Card number id# | #ppcp-credit-card-gateway-card-number |
Expiry id# | #ppcp-credit-card-gateway-card-expiry |
CVV id# | #ppcp-credit-card-gateway-card-cvc |
Save Credit Card box id# | #saved-credit-card |
For more information on supported CSS properties, please refer to the PayPal documentation. This resource provides a comprehensive list that you can use to further customize your hosted fields.
While the default style of the fields is controlled by the theme, you have the option to customize the appearance to better fit your needs. Here’s an example CSS that can be added to the WordPress customizer to see the possible adjustments:
#ppcp-credit-card-gateway-card-number, #ppcp-credit-card-gateway-card-expiry, #ppcp-credit-card-gateway-card-cvc {
background-color: #ffffff !important;
border: 1px solid #bbbbbb !important;
border-radius: 5px !important;
box-shadow: 0 2px 4px 0 rgba(0, 0, 0, 0.1) !important;
height: 40px !important;
padding: 0 10px !important;
}
Testing Advanced Credit and Debit Card features with PayPal Sandbox
The Advanced Card Processing implements on-site hosted fields to deliver SCA & PCI compliant payment experiences and supports advanced features like 3D Secure 2 or Vaulting.
The Vaulting feature requires special cards for testing: PayPal documentation: Vault-ready test cards
3D Secure 2 requires dedicated test cards and older 3d Secure credit cards from the official PayPal documentation may not work anymore since they only cover 3D Secure 1 scenarios.
3D Secure 2 test cards:
These sandbox test cards trigger a successful 3D Secure 2 scenario with the Advanced Card Processing:4020024518402084
5232106671708398
Regular, non-3D Secure & non-Vaulting payments can be tested with cards from the Card Generator in the PayPal developer dashboard.
The Vaulting feature allows you to securely store your customer’s payment methods as a unique, non-sensitive token within your system. Your customer won’t have to enter their payment details the next time they purchase from your site.
If you have been approved for Vaulting (Reference Transactions), you can store the information in the PayPal vault without additional fees.
Here are the benefits of saving your customer’s payment methods:
Visit this page or the PayPal Developer Portal to learn more about saving customers’ payment methods.
If your customers complete an initial purchase on your website using any of the following payment methods while the Vaulting feature is enabled, they will be able to save that payment method in the PayPal vault.
Vaulting requires your PayPal business account to be approved for Reference Transactions to start saving your customer’s payment methods using the PayPal vault
Here’s how to request Vaulting approval from your PayPal account using a web browser:
PayPal will send you an email with the next steps or the approval confirmation.
Once you’re approved, go back to Account Settings and click Configure to set up saved payments.
Note: The onboarding wizard is the recommended way to connect your account, as it will automatically configure the REST application for use with PayPal Payments, including Vaulting.
For manually created REST applications, you can enable the Vaulting feature from the PayPal developer dashboard. To use Vaulting within the plugin, ensure it’s activated for the REST application. This step is necessary only when integrating existing API credentials manually, rather than using the onboarding wizard for the account connection.
To manually enable vaulting on your Live REST App, follow these steps:
When Vaulting is enabled in the plugin settings, the Pay Later button & APMs will be hidden, and settings in the Pay Later tab will be disabled.
At this time, Vaulting and Pay Later are mutually exclusive features.
Support for WooCommerce Subscriptions is automatically activated when the Vaulting feature is enabled in the plugin settings.
Required to save payments
Your PayPal account has to be approved for Vaulting (Reference Transactions) to save PayPal accounts in the Vault, e.g. for automatic subscription renewal payments. Credit cards can be saved in the Vault via Advanced Card Processing and used for automatic payments without Reference Transactions.
When the Vaulting setting is enabled, PayPal accounts are saved in the secure Vault after a payment is attempted. Reference Transactions must be enabled to store PayPal accounts in the Vault, for future payments, such as subscription renewals.
With saved payment methods, customers can make PayPal payments with just one click while logged into their WordPress user account, providing a streamlined checkout experience for repeat customers.
The Advanced Card Processing gateway allows credit cards to be securely stored for future use before confirming the payment. While the standard card button does not support card vaulting, it can display a previously vaulted card in the checkout process as can be seen in the Customer Experience screenshots.
Test card vaulting in the sandbox using the PayPal documentation’s list of Vault-ready test cards. In live mode, all supported credit and debit card types are eligible for card vaulting.
Note
Saving credit cards in the Vault is only possible through the Advanced Card Processing gateway, not through the standard card button. Only the test cards listed in the Vault-ready test cards of PayPal documentation can be vaulted in the sandbox. In live mode, all supported credit/debit cards can be vaulted.
Payment methods saved in the Vault can be viewed and deleted on the shop website in the My Account > Payment Methods section.
At this time, new payment methods can only be saved in the Vault by completing a payment.
In a future release, PayPal Payments will receive functionality to add a new payment method from this page without completing a purchase.
PayPal Payments saves a payment method in the secure Vault at PayPal. The vaulted payment method can be used for subsequent checkouts or subscription renewal payments without the buyer being present on the site. Vaulting is a requirement for automatic subscription renewals but not for manual renewals.
Vaulted payment methods allow the buyer to pay for an order or manually confirm a subscription renewal without having to log in to the PayPal account or manually enter the credit or debit card details.
Billing Agreements are required to save a PayPal payment method for automatic subscription renewals in the Vault, so the PayPal merchant account has to be approved for Reference Transactions. Without Reference Transactions, saving a PayPal payment method in the Vault may fail. In that case, the setting Subscription capture behavior if Vault fails must be configured not to fail & void subscription payments if saving the payment method was unsuccessful so buyers can manually confirm renewal payments via PayPal.
Vaulted credit cards via Advanced Card Processing can be saved in the Vault and used for automatic payments without the buyer being present on the site and without being approved for Reference Transactions.
For more details on how PayPal Payments works with WooCommerce Subscriptions, please view the Subscriptions FAQ.
Saving a payment method in the Vault could potentially fail, but PayPal Payments usually cannot precisely determine the reason for the failure. For example, the lack of Reference Transactions may result in PayPal accounts not being saved in the Vault. Beyond this, unverified PayPal accounts or accounts without a linked payment source may not be eligible to save a payment method in the Vault.
Vaulting-specific limitation
A PayPal buyer account can only be saved in the Vault of the PayPal merchant account for one customer id
(unique per WordPress user), not across multiple sites or customer ids
. Reusing the same PayPal merchant account on multiple sites with Vaulting is not recommended, as it could lead to potential problems.
When a buyer attempts to buy a subscription product but the payment method could not be saved in the Vault, it may fail with this error: Could not process order because it was not possible to save the payment on PayPal.
The capture behavior for subscription orders can be controlled with the Subscription capture behavior if Vault fails setting.
Please contact the PayPal Merchant Technical Support with a copy of your plugin log files to request more details about why a payment method could not be saved for a specific case.
BASIC FEATURES | FEATURE SUPPORTED |
Subscription Suspension | ✔ |
Subscription Cancellation | ✔ |
Subscription Reactivation | ✔ |
ADVANCED FEATURES | FEATURE SUPPORTED |
Multiple Subscriptions | ✔ |
Recurring total changes | ✔ |
Payment date changes | ✔ |
Subscription Switching | ✔ |
Customer payment method changes | ✔ (requires saved payment method) |
Store manager payment method changes | ✔ (requires saved payment method) |
Free trial Subscriptions | ✔ |
Synchronized or prorated payments | ✔ |
PayPal Payments uses Vaulting to save a payment method and applies special handling for WooCommerce Subscriptions products (Simple Subscription & Variable Subscription) to ensure successful renewal payments. Subscription products with a free trial period have a special checkout flow as the payment method is saved in the Vault without an actual payment.
Regardless of the configured Intent setting, subscription products are handled with payment authorizations. When the customer completes the subscription payment, the payment is first authorized, and a WooCommerce order is created in the “On-hold” status. If the intent Capture is configured, the authorized payment may be captured automatically within three minutes. During this time, a webhook should be received, which confirms whether or not the payment method was successfully saved in the PayPal Vault.
Saving a payment method in the Vault may fail under certain circumstances. The Subscription capture behavior if Vault fails option determines how these failure scenarios are handled.
The default configuration prevents subscription payments when the payment method was not saved in the Vault.
Failed
. This configuration prevents subscription signups and payments without a saved payment method.“Could not process order because it was not possible to save the payment on PayPal. Order status changed from On hold to Failed.“
Configuring the intent Authorize prevents the failure of manual subscription payments. The authorized payment can be captured manually, but when the payment method is not saved in the Vault during the authorization, automatic renewal payments are still not possible. Automatic subscription renewal payments require a payment method saved in the Vault.
Read the Troubleshooting Vaulting section for more guidance.
PayPal Vaulting stores payment methods securely when Reference Transactions are enabled for the merchant account. This allows for automatic renewals without the customer being present on the site.
Vaulted payment methods can be used for multiple concurrent subscriptions, even if the amounts or renewal dates vary. Subscriptions can be canceled without impacting saved payment methods or automatic renewals from active subscriptions.
If Reference Transactions are not enabled, customers can still purchase subscription products when changing the Subscription capture behavior if Vault fails setting. However, if no payment method was saved, renewal payments require manual confirmation by the customer who must be logged in to the website.
A feature for automatic PayPal renewals without requiring Reference Transactions is in development and expected to be released before the end of Q1 2023.
Credit card payments through Advanced Card Processing do not require Reference Transactions for automatic subscription renewals as there is no billing agreement created for these transactions.
The customer can use payment methods saved in the Vault while being present on the site to manually process a payment for a subscription renewal with a single click. The saved payment method in the Vault allows the buyer an easier and faster login/payment process by not having to manually log in with the PayPal account credentials.
Vaulting is not a requirement for subscriptions if manual renewals are enabled in the WooCommerce Subscriptions settings. Customers can buy subscription products and renew them manually without having a saved payment method in the Vault.
When Vaulting is enabled, the plugin ensures a payment method could be saved at PayPal for subscription-type products and will potentially fail the order if no payment method could be saved.
Subscriptions from different payment gateways using automatic recurring payments can be updated to use PayPal Payments as a payment method instead.
Note:
A saved payment method is required to successfully switch existing subscriptions to PayPal Payments. A separate payment, e.g. for a pending renewal order, is required to save the payment method in the Vault.
Automatic renewal payments will not succeed when the subscription payment method is changed to PayPal Payments without a saved payment method in the Vault.
Customer Payment Method Changes: The payment gateway is presented as an option when a customer changes the recurring payment method used for a subscription. This allows the customer to update the payment method used for future recurring payments when a previous payment failed or when it was set to “Manual Renewal”.
Store Manager Payment Method Changes: The payment gateway is presented to the store manager as an option when changing the recurring payment method used for a subscription on the Edit Subscription screen.
Once a payment method has been saved in the Vault, it can be used for multiple concurrent subscriptions (varying amounts or renewal dates). Subscriptions can be canceled without impacting the saved payment method in the Vault.
The subscription migration layer in PayPal Payments allows automatic renewals of existing PayPal Checkout subscriptions. When a buyer with a pre-existing subscription makes a manual payment, the PayPal account is automatically saved in the Vault. New subscriptions use the payment method saved in the Vault by PayPal Payments, while the migrated subscription renews using the old billing agreement ID (which does not make a difference for the buyer).
Using the same PayPal merchant account on multiple sites for subscriptions is not recommended. Suppose the buyer already has an ongoing subscription with a saved payment method on site A. In that case, the existing billing agreement must be canceled before the same PayPal account could be saved in the Vault of the same merchant on site B.
Follow these steps to cancel existing billing agreements at PayPal:
The customer can also cancel the billing agreement from their PayPal account: What is an automatic payment and how do I cancel or update one?
Once the billing agreement has been canceled, PayPal Payments will automatically attempt to save the payment method in the Vault with the next purchase.
Requirements to save a payment method without a payment
Subscription products with no sign-up costs can only be purchased when the merchant account has Reference Transactions enabled. Without Reference Transactions enabled, buyers attempting to save a payment method for a free trial subscription product may receive an error: UNKNOWN_BUSINESS_ERROR
PayPal Payments includes support for subscriptions with a free trial period or prorated & synchronized payment dates.
To purchase a subscription product with no sign-up costs, the buyer must save a payment method in the Vault. While the customer has a free subscription product in the Cart and the Checkout total is zero, the PayPal button on the Checkout page redirects the customer to the PayPal website, where the PayPal account can be authorized for future transactions.
To save the payment method in the Vault without an initial purchase, PayPal Payments authorizes and then voids a $1 payment.
The subscription cannot be purchased if the buyer has no funds available or no payment method connected to authorize this payment with the PayPal account.
After the $1 payment was authorized and voided, the PayPal account will be saved in the Vault for the current user session. The buyer can complete the subscription purchase with the regular Sign up now button after returning to the Checkout page.
PayPal Payments officially supports the official WooCommerce Subscriptions plugin.
Subscription plans from the All Products for WooCommerce Subscriptions are partially supported.
Subscription-type products from the WooCommerce Payments plugin are not supported.
Broader subscription compatibility with third-party plugins and setups relying on manual renewals will be added in a later update.
Pay upon Invoice is an invoice payment method in Germany. It’s a local buy now, pay later payment method that allows the buyer to place an order, receive the goods, try them, verify they are in good order, and then pay the invoice within 30 days. No PayPal account is needed for the buyer to use Pay upon Invoice.
PayPal has partnered with Ratepay to provide this service. This payment method is also called Rechnungskauf mit Ratepay in German.
PayPal Payments integrates the PayPal shipment tracking feature, enabling you to update tracking information on PayPal. This feature allows you to add tracking numbers and other relevant information to your PayPal orders. The information can be added with or without a tracking number using the Tracking Information metabox.
The tracking integration in PayPal Payments comes with a list of supported carriers and countries. However, the carriers or statuses can be customized to fit specific needs. The customization process is explained in detail in the developer documentation. Additionally, if you need to programmatically modify the tracking data, you can find the relevant information here.
Enabling the Pay upon Invoice payment gateway also automatically activates tracking.
Additionally, the tracking integration interfaces with certain third-party plugins such as Germanized to automatically send your provided tracking data to PayPal without having to manually add it via the Tracking Information metabox.
Before you can add tracking information to orders, the feature must be enabled for your PayPal account.
The easiest way to enable tracking is to disconnect your PayPal account from the integration and reconnect it using the onboarding wizard.
Alternatively, get in touch with the PayPal Merchant Support and request Tracking to be enabled for your account.
FraudNet is a PayPal-developed, JavaScript library embedded into your web page to collect browser-based customer data to help reduce fraud. Upon checkout, data elements are sent to PayPal Risk Services for fraud and risk assessment. FraudNet is for desktop browsers only.
Data collected by FraudNet is used for risk analysis and authentication. PayPal does not share FraudNet data with third parties for their own independent benefit.
When enabled, the FraudNet library is automatically loaded on all pages with enabled PayPal buttons. FraudNet is automatically enabled when Pay upon Invoice is active.
Help boost sales and average order values with PayPal Pay Later.
Pay Later is built into PayPal Payments at no additional cost to you and gives your customers flexible payment options, including short-term interest-free payments and longer term monthly installments with no late fees. Your customers can get what they need now and pay later, while you get paid in full – up front. Pay Later availability and terms vary by country. See details below.
When you install the WooCommerce PayPal Payments extension and connect to a PayPal account, Pay Later messaging is enabled by default.
Once you have installed WooCommerce PayPal Payments, PayPal Pay Later is available in the following regions:
– Pay in 4 & Pay Monthly; for full details, check the Pay Later details for the US
– Pay in 4; for full details, check the Pay Later details for Australia
– PayPal Ratenzahlung & Pay in 30; for full details, check the Pay Later details for Germany
– Pay in 3 instalments; for full details, check the Pay Later details for Spain
– Pay in 4X; for full details, check the Pay Later details for France
– Pay in 3 instalments; for full details, check the Pay Later details for Italy
– Pay in 3 & PayPal Credit; for full details, check the Pay Later details for the UK
Your existing PayPal buttons change to show a new Pay Later button when eligible. When customers select Pay Later, they can pay with flexible, buy now, pay later offers.
Pay Later messaging can be enabled on the single product page, Cart, and Checkout and helps you get the most out of PayPal’s buy now, pay later offers. You can use this onsite messaging to dynamically promote Pay Later offers, which can help grow your sales, attract new customers, and drive customer loyalty.
Pay Later messaging on your site lets your customers know about flexible payment options while browsing, helping convert more sales. In fact, 80% of buy now pay later (BNPL) users in the US agree that seeing a BNPL message while browsing gives allows them to spend more.
The Pay later messaging can be customized with several different styles per Pay Later messaging configuration.
More details can be found in the PayPal documentation: Pay Later messaging
The Pay Later messaging can be individually enabled or disabled for the single product, Cart, and Checkout page.
The Pay Later button is loaded independently of the messaging and both can be disabled from the Pay Later settings tab.
All Pay Later features are automatically disabled when the Vaulting feature is active.
Based on eligibility, PayPal Payments automatically provides buyers with a Venmo button.
Pay with Venmo offers a simplified mobile checkout experience with no additional steps to set up or cost to you. Your buyers get:
All funds will be automatically forwarded to the connected PayPal account.
When eligible, your buyers can use Venmo on the same pages they can use PayPal, including your product page, Cart page, and Checkout page. When buyers select Venmo, they can pay in their Venmo app.
The full Venmo checkout flow is described in the PayPal developer documentation: PayPal documentation: Pay with Venmo – Buyer experience
Alternative Payment Methods, including Venmo, are supported by PayPal business and personal seller accounts.
More information about the eligibility for Venmo is available at the PayPal developer documentation: PayPal documentation: Pay with Venmo eligibility
The Venmo button is automatically displayed for eligible customers by default but can be hidden in different ways:
Alternative Payment Methods (APMs) are supported by PayPal business and personal seller accounts.
These payment methods appear automatically for eligible buyers, primarily on the Checkout page. The funds will be received by your connected PayPal merchant account without requiring additional configuration.
APMs allow you to accept payments from customers around the globe who use their bank accounts, wallets, and local payment methods. When a buyer pays in a currency different than yours, PayPal handles currency conversion for you and presents conversion information to the buyer during checkout.
For example, a customer in the Netherlands might want to pay using iDEAL, which more than half of consumers in the Netherlands used for online purchases. In contrast, a customer in Belgium on the same website might want to pay using Bancontact, a popular payment method there.
PayPal Payments automatically provides payment methods that are relevant to the user.
As of the latest version, PayPal Payments supports the following APMs:
The latest list of supported APMs is available in the PayPal documentation – APM Availability.
Alternative Payment Methods are displayed by default but can be hidden in different ways:
The credit card smart button renders only on the Checkout page and not on the single product, or Cart page to provide a more consistent user experience.
The following payment methods are available from the non-Checkout pages: PayPal, Pay Later, Venmo, and SEPA Direct Debit.
All remaining funding sources (including credit cards) are only available from the Checkout page.
Starting with version 1.5.0, PayPal Payments integrates a migration layer to carry over existing configurations from the no longer supported PayPal Checkout gateway plugin.
When upgrading to PayPal Payments, only the PayPal account must be connected once, and most of the settings (button styling, etc.) will be automatically migrated from the old to the new plugin.
The migration layer will also take over subscription renewals from PayPal Checkout when the latter is not active. This allows you to completely disable or remove the PayPal Checkout extension, while subscription renewals continue to be processed as usual.
We recommend disabling the PayPal Standard and PayPal Checkout gateways (under WooCommerce > Payments) to prevent customers from purchasing new subscriptions using those gateways.
The Vaulting section describes how new subscriptions are handled with PayPal Payments.
If you don’t need the migration functionality, it can be disabled with a filter.
The WooCommerce Cart & Checkout Blocks are a feature to optimize for faster checkout. To make sure this feature is right for your store review the list of compatible extensions from the Cart & Checkout Blocks – Status page.
Pages with the WooCommerce Cart & Checkout Blocks can be set up as new pages, or replace your existing Cart & Checkout pages as explained in this guide.
PayPal Payments comes with an early integration for the Block Cart & Block Express Checkout, with more features being in active development.
PayPal, Pay Later, & Venmo buttons on Block Cart & Block Express Checkout:
Block gateway without smart buttons to complete previously approved express payments:
Using PayPal Payments version 2.2.0 or newer, the PayPal and Venmo buttons can be enabled on the Block Cart & Block Express Checkout locations using the Smart Button Locations setting.
These Block buttons share the styling configuration with the regular Cart & Checkout buttons.
The Pay Later button must be enabled separately for the new locations if you wish to display it for eligible buyers:
The regular payment gateway on the Block page with the PayPal smart buttons is still in development. The express buttons were implemented as a first step to get feedback about Block features while the development of additional features continues.
Yes. While there is no regular PayPal payment gateway on the Block Checkout page yet, a PayPal gateway will load when the buyer has already initiated the PayPal payment process from any express button.
This setting decides if your buyers must confirm the payment from the Block Cart & Block Express Checkout on the Checkout page. It does not affect payments initiated from non-Block pages. This feature is recommended to remain enabled for the best possible compatibility.
If the Require final confirmation on checkout setting is disabled: