To use coupons with WooCommerce.

1. Go to:  WooCommerce > Settings > General > Enable coupons
2. Tick the checkbox to Enable the use of coupon codes.
3. Save Changes.

More info at: Configuring WooCommerce – General options.

Adding a coupon

To add a coupon:

1. Go to: Marketing > Coupons.
   • A fresh installation of WooCommerce will show you an initial screen to create a coupon or to learn more.
     
   • Existing stores start on the Coupons screen.
     
2. Create a new coupon by selecting Add Coupon. Or hover over an existing one to Edit.
3. Enter or generate a Coupon Code. The code is used by the customer to apply the coupon and associated discount. Must be unique as it’s used as an identifier.
   

    

   • Your code – Enter any alphanumeric code you wish.
   • Any code – Select the Generate Coupon Code button if you want WooCommerce to auto-create and enter a coupon code via algorithm.
4. Enter a Description (optional) — Info about the coupon for internal use. For example: Name of promotion/event, dates in effect, compensation, ticket number, customer name.

Under Coupon Data, there are three sections you can use to add restrictions and limits for the coupon: General, Usage Restriction, and Usage Limits.

General

• Discount type :
  • Percentage discount – A percentage discount for selected products only. For example, if the cart contains three (3) t-shirts @ $20 each = $60, a coupon for 10% off applies a discount of $6.
  • Fixed cart discount – A fixed total discount for the entire cart. For example, if the cart contains three (3)  t-shirts @ $20 each = $60, a coupon for $10 off gives a discount of $10.
  • Fixed product discount – A fixed total discount for selected products only. Customer receives a set amount of discount per item. For example, three (3) t-shirts @ $20 each with a coupon for $10 off applies a discount of $30.
• Coupon amount – Fixed value or percentage, depending on discount type you choose. Entered without a currency unit or a percent sign, which are added automatically, e.g., Enter ’10’ for £10 or 10%.
• Allow free shipping – Removes shipping cost when coupon is used. Requires Free Shipping to be enabled.
• Coupon expiry date – Date the coupon should expire and can no longer be used. Expiry happens at 12:00 am or 00:00 on the date chosen. If you want a coupon to be valid through Christmas Day but invalid the moment Christmas is over, set the expiration date to YYYY-12-26 as it will expire on YYYY-12-26 00:00. It uses your site’s time zone setting at Settings > General > Timezone in WordPress.

Usage Restriction

• Minimum spend – Allows you to set the minimum subtotal needed to use the coupon.  Note: The sum of the cart subtotal + tax is used to determine the minimum amount.
• Maximum spend – Allows you to set the maximum subtotal allowed when using the coupon.
• Individual use only – Tick the box if you don’t want this coupon to be used in combination with other coupons.
• Exclude sale items – Tick the box if you don’t want this coupon to apply to products on sale. Per-cart coupons do not work if a sale item is added afterward.
• Products – Products that the coupon will be applied to, or that need to be in the cart in order for the fixed or percentage discount to be applied.
• Exclude products – Products that the coupon will not be applied to, or that cannot be in the cart in order for the “Fixed cart discount” to be applied.
• Product categories – Product categories that the coupon will be applied to, or that need to be in the cart in order for the fixed or percentage discount to be applied.
• Exclude categories – Product categories that the coupon will not be applied to, or that cannot be in the cart in order for the “Fixed cart discount” to be applied.
• Allowed Emails/Email restrictions – Email address or addresses that can use a coupon. Verified against customer’s billing email. WooCommerce 3.4+ also allows you to include a wildcard character (*) to match multiple email addresses, for example, `*@gmail.com` would make any gmail address.

Usage Limits

• Usage limit per coupon – How many times a coupon can be used by all customers before being invalid.
• Limit usage to X items – How many items the coupon can be applied to before being invalid. This field is only displayed if there is one or more products that the coupon can be used with, and is configured under the Usage Restrictions.
• Usage limit per user – How many times a coupon can be used by each customer before being invalid for that customer.

Once you’ve configured all settings, select Publish and your coupon is ready to use.

Sending a coupon

Once coupons are published, go ahead and make available to customers: Copy the title and send, advertise it via email, social media and onsite banners.

Applying a coupon

From WooCommerce 3.2+, coupons can be added to or removed from orders in the Edit Order screen. Orders must be unpaid and you need to know the coupon code you wish to apply.

FAQs

How do coupons impact tax calculations?

Coupons are applied to the product price before tax is calculated. To make sure taxes are then calculated correctly due to rounding, we need to split the discount across all items in the cart rather than remove an amount from the total.

When you split a discount across the cart, naturally, half values could occur that in turn can cause rounding issues once everything is summed up.

To help prevent this, we only use cent values. Once split between items, any remainder is applied one line item at a time until exhausted. The final total will then total the applied discount total. This is most important for fixed cart discounts.

How do coupons impact shipping calculations?

Coupons are applied to individual products or the items in the cart. Shipping Rates are not cart items so coupon discount will not be applied to shipping. e.g. a A $50 coupon applied to a $40 product with a $10 Flat Rate shipping will only discount $40. The order will still cost $10.

Can I customize the Generate Coupon Code function?

Yes, if you are a developer, it’s possible to customize the JS-driven Generate Coupon Code functionality by specifying length of code, and add a prefix and/or  suffix. The Core team intentionally excluded characters that could be ambiguous or difficult to read.

The post Coupon Management first appeared on CODIBU.

Enabling Taxes

To access the tax settings screens, they first need to be enabled.

1. Go to: WooCommerce > Settings > General.
2. Select the Enable Taxes and Tax Calculations checkbox.
3. Save changes.

Configuring Tax Options

To start configuring taxes:

Go to: WooCommerce > Settings > Tax. This tab is only visible if taxes are enabled.

The Tax tab displays several options that can be set to suit your needs — settings you choose are based on the tax jurisdiction under which your store is located.

Prices Entered With Tax

This option is perhaps the most important when managing taxes in your store, as it determines how you input product prices later on.

• “Yes, I will enter prices inclusive of tax” means that all catalog prices are input using your store’s base tax rate.

For example, in the UK you would input prices inclusive of the 20% tax rate e.g. You enter a product price of £9.99 that includes £1.67 tax. A customer in the UK would pay £9.99 as defined, and a customer in the US would only pay £8.32.

• “No, I will enter prices exclusive of tax” would mean that your catalog prices need to be tax exclusive.

Using the example from above, a UK shop would enter 8.32 at the product price. A tax of 20% would be applied on top of this during checkout making the amount payable £9.99.

The tax calculation for tax-inclusive prices is:

tax_amount = price - ( price / ( ( tax_rate_% / 100 ) + 1 ) )

The tax calculation for tax-exclusive prices is:

tax_amount = price * ( tax_rate_% / 100 )

More information about:

• How Taxes Work in WooCommerce
• Automated tax calculation with WooCommerce Tax

Calculate Tax Based On

This setting determines which address is used for tax calculations.

• Customer billing address
• Customer shipping address (default)
• Store base address

If you use store base address, taxes are always based on your store location and not your customer’s location.

Shipping Tax Class

In most setups, shipping tax class is inherited from the item being shipped, e.g., Shipping a reduced rate item such as baby clothes would also use a reduced rate. If this is not the case in your jurisdiction, choose a different tax class.

In the case of multiple tax rates in the order, the shipping tax will be applied as follows:

• If you have a product with the Standard rate in the order, it will be used for the shipping regardless if this rate is high or low;
• If you don’t have a product with the Standard rate in the order, then the first rate found in the Additional tax class section will be used for shipping.

The goal is to make sure that your highest rate is listed the first in the Additional tax class section if you don’t use the Standard class and if you need the highest tax rate to apply to shipping, for example.

Here is a setup to showcase it visually:

The Standard class is there by default but Tax A, Tax B, Tax C should be created for each tax class respectively. Note that it is not possible to delete the Standard tax rate but you can leave it empty and it will be ignored:

Standard rate is empty:

Tax A (24%) – the highest rate listed the first:

Tax B (14%):

Tax C (10%):

As a result, the highest tax rate gets applied to the shipping in the order with multiple tax rates assigned to products:

Rounding

If you enable Rounding tax at subtotal level, instead of per line, the rounding is done at the Subtotal level. Check your tax jurisdiction to know if this is done.

Additional Tax Classes

Tax Classes are assigned to your products. In most cases, you want to use the default Standard class. If you sell goods that require a different tax class (i.e., Tax, except zero-rated products) you can add the classes here. To get started, we include Standard, Reduced Rate and Zero Rate tax classes.

Each class is listed at the top of the tax settings page – click a class to view tax rates assigned to the class.

Display Prices in the Shop

This option determines how prices are displayed in your shop/catalog. Choose from inclusive/exclusive tax display.

Display Prices During Cart and Checkout

This option determines how prices are displayed in your cart and checkout pages – it works independently of your catalog prices. Choose from inclusive/exclusive tax display.

Price Display Suffix

Allows you to change display to: “Prices include __% tax/VAT” or anything appropriate for your store. You can use these two placeholders if you want to have text before and after the price:

• {price_including_tax}
• {price_excluding_tax}

For example: “Price incl. VAT: {price_including_tax}” will display as: “Price incl. VAT: $15” (if that is the price, of course). So, if you’ve set the taxes to display excluding tax, you could add in small print what the tax inclusive of tax will look like:

Display Tax Totals

This determines if multiple taxes get displayed as one total during checkout, or as an itemized list of taxes.

Setting up tax rates

Tax classes are displayed at the top of the tax screen. Click one to view tax rates for the class.

In the tax rates table, you can define tax rates (one per row). Click Insert Row to get started.

Each tax rate has these attributes:

• Country Code – 2 digit country code for the rate. Use ISO 3166-1 alpha-2 codes. Leave blank (*) to apply to all countries.
• State Code – 2 digit state code for the rate. See i18n/states/COUNTRYCODE.php for supported states. For the US, use a 2 digit abbreviation e.g. AL. Leave blank (*) to apply to all states.
• ZIP/Postcode – Enter postcodes for the rate. You may separate multiple values with a semi-colon (;), use wildcards to match several postcodes (e.g. PE* would match all postcodes starting with PE), and use numeric ranges (e.g. 2000…3000). Leave blank (*) to apply to all postcodes.
• City – Semi-colon separated list of cities for the rate. Leave blank (*) to apply to all cities.
• Rate % – Enter the tax rate, for example, 20.000 for a tax rate of 20%.
• Tax Name – Name your tax, e.g. VAT
• Priority – Choose a priority for this tax rate. Only 1 matching rate per priority will be used. To define multiple tax rates for a single area you need to specify a different priority per rate.
• Compound – If this rate is compound (applied on top of all prior taxes) check this box.
• Shipping – If this rate also applies to shipping, check this box.

Tax rate examples

Here is an example of a tax setup for a UK store — 20% for UK customers only.

In this example, we have a 6% tax rate for all U.S. states except California, which has a 7% tax rate and a local tax rate of 2% for ZIP code 90210. Notice the priorities — this demonstrates how you can ‘layer’ rates on top of another.

Importing and exporting rates

There are Import CSV and Export CSV buttons below the table with the rates. You can use them to import and export tax rates to and from a CSV file.

The CSV file for importing requires 10 columns;

country code, state code, postcodes, cities, rate, tax name, priority, compound, shipping, tax class

Leave tax class blank for standard rates.

Below we’ve provided a sample tax rate CSV to import for the United States based on state tax only. This should not be used for production/live purposes, as tax rates frequently change. Double-check any rate for accuracy before using.

Download Sample Tax Rate CSV Here

Deleting tax rates

If you incorrectly added tax rates or the CSV import has incorrectly added tax lines, this information needs to be deleted.

To delete:

1. Go to: WooCommerce > Settings > Tax > Your Tax Rates (Standard, Reduced Rate, Zero Rate)
2. Select the incorrect lines by clicking on them. They are highlighted in yellow.
3. Select Remove Selected Rows. This deletes the highlighted row(s).
4. Save changes.

If you want to delete all tax rates at once, use Delete WooCommerce Tax Rates in WooCommerce > Status > Tools.

Viewing tax reports

Tax reporting can be found in WooCommerce > Reports > Taxes > Taxes by Date > Year. This report allows you view taxes for the year.

Going to Reports > Taxes > Taxes by code displays a different report, showing taxes separately.

Configuring special tax setups

Tax based on subtotal amount

Apply different tax rates based on the customer role

Frequently Asked Questions

Why do prices change when “Prices Include Tax”?

If you are entering prices including tax, you should be aware that this price might change based on the country in which your customer is located.

For example, your store is in the UK, so you create one tax rate for GB of 20%.

• You create a product with a tax inclusive price of £120.
• Customers in the UK will pay £120 (£100 + £20 VAT).
• Customers outside the UK will pay £100 because you do not have any tax rates set up for any other country.

OR

Your store is in the UK, so you create one tax rate for GB of 20%, a tax rate for France of 19% and Norway at 25%.

• You create a product with a tax inclusive price of £120.
• Customers in the UK will pay £120 (£100 + £20 VAT).
• Customers in France will pay £119 (£100 + £19 Tax).
• Customers in Norway will pay £125 (£100 + £25 Tax).
• Customers outside the UK, France or Norway will only pay £100 because you do not have any tax rates set up for any other countries.

This is explained in more detail at: How Taxes Work in WooCommerce.

Can I charge one amount regardless of customer location when defining prices including tax?

This can be done but is an experimental (not officially supported) feature. Read: How Taxes Work in WooCommerce.

When some users visit my store, taxes are not shown.

Since taxes are based on customer location in most setups, things like geolocation can make taxes hidden until the user checks out and inputs their real address.

To prevent this, go to WooCommerce > Settings > General > Default Customer Location to disable Geolocate and set to the Shop Base Address.

Why tax options are greyed out?

Tax options are greyed out if you have enabled automated taxes with WooCommerce Shipping & Tax:

To edit your tax options back, choose Disable automated taxes, and click Save changes.

The post Setting up Taxes in WooCommerce first appeared on CODIBU.

What is a payment gateway?

A payment gateway in WooCommerce terms is a WordPress plugin for WooCommerce that allows customers to pay for goods and services using a payment system such as PayPal or Stripe.

• All require an account with the Payment Gateway company.
• Each has terms and fees set by the Payment Gateway company, which is separate from the WooCommerce extension subscription. Contact the Payment Gateway company directly, with questions about account requirements, terms and fees.
• Some have multiple options based on different account types, transaction types or redirect methods, such as PayPal and CyberSource.

Comparison charts for PayPal and CyberSource.

How to choose a payment gateway

When selecting and setting up up a Payment Gateway, it’s important to consider:

• Cost
• Location
• Security
  • Redirect: Customer is forwarded to the Payment Gateway site to process payment, then redirected back to your site to complete checkout.
  • Direct: Customer purchases and pays directly on your site, requiring an SSL certificate as part of PCI Compliance.
• Support for WooCommerce Subscriptions (if applicable)

If you’d like to read more about payment gateway security, check out our WooCommerce site and data security FAQ.

Cost

Startup and ongoing costs are different for each payment gateway and can consist of:

• Purchase of the payment gateway, if not free
• Signup fee charged by the payment gateway company/processor
• Monthly/yearly subscription fees
• Transaction fees

Location

Shop location and currency are factors. A payment gateway company/processor may only serve merchants based in certain countries. If it only supports U.S. dollars and accepts U.S. shop owners, shop owners in Canada and Europe cannot use it.

However, customers from all over the world can use the gateway to check out and pay. More info at: What to Consider about Payments when Selling Internationally and How to Choose a Payment Gateway

Security

Shop owners accepting payments have a responsibility to protect sensitive customer information, such as email addresses, shipping addresses and billing information.

To do this, most payment gateways require an SSL certificate. This encrypts communications between your site and customers, and your site and the payment processor. More info at: SSL FAQ.

Other steps to secure your site are covered by the Payment Card Industry Data Security Standard (PCI-DSS), which apply to anyone storing, processing or transmitting credit card data. More info at: PCI-DSS compliance and WooCommerce.

Support for Subscriptions

Should you wish to sell Subscriptions (separate purchase), you must choose a payment gateway that supports manual or automatic recurring payments. More info at: Subscription payment methods and gateways.

How many do I need?

You need at least one payment method to collect payment on your site.

• One: Only having one way for customers to pay is a risk, as payment gateways can encounter down time or another unforeseen issue.
• Two: Offering different payment options increases the possibility that customers can always check out and complete payment.

Too many payment gateways can overwhelm customers with choice and make your site administration more complex. Choose according to shop requirements and business needs.

Here’s an example of two payment gateways on the checkout page:

Free vs. Premium

Our WooCommerce plugin gives you several free payment options to use, called Core Payment Options. Should you wish to use something different, you can select and purchase a Premium gateway.

Core gateways (free)

Payment gateways and options included in WooCommerce for *free are listed at: Core Payment Options.

*PayPal and Stripe charge fees and require you to set up an account. WooCommerce.com charges you nothing.

Premium gateways

Paid payment options available: Premium Payment Gateway extensions. In the left sidebar, search by Direct, form, iFrame, Offsite (Indirect) or Country.

Payment gateways and the GDPR

If selling to customers in Europe, the European General Data Protection Regulation (GDPR) framework should be part of your decision on which payment gateway to choose. For more information on the GDPR and its concerns for user privacy, see: WooCommerce and the GDPR.

Customer information collected during checkout depends on the payment gateway. If you’re working with a manual payment gateway such as BACS, your site won’t process the payment itself, since you will check your bank account, independently of your site. Other payment gateways, such as Stripe or PayPal, require information to be passed from your site to that payment processor. It’s up to you to choose a reliable processor, as well as consider the impact on customer data.

• Be aware of what information is being sent
• Inform customers on what happens to their data
• Understand what the payment processor does with that information

For example, the WooCommerce Stripe plugin sends certain customer information to Stripe (see Stripe documentation for specifics). You need to disclose this process in your site’s Privacy Policy.

Any payment gateway you choose should have information about how to handle customer data. Check the payment processor’s website to learn more about their privacy policies and GDPR.

For more information on how payment gateways apply GDPR, see: Privacy Considerations when Using Official Payments Extensions.

The post Which Payment Option is Right for Me? first appeared on CODIBU.

For more details and information about this, please see the European Commission Taxation and Customs Union website for VAT MOSS (mini One Stop Shop).

In addition, you need to set up VAT rates in your WooCommerce store to charge the correct amount. This guide shows you how to set up rates specific to Digital Goods.

Setting Up Your Tax Classes

If you’re only selling digital goods, VAT rates can be added under Standard Rates in WooCommerce.

If you’re selling/distributing both digital and regular products, you can create and use a new tax class, for example, Digital Goods, and update them.

To set up EU VAT rates in a new tax class:

1. Go to: WooCommerce > Settings > Tax.
2. Select the Additional Tax Classes setting.
3. Add a new tax class to the list, for example, Digital Goods.
4. Save.

After saving the tax options changes, tax rates need to be assigned to this tax class.

Setting Up the EU VAT Rates

The next step is to input the EU VAT Rates into WooCommerce.

Look Up the Latest VAT Rates

The latest VAT rates can be found at the Europa website in a PDF document. If these rates change, you need to update the VAT rates for your store.

Input Rates

1. Go to: WooCommerce > Settings > Tax > Digital Goods (now a new tab after you created a new tax class).
2. Enter rates for all EU member states. See our guide on Setting Up Tax Rates in WooCommerce.

At the time of the last update, Standard VAT rates are:

Alternatively, if you have a CSV file in the correct format, you can import the VAT rates to save time. Here are the above rates in CSV format with tax class Digital Goods: vat_rates.csv

To import this file, select Import Rates on the tax input page, and an importer will appear.

Once rates have been uploaded, imported or input, in the tax rate screen you will see a table similar to this:

With EU VAT rates set up, users buying a product with the Digital Goods tax class are charged tax based on their location, not the store location.

Assigning the Tax Class to Products

To apply this tax class to digital products in WooCommerce:

1. Go to: Products > All Products.
2. Edit a product.
3. In the General section of the Product data, select the tax class created from the Tax Class dropdown.
4. Update the product

You can also bulk-edit products:

1. Go to: Products > All Products.
2. Tick the box to the left of each of the products you want to bulk-edit.
3. Select Edit from the bulk actions dropdown.
4. Apply.

After clicking Apply the bulk edit view will appear:

1. Choose the tax class from the Tax class dropdown.
2. Click Update to apply the Tax class to the selected products.

Questions

Have a question or need assistance? Get in touch with a Happiness Engineer via the Help Desk.

The post Setting Up EU VAT Rates for Digital Products first appeared on CODIBU.

The cart and checkout blocks are fully functional, with some limitations. The blocks are not yet a complete replacement for the existing shortcodes.

The purpose of this document is to provide clear information about what is supported and what’s still in development, so stores can make an informed decision about how to use the blocks.

Requirements

To use the cart and checkout blocks, your site must meet the following requirements:

• WooCommerce Blocks plugin installed and active (v2.6 minimum, latest recommended).
• Use one or more supported payment gateways (see below for details).

Compatible Payment Gateways

Extensibility

The extensibility interfaces for the cart and checkout blocks are still being developed. Because the blocks are completely new, extensibility interfaces are not final and are subject to change.

The cart and checkout blocks support selected payment methods (detailed above). Note that not all payment methods in the Stripe extension are supported at present.

The cart and checkout blocks do not currently support plugins that integrate with the cart and checkout shortcodes. In particular, extensions that use hooks related to cart and checkout may not function as expected. Extensions that render additional markup in cart or checkout – for example, custom checkout fields – are not supported.

If you’re developing extensions or customizations that integrate with cart and checkout, you can follow development progress, and provide feedback over on GitHub.

The post Cart & Checkout Blocks – Status first appeared on CODIBU.

Requirements

• A PayPal Business account

Go to paypal.com, and sign up for a PayPal Business account or convert an existing Personal account to Business. It’s free.

Setup and Configuration

To set up PayPal Standard:

1/ Go to: WooCommerce > Settings > Payments.
Note: ‘Payments’ formerly called ‘Checkout’ prior to WooCommerce 3.4.

2/ Use the toggle under Enabled to select PayPal.

3/ Select Set up. You are taken to the PayPal Standard settings.

4/ Enter your email address in the PayPal Email field, which is the most important thing to configure before taking payments. Must match the same email address on your PayPal Business account.

Advanced Options

Under Advanced Options, complete fields as needed.

5/ Tick the box for Enable PayPal Sandbox if you wish to test the checkout process during your store’s development. With sandbox enabled, no payment/money is taken. To use Sandbox mode, you need a separate sandbox account via PayPal Sandbox.

6/ Debug log may also be turned on, which can be useful during development. You may need to first create a wc-logs folder and set permissions to make it writable. These logs are available at WooCommerce > System Status > Logs and then select the PayPal log from the dropdown.

7/ Tick the box for Enable IPN Email Notifications (optional). Instant Payment Notifications (IPN) are sent from PayPal when you receive a payment, issue a refund or a chargeback or cancellation.

8/ Enter an email address for Receiver Mail if this address is different than the PayPal email address you entered above in step 4.

9/ PayPal Identity Token (optional). Only required if you signed up for the Data Transfer option on your PayPal account; can be used to verify payments if you have IPN issues.

10/ Enter an Invoice Prefix (useful if you have multiple stores). WC is default to denote WooCommerce transactions.

11/ There are two shipping options:

• Send shipping details to PayPal. You can opt to have WooCommerce send shipping details to PayPal to create shipping labels instead of billing.
• Address override option. PayPal verifies addresses therefore this setting can cause errors. We recommend keeping it disabled, but it can be useful in preventing address information from being changed.

12/ Payment Action lets you choose to Capture funds immediately or only Authorize*.

*Once an ‘authorize only’ order has been changed to Processing or Completed, funds are automatically captured as long as you have entered your PayPal API Credentials (as below) under WooCommerce > Settings > Payments > PayPal. It is no longer a manual process as of WooCommerce 3.0.

13/ Page Style (optional) allows you to select the name of a custom page from your PayPal account.

14/ Image URL (optional) gives the option to specify a 150×50 image to display on PayPal checkout pages.

API Credentials

There are three fields to paste API information into:

• API Username
• API Password
• API Signature

How to get Live API Information

1. Log in to your PayPal account at PayPal.com.
2. Go to Settings (Gear Icon) > Account Settings > API Access.
3. Select NVP/SOAP API integration (Classic) > Manage API Credentials > Request API Signature.
4. View and copy API Username, API Password, and API Signature.

Configuring the PayPal dashboard

Most of the configuration is handled from WooCommerce, but there are a few items to set up at PayPal.

PayPal IPN URL

It’s necessary for WooCommerce to set up your PayPal IPN URL.

PayPal Instant Payment Notifications (PayPal IPN) tells your store that payment has been successful (or not). To learn more about how to set this up on PayPal, see: How to Activate IPN in your PayPal Account.

How to setup PayPal IPN

1. Log in to your PayPal account at PayPal.com.
2. Go to Settings (Gear Icon) > Account Settings > Notifications > Instant Payment Notifications (Update).
3. Click the Choose IPN Settings button, then use this URL, replacing example.com with your own URL:

   https://example.com/?wc-api=WC_Gateway_Paypal

4. Make sure the Receive IPN messages option is selected, then save.

Auto-Return

You can set up auto-return in your PayPal account, which will take customers to a receipt page.

How to setup Auto-Return

1. Log in to your PayPal account at PayPal.com.
2. Go to Settings (Gear Icon) > Account Settings > Website payments > Website preferences.
3. In the Auto return section, select On, then use this URL, replacing example.com with your own URL:

   https://example.com/checkout/order-received/

   Regardless of this setting, it redirects dynamically to the correct receipt page.

4. Optional: Add ?utm_nooverride=1 to the end of your URL to ensure that transactions (i.e., conversions) are credited to the original traffic source, rather than PayPal.

Testing with PayPal Sandbox

While configuring and ironing out your site’s checkout and payment workflows, you might choose to use PayPal sandbox details instead, so you can transact to your heart’s content.

For this purpose, you can sign up for a PayPal developer account. Once signed up, select Sandbox » Accounts (1) from the menu, and click Create Account (2). Specify the Account type and Country/Region to match your requirements.

Note: The Country/Region will determine the currency of your sandbox account, which should match your site’s currency to avoid orders being set to Pending payment.

Next, click the dots menu next to the newly added account in the Manage accounts column, and select View/Edit Account (3) to reveal the sandbox account’s details.

Under the Profile tab of the modal that opens, you’ll notice your sandbox account has a PayPal provided Email ID. Use this email address while your site is in sandbox mode.

Note: The sandbox Email ID should be used for both the PayPal email and Receiver email fields on your site, which can be found under WooCommerce > Settings > Payments > PayPal .

If the live PayPal email address is used instead, order statuses will show On Hold and the order notes will read “Payment pending (unilateral). Order status changed from Pending payment to On hold”.

Frequently Asked Questions

Do I need an SSL certificate?

Payment is made offsite on the PayPal website and not your checkout. Adding an SSL certificate is optional but definitely recommended. SSL is a ranking factor in search results; it also keeps any information transmitted to and from your site secure, and customers expect it. For free and low-cost options, see: SSL and HTTPS.

How much does it cost to use PayPal with WooCommerce?

PayPal Standard is included with the core of WooCommerce, which is free to download.

PayPal charges you transaction fees depending on the account you qualify for and the number/volume of sales you make. Find out more at: Which Payment Option is Right for Me?

WooCommerce does not charge you a fee.

I have pending orders, but no payment was received.

If the customer abandons the order in PayPal (and not your WooCommerce store), the order shows as Pending (unpaid). No action is necessary.

When the hold stock time is reached, the order will be automatically canceled.

What data is sent to PayPal when a customer is checking out?

The PayPal gateway passes individual line items to PayPal (product name, price and quantity) unless:

• Your prices are defined as including tax
• You have more than nine line items, including shipping – PayPal only supports nine items.

This is to prevent rounding errors and to ensure correct totals are charged. When line items are not sent, the items are grouped and named ‘Order #x’.

My shipping costs are not transferring to PayPal

WooCommerce 2.6+ sends shipping costs as a ‘real’ shipping line item via PayPals API. If your PayPal account has shipping rules setup within it, these will take over and remove the cost WooCommerce sends across.

To resolve, you must remove all shipping rules that are set up in the PayPal account or disable them using the method outlined here.

Why am I getting payments, but orders are still pending? *OR* Why is my cart not clearing after making payment?

In this case, the PayPal IPN is failing. Check your server and see the Debugging IPN issues section below.

Why do I get an Internal Server Error?

If you see the following error message after hitting the purchase button, the email address you entered in PayPal settings is incorrect:

Using the same PayPal account with more than one website

WooCommerce uses an “invoice” system. There is a setting that “blocks duplicate invoices.” With two websites using invoices, it is inevitable that there will be duplicate invoice numbers. By de-selecting that setting in PayPal, the invoices have no issue. Please check that the Invoice Prefix in your WooCommerce PayPal settings is different for each site.

Alternatively, to disable duplicate invoice checking, log into your PayPal account and go to Profile > Profile and Settings > My Selling Preferences > Block Payments (or) Payment Receiving Preferences and set Block accidental payments to “No.“

Do customers need a PayPal account?

There is an option that allows customers to check out without creating an account, but it does first need enabled in your PayPal account.

Once logged in select the gear icon in the top right to get to the My Profile page. Then head to the Products & Services section and select Website Preferences. Once there toggle on the PayPal Account Optional option. To learn more, see: PayPal’s Website.

Is PayPal Seller Protection in effect?

Yes, if you use the Shipping address. No, if you use your Billing address (default). The PayPal API does not recognize more than one address.

How does Venmo work with my PayPal account?

PayPal has a page dedicated to common questions about Venmo signup, payments, refunds, disputes and opting out at Venmo and my PayPal account FAQ.

Message: Seller only accepts payments from unencrypted payments

The “Seller only accepts payments from unencrypted payments” message is from PayPal.

This error displays when your PayPal Account Profile is set to only accept payments from “encrypted” buttons but your item button code is “not” encrypted. This interrupts the payment process and displays the error message.

To turn off this option:

1. Log into your PayPal Account.
2. Select the Profile tab or Edit Profile link.
3. Under Selling Preferences, select Website Payment Preferences.
4. In the “Encrypted Website Payments” section, select Off.
5. Save changes.

Message: This invoice has already been paid

WooCommerce order numbers may not be unique if you’re running multiple stores or use your PayPal account for other things.

To avoid this issue, go to WooCommerce > Settings > Checkout > PayPal and set a unique ‘prefix’ for your store, e.g., MYSTORE-

Message: Sorry, it seems there are no available payment methods which support subscriptions

To use PayPal Standard with WooCommerce Subscriptions:

• add API credentials
• set up PayPal IPN URL
• check the box Enable PayPal Standard for Subscriptions:

Debugging IPN issues

As mentioned above, Instant Payment Notifications (IPN) are sent from PayPal when you receive a payment, issue a refund or a chargeback or cancellation.

The below steps can be taken if IPN is not updating your orders. While working on these problems you may want to prevent pending (unpaid) orders cancelling automatically so you have a chance to manually confirm payment without IPN. To do this, go to WooCommerce > Settings > Products > Inventory and set the “Hold Stock (minutes)” option to nothing (leave the field empty).

Please also note, you can check the IPN history page for more information on IPN deliverability here, after logging into your PayPal account: https://www.paypal.com/us/cgi-bin/webscr?cmd=_display-ipns-history

Are you testing locally?

If you are testing locally, on MAMP for example, PayPal is unable to talk to your store. This is normal — it will work when you host it on the web.

Check your server has support for fsockopen

The gateway must talk to PayPal to check the validity of notifications – for this it needs fsockopen support. The exact function used is https://codex.wordpress.org/Function_API/wp_remote_post

*To check if this is supported by your server, go to WooCommerce > System Status and see the results.

Check if your server has a firewall

The gateway talks to PayPal via a https URL. Your firewall needs to have the outgoing port 443 open.

Enable Logging

After enabling logs via the settings, check to see that responses are being received. If they are not, then the problem may be due to your WordPress install or a plugin conflict. Turn off other plugins.

Check Email Addresses

Check that the Email Address in the PayPal gateway settings matches the email address passed back by IPN. Use your primary email address for your PayPal account. They need to match.

Failure to do so will cause the IPN response to be rejected. This could result in orders remaining on hold or not completing.

Check for conflicts

If the order status is not changing on order complete, check if there is a conflict with W3 Total Cache.

Currency in PayPal Sandbox mode

When PayPal is in sandbox mode, it automatically sets payments to Pending if they are made in a currency other than the sandbox currency. Ensure that the currency you have set in PayPal sandbox is the same as the currency in your WooCommerce store.

Why don’t customers see the link to download products after paying and getting redirected back to my website?

This could be a sign that the IPN isn’t working correctly with your website. A possible workaround is to enable Payment Data Transfer (PDT). Within your PayPal account settings, try setting the following:

Once you have saved the settings, go back to the Website Settings page and find the PDT Identity Token:

With the PDT Identity Token copied, you can paste it into the WooCommerce > Settings > Checkout > PayPal field:

Still not working?

Get in touch with your host. Some hosts, such as GoDaddy, are known to have problems with IPN, and this is unfortunately out of our control. Make sure the response from PayPal isn’t blocked by caching, firewalls, or other things in place on your server.

The post PayPal Standard first appeared on CODIBU.

You, as the store owner, should confirm that cheques have cleared before processing orders in WooCommerce. It’s important to verify that you are paid before shipping an order and marking it Complete.

For more information, see Managing Orders.

Note: Check Payments was formerly called ‘Cheque’ prior to WooCommerce 3.3.

Setup and Configuration

1. Go to: WooCommerce > Settings > Payments.
2. Use the toggle under Enabled to select Check Payments.
3. Select Set Up. You are taken to the Check Payments settings.
   
4. Configure your settings:
   • Enable/Disable – Enable to use. Disable to turn off.
   • Title – Choose the title shown to customers during checkout
   • Description –Add info shown to customers if they choose Check
   • Instructions – Explain how to pay by Check
5. Save changes

The post Check Payments first appeared on CODIBU.

Orders using Direct Bank Transfer are set On Hold until payment clears outside of WooCommerce.

You, as the store owner, should confirm that payments have cleared bank accounts before processing orders in WooCommerce. It’s important to verify that you are paid before shipping an order and marking it as Processing or Complete.

For more information, see Managing Orders.

Setup and Configuration

1. Go to: WooCommerce > Settings > Payments.
2. Use the toggle under Enable to select Direct Bank Transfer.
3. Select Set Up. You are taken to the Direct Bank Transfer settings.
   
4. Configure your settings:
   • Enable/Disable – Enable to use. Disable to turn off.
   • Title – Choose the title shown to customers during checkout
   • Description – Add info shown to customers if they choose Direct Bank Transfer
   • Instructions – Explain how to make payment to your bank account(s)
   • Account Details –  Enter account name and number, bank name, routing number, IBAN and/or SWIFT/BIC numbers shown to customers on the Order Received page and in Order emails after checking out
5. Save changes.

Bank account details will show on both the Order Received page and the order email sent to the customer:

The post Direct Bank Transfer (BACS) first appeared on CODIBU.

You, as the store owner, need to confirm payment was collected before marking orders Complete in WooCommerce.

For more information, see Managing Orders.

Setup and Configuration

1. Go to: WooCommerce > Settings > Payments.
2. Use the toggle under Enabled to select Cash on Delivery.
3. Select Set Up. You are taken to the Cash on Delivery settings.
   
4. Configure your settings:
   • Enable COD – Enable to use. Disable to turn off.
   • Title – Choose the title shown to customers during checkout
   • Description –Add info shown to customers if they choose Cash on Delivery
   • Instructions – Explain how to pay via Cash on Delivery
   • Enable for shipping methods – Choose which shipping methods and rates will offer Cash on Delivery
   • Accept for virtual orders – Tick box to allow COD for virtual products
5. Save changes

To extend the standard Cash on Delivery feature, please see this Advanced Cash on Delivery with Fee extension.

The post Cash on Delivery first appeared on CODIBU.

Download it now at WordPress.org or via the “Add New” option under Plugins on your site. For full details of updates, please see the Changelog.

Installation

1. Go to Plugins > Add New on your WordPress site.
2. Enter WooCommerce Stripe in the Search Plugins bar. The author is WooCommerce.
3. Click Install Now and Activate.

To learn more, see Installing and Managing Plugins.

Setup and Configuration

1. Go to: WooCommerce > Settings > Payments and you’ll see all the separate payment method Stripe offers. The main one just being Stripe
   
2. When first activated, the Stripe payment method will be Enabled. Tick the Enable Stripe checkbox to disable.
3. Enter a Title (required) and Description (optional) seen by the customer during checkout.
   • The Title is shown at the payment method option on the Checkout Page and also within the Order showing how the customer paid
   • The Description is displayed within the payment method option on the Checkout Page
4. Tick the Enable Test Mode checkbox, if you wish to test before going live. Untick to begin accepting payments with Stripe.
5. Enter your Live Secret Key and Live Publishable Key (obtained from your Stripe account). The Test Secret Key and Test Publishable Key are different and should only be used when Enable Test Mode selected in step 4.
6. Enter Statement Descriptor, a description that appears on a customer’s bank or credit card statement. This cannot be blank and can be up to 22 characters. The statement description must contain at least one letter, may not include these characters > < " '. In addition, only alpha-numeric characters may be used.
7. Tick the checkbox to Capture Charge Immediately (Authorize and Capture at the same time) or untick to only Authorize. If you untick the box, you’ll need to capture funds manually for each order within 7 days otherwise the authorization will be canceled alongside the order. See our FAQ on this for more.
8. Enable Payment Request Buttons (optional) if you wish to give customers the ability to pay via a supported method. More information in the Payment Request buttons section.
9. Payment Request Button Type will change the type of button to show.
   • Default – “Pay” (default Apple or Stripe button)
   • Buy – “Buy Now” (Apple or Stripe variant)
   • Donate – “Donate” (Apple or Stripe variant)
   • Branded – Branded button, enables Google Pay styles in Chrome browsers
   • Custom – Simple unbranded button with custom text. Follow these guidelines to customize its appearance
10. Payment Request Button Theme will change the appearance of the button to show.
11. Payment Request Button Height will change the height of the button to match your styling preferences.
12. Payment Request Branded Button Label Format will change the label format of the branded button.
13. Payment Request Button Label will change the text of the custom button.
14. Saved Cards, if you want to give Stripe customers the ability to use a card saved on their account for future purchases.
15. Log Debug Messages, if you wish to save logs that can help you/us troubleshoot your site. Can be disabled and enabled as needed.
    1. Logs will appear under WooCommerce > Status > Logs. Use the dropdown menu to select, and view.
       • The log will be titled in the same format as other WooCommerce plugin log files: `woocommerce-gateway-stripe-[date]-[string].log`
    2. When enabled, only events that happen after the point of being enabled are logged.
16. Save Changes.

Webhooks

Webhooks are used by Stripe to communicate with your site. It provides information such as the status of the payment, and is used update the order based on certain events from Stripes side of things.

In the Stripe settings you’ll find a webhook endpoint ready for you to copy and paste into your Stripe.com account.

• Head to WooCommerce > Settings > Payments > Stripe. Under the Webhook Endpoints section copy your webhook endpoint URL.
• Next in your Stripe Dashboard go to Webhook Setting and select Add Endpoint at the top right.
• Paste the webhook endpoint URL copied earlier into the Endpoint URL field and click receive all events.
• Select Latest API version from the Version section if shown, and then Add endpoint.
• Repeat this process for your live Webhook Secret, or vice versa, depending on which you setup first.

If your site experiences a slowdown after this, you can select events manually instead of all events. This can be done from the Events to send dropdown. The events needed by our Stripe extension are:

• source.chargeable
• source.canceled
• charge.succeeded
• charge.failed
• charge.captured
• charge.dispute.created
• charge.refunded
• review.opened
• review.closed
• payment_intent.succeeded
• payment_intent.payment_failed
• payment_intent.amount_capturable_updated

Stripe Checkout

Stripe Checkout

The new Stripe Checkout is not part of the WooCommerce Stripe payment gateway. This is an open enhancement and further details and any future development will be linked from this GitHub Issue.

Stripe Modal Checkout

Payment Request Buttons

When the Payment Request Buttons option is selected, all types of Payment Request Button are activated (on your site) at once so you’re ready to accept payments via a variety of methods with the WooCommerce Stripe payment gateway.

Available options are:

• Apple Pay
• Google Pay
• Microsoft Pay
• Samsung Pay
• Any other method that uses the Payment Request API. The customer needs to be using a supported browser and have credit cards saved to their account.

To see what a Payment Request Button looks like and how it behaves, go to the Stripe.com Payment Request Button documentation page.

Apple Pay

Customers need to have a payment method from a supported bank or payment card provider listed at the Apple Pay support page, and a compatible Apple device.

The WooCommerce Stripe payment gateway handles domain verification for you automatically, so no manual configuration should be required. (If your domain changes or you encounter an issue, load WooCommerce > Settings > Payments > Stripe and then verify that your domain now appears listed in the Apple Pay configuration on your Stripe Dashboard – see Stripe’s “Verify your domain with Apple Pay” doc for more.)

For existing Stripe merchants looking to enable Apple Pay, please ensure that the Payment Request Buttons box is ticked on within WooCommerce > Settings > Payments > Stripe. If you have any issues with accepting Apple Pay, please follow the steps above by logging into your Stripe Dashboard and verifying your domain.

Use of “Apple Pay on the Web”, which our Stripe integration uses to display the Apple Pay Payment Request buttons, is subject to the Apple Pay on the Web terms of service. This is a part of the Stripe Services agreement to which you agree when activating your Stripe account.

Google Pay / Samsung Pay / Microsoft Pay

Make sure that the Payment Request Buttons option is enabled, there is no other setup for you to accept payments via these methods.

Note: these Payment Request buttons usually only show when there is a saved payment method in the browser or device being used. Customers need to have a payment method from a supported bank or payment card provider.

More details and support at Google Pay Help, Samsung Pay, Microsoft Pay.

Additional Payment Methods

Aside from standard credit and debit cards, Stripe comes with additional payment methods that can be used to target different markets. Our extension supports:

• Alipay
• Bancontact
• EPS
• Giropay
• iDEAL
• Multibanco
• Przelewy24 (P24)
• SEPA Direct Debit
• SOFORT

* WeChat Pay – Currently in Public Beta and will be available at general release.
* Klarna – Currently in Public Beta and will be available at general release.

For detailed information about these payment methods, please click on the links above or visit the Stripe Payment Methods, alternatively Stripe.com has a Payments overview page with a lot of useful information. Most of these additional payment methods need to be enabled under Payment Settings on your Stripe.com Dashboard and may require additional information to be fully set up.

Once enabled in Stripe, they can be set up and managed under WooCommerce > Settings > Payments by using the slider icon or by selecting the payment service name. You can also change the title and description of each service within settings for that method.

Customer Usage

Checkout Page

Customers pay on the checkout page, where the form now uses Stripe Elements that provide enhanced security, styling, and better customer experience.

Using a new card, they see the option to enter credit card details, and tick the Save payment info to account box (this screenshot shows the “Inline Credit Card Form” version):

For customers who have a saved card, they are presented with stored card options on file (if that option is enabled) or they can store a new one (screenshot showing the standard non-Inline form):

When Payment Request Buttons are enabled, customers see the corresponding button on the product page and on the cart page when using a supported device, browser, and payment method.

Payment Request Buttons

Browse the gallery to view default layouts for Payment Request buttons.

Saved Payment Methods

On the My Account page, customers can add, view, and remove cards from their account within the Payment Methods submenu:

Hooks (Actions/Filters)

This section describes all hooks available to you if you need to manipulate how Stripe functions. This is more advanced so read over the Hooks page of the WordPress.org Codex if unfamiliar with how hooks work within WordPress.

Hook name (parameters)

Action Hooks

• wc_gateway_stripe_process_response ($stripe_response, $order) – The response we get back after calling a charge request to Stripe.
• woocommerce_credit_card_form_start ($gateway_id) – Before showing the credit card form.
• woocommerce_credit_card_form_end ($gateway_id) – After showing the credit card form.
• wc_gateway_stripe_process_payment ($stripe_response, $order) – The response we get back after calling a charge request to Stripe but before processing the actual response.
• wc_gateway_stripe_process_payment_error ($error, $order) – Called when an error occurs during the process payment event.
• woocommerce_stripe_add_customer ($args, $response) – Called after creating a Stripe customer.
• woocommerce_stripe_add_source ($stripe_customer_id, $wc_token, $response, $source_id) – Called after creating/attaching a source to a customer.
• wc_stripe_delete_source ($stripe_customer_id, $response) – Called after deleting a source from customer.
• wc_stripe_set_default_source ($stripe_customer_id, $response) – Called after setting a default source to a customer.
• wc_gateway_stripe_process_redirect_payment ($response, $order) – Called after a redirect payment process.
• wc_gateway_stripe_process_redirect_payment_error ($error, $order) – Called after a failed redirect payment process.
• woocommerce_stripe_process_manual_capture ($order, $result) – Called after a manual capture of a charge within admin order.
• woocommerce_stripe_process_manual_cancel ($order) – Called after a cancel of the order that is authorized and not yet captured.
• wc_gateway_stripe_process_webhook_payment ($response, $order) – Called after a webhook payment process.
• wc_gateway_stripe_process_webhook_payment_error ($order, $notification, *$e) – Called after a webhook payment process error.

Filter Hooks

• wc_stripe_save_to_account_text ($text) – Text that shows to customers next to the save payment information checkbox.
• wc_stripe_payment_icons ($icons_array) – Icons that show next to each payment method.
• wc_stripe_send_stripe_receipt *boolean* – Whether to send a receipt via Stripe.
• wc_stripe_payment_metadata ($metadata, $order, $prepared_source) – Metadata that gets passed during a payment request.
• wc_stripe_generate_payment_request ($post_data, $order, $prepared_source) – Post data that gets passed during a payment request.
• wc_stripe_owner_details ($details, $order) – The owner details of an order.
• wc_stripe_force_save_source ($force_save_source, $customer) – Override force save customer.
• wc_stripe_use_default_customer_source ($use_default) – Whether to use default customer source if source not found.
• wc_stripe_refund_request ($request, $order) – Request parameters when refund is requested.
• wc_stripe_PAYMENT_METHOD_settings ($settings)</strong – Admin settings for payment method.
• wc_stripe_description ($description, $payment_method_id) – Override the description of credit card payments.
• wc_stripe_display_save_payment_method_checkbox *boolean* – Whether to show the save payment method checkbox.
• wc_stripe_sepa_mandate_notification ($method) – The method to use to inform customer of the SEPA mandate.
• wc_stripe_allow_prepaid_card *boolean* – Whether to allow prepaid credit card to be used.
• wc_stripe_elements_options – Additional options to manipulate Stripe elements.
• wc_stripe_elements_styling – Additional options to manipulate the Stripe elements styling.
• wc_stripe_elements_classes – Additional options to add classes to the Stripe elements.
• wc_stripe_params ($params) – Localized JS key/value pair.
• wc_stripe_payment_request_params ($params) – Localized JS key/value pair.
• wc_stripe_hide_display_order_fee ($bool, $order_id) – Whether to hide the display order fee in orders view.
• wc_stripe_hide_display_order_payout ($bool, $order_id) – Whether to hide the display order payout in orders view.
• woocommerce_stripe_request_headers ($headers_args) – Headers parameters for cURL requests.
• wc_stripe_idempotency_key ($key_string, $request) – The string for the idempotency key on request.
• woocommerce_stripe_request_body ($request, $api) – The request body to pass when doing a request
• wc_stripe_customer_metadata ($metadata, $user) – The meta data used when creating a customer.
• wc_stripe_create_customer_args ($args) – The arguments used when creating a customer.
• wc_stripe_localized_messages ($localized_messages) – The messages used from Stripe responses.
• wc_stripe_logging ($bool, $message) – Whether to log a specific message when logging is enabled.
• wc_stripe_webhook_review_change_order_status ($bool, $order, $notification) – Whether to change the order status when order review event happens.
• wc_stripe_PAYMENT_METHOD_supported_currencies ($currencies) – The supported currencies for that specific payment method.
• wc_stripe_payment_request_total_label_suffix ($suffix) – Label suffix to use when Payment Request is engaged.
• wc_stripe_payment_request_total_label ($label) – The total label to use when Payment Request is engaged.
• wc_stripe_payment_request_supported_types ($types) – The product types Payment Request supports.
• wc_stripe_hide_payment_request_on_product_page *boolean* – Whether to hide Payment Request button on product detail page.
• wc_stripe_show_payment_request_on_checkout *boolean* – Whether to show Payment Request button on checkout page.
• wc_stripe_payment_request_hide_itemization *boolean* – Whether to show itemizations when using Payment Request.
• wc_stripe_save_to_subs_text ($text) – Text that shows to customers ext to the checkbox to update all active subscriptions with the new saved card.
• wc_stripe_save_to_subs_checked *boolean* – Whether to have the checkbox to update all active subscriptions with the new saved card be checked by default.
• wc_stripe_update_subs_payment_method_card_statuses ($statuses) – Which subscriptions will have their payment method updated if the customer chose that option when adding a new payment method. By default, only the “active” subscriptions will be updated.

SCA/PSD2

What is SCA/PSD2

New requirements for authenticating online payments were introduced in Europe with the second Payment Services Directive (PSD2) as of September 2019. These requirements are referred to as Strong Customer Authentication (SCA) for most electronic payments.

WooCommerce.com works with payment partners, of which Stripe.com is one, to ensure all payment gateway extensions are updated. We have a post that goes through this in more detail. Our Stripe extension implemented this new change as of version 4.2.0.

Failed Payments, Subscription Renewals and SCA

It’s possible that you, the store owner, may receive an “Order #XXX has Failed” email when a subscription is due to renew, or when you are attempting to manually process a subscription renewal (from the Edit Subscription > Subscription Actions > Process Renewal) flow.

Why? The buyer may need to log in to authenticate the payment due to Strong Customer Authentication (SCA) or other authentication requirements by the bank issuing their credit card. If this is the case, there will be corresponding failed order notes:

• “Stripe charge awaiting authentication by user”
  

  

• “Stripe SCA authentication failed.”
  

  

• “This transaction requires authentication.”
  

  

At the same time you receive the “Order #XXXX has Failed” email, the buyer is sent a “Payment authorization needed for renewal“ email asking them to log back in and authorize the payment with an included link.

Once the buyer returns and authorizes payment, the renewal order changes from Failed to Processing, and the subscription becomes Active again.

Frequently Asked Questions

The Stripe payment method is not showing.

In live mode, an SSL certificate must be installed on your site to use Stripe. In addition to SSL encryption, Stripe provides an extra JavaScript method to secure card data.

The Payment Request Button is not showing.

The customer must have a compatible device and payment method in a supported region, otherwise, the option is unavailable.
Please see the support pages for full details:

• Apple Pay support
• Google Pay support

What type of Products can be purchased with the Payment Request Button?

Currently, Simple and Variable products and Subscription products are supported. The buttons won’t show for other Product types (such as Bookings) and won’t work with custom product fields.

Does WooCommerce Subscriptions support using Apple Pay or another Payment Request button?

Yes, Payment Request buttons are supported for Simple and Variable products when using the WooCommerce Subscriptions extension. This functionality will only be enabled when account username and password generation settings are enabled in the Account Creation settings

Product Add-Ons are not charged with Payment Request buttons from a single product page.

Payment Request buttons do not support custom product fields such as Product Add-Ons from single product pages. To avoid orders being placed with no add-ons paid, you can Support Ending for Stripe Modal Checkout. Please vote this feature request on our Ideas Board.

PCI Compliance – what level does the Stripe extension cover?

Since the Stripe extension uses Stripe Elements, this covers Pre-filled SAQ A – please see the Stripe.com Documentation for more details under “Checkout/Elements”.

How can I test Stripe transactions?

When your site is configured using test keys, you will be able to use one of the cards listed under Test card numbers and tokens.

You can view these test transactions on your Stripe Dashboard by using the toggle button to View Test data on the left sidebar at Stripe Dashboard.

Please don’t forget to switch to Live mode when you’re ready to start accepting real payments. You can do that by unchecking the Test mode button at WooCommerce > Settings > Payments > Stripe, and copying the live credentials from Stripe Dashboard.

Can I test Apple Pay?

Yes, please follow the link here for instructions Apple Pay Testing.

Can I test Google Pay?

Yes, save a Stripe test card to your device, and view a product page.

Can I hide the Payment Request button on the single Product page?

You can remove the Payment Request button from the Product page with this filter: add_filter( 'wc_stripe_hide_payment_request_on_product_page', '__return_true' );

Can I hide the Payment Request button on the Cart page?

Yes, you would need to remove the actions:

add_action( 'init', 'remove_stripe_payment_request_from_cart_20200608', 99 );
function remove_stripe_payment_request_from_cart_20200608() {
remove_action( 'woocommerce_proceed_to_checkout', array( WC_Stripe_Payment_Request::instance(), 'display_payment_request_button_html' ), 1 );
remove_action( 'woocommerce_proceed_to_checkout', array( WC_Stripe_Payment_Request::instance(), 'display_payment_request_button_separator_html' ), 2 );
}

Can I show the Payment Request button on the Checkout page?

Yes, although the Payment Button has been removed for clarity on the Checkout Page, a filter has been added to allow you to show this again: add_filter( 'wc_stripe_show_payment_request_on_checkout', '__return_true' );

Can a single customer have multiple subscriptions?

Using the WooCommerce Stripe extension and WooCommerce Subscriptions, you can have multiple subscriptions in your WooCommerce store. It should be noted that WC Subscriptions and the WC Stripe extension don’t use Stripe’s Recurring Plan feature, but instead manage subscriptions in WooCommerce and use token billing for each recurring payment.

How can I change the style of the Stripe Form?

The payment form is served in an iframe method on your site; this provides extra security and is required by Stripe. If you target the iframe with CSS you will find it doesn’t work. What you need to do instead is target the wrapping div element. Here’s some sample CSS that can help you:

Custom CSS to change the style of the Stripe Elements form:

Note: You can style the size, margin, padding, and background color of the boxes.

You can also add custom Stripe Elements styles using the wc_stripe_elements_styling filter. Here’s an example of how you can do that:

How can I translate the placeholders text inside the credit card form?

The placeholders text inside the credit card form is automatically translated by Stripe and cannot be translated by adding new translation strings to your site. Here’s a screenshot showing which is the placeholder text:

By default Stripe detects the locale of the browser and use that as the default. The available locales are ar, da, de, en, es, fi, fr, he, it, ja, lt, lv, ms, nb, nl, pl, pt, ru, sv, zh (see the Stripe documentation for more details).

You can change the locale used with the filter wc_stripe_elements_options. For example, to change it to use the site locale you can use this snippet:

add_filter( 'wc_stripe_elements_options', 'wc_update_locale_in_stripe_element_options' );
function wc_update_locale_in_stripe_element_options( $options ) {
    return array_merge(
        $options,
        array(
            'locale' => 'it',
        )
    );
};

To use the site’s locale as the language, you can instead use this line with the above snippet:

'locale' => get_locale(),

What version of the Stripe API does this extension use?

We try to use the latest possible and we’ll update it whenever we can. Note that you can usually update the API version on your Stripe dashboard without affecting our extension. For clarification, you can find which version we’re using in code on GitHub.

Does this extension support Bitcoin?

As of version 4.1.2 Bitcoin is no longer offered as a payment method. This is due to Stripe dropping support for processing Bitcoin payments on April 23, 2018.

Does this extension support Stripe Connect?

No, not currently. We’re unable to integrate at this time.

Does Stripe use AVS – Address Verification System?

Yes! This is enabled in your Stripe account dashboard and will then work in WooCommerce. See Stripe’s documentation about Avoiding fraud and disputes.

Does Stripe Support Authorization and Capture?

Yes! This is an option in the extension settings. Charges can be captured from within the WooCommerce dashboard. Please note that un-captured authorizations will expire after 7 days.
When the Stripe payment gateway is set to authorize, orders made via Stripe will have the status on hold and the following note:

Change the order status to processing or completed to capture the payment or cancel the order to remove the pre-authorization.

Does Stripe allow refunds inside WooCommerce?

Yes, please see more info on our WooCommerce Refunds documentation page.

Does Stripe Support ACH?

Not currently but Stripe are actively working on this. For more details, please add your votes to our Ideas board.

Why aren’t my subscriptions displayed on the Stripe Dashboard?

WooCommerce Subscriptions does not use the Stripe Subscriptions feature. Instead, it uses a Stripe Customer and Card token and controls the processing of recurring payments.

This avoids any potential issues that could occur by trying to keep two copies of each subscription’s data in sync on two different systems (one in your store and one at Stripe). It also makes it possible for Stripe to support all of WooCommerce Subscriptions’ features, like payment date changes, rather than only those the Stripe Subscriptions allows.

Because of this, you will not see subscriptions created with WooCommerce in your Stripe Dashboard as Subscriptions. This does not mean recurring payments will not be processed. As long as your store is running correctly, recurring payments will be processed correctly and will show up in the Stripe Dashboard as Payments.

Do I need to enable “Saved Card” to process subscriptions?

The WooCommerce Subscriptions extension has its own mechanism for saving credit card details. When a customer buys a subscription product, Stripe will create a special payment token that will use the same credit card details for future subscription payments. Saving the same card again on the customer’s account is not necessary unless you want to allow the customer to reuse the card for other purchases in your store.

How can I change the payment icons used such as Visa, Mastercard…etc?

You can change it via a built-in hook. Here is an example showing the use of the hook changing out the Visa logo.

add_filter( 'wc_stripe_payment_icons', 'change_my_icons' );
function change_my_icons( $icons ) {
        // var_dump( $icons ); to show all possible icons to change.
    $icons['visa'] = '<img src="https://shipyouridea.com/wp-content/plugins/woocommerce/assets/images/icons/credit-cards/visa.svg" />';
    return $icons;
}

How can I change the width of the Payment Request button?

You can target the button div using #wc-stripe-payment-request-button and the “OR” separator using #wc-stripe-payment-request-button-separator. See the Styling documentation for more details.

Am I eligible for Stripe Instant Payouts?

Stripe offers Instant Payouts for immediate access to your funds. Stripe determines your Instant Payouts eligibility. You can check your eligibility by logging into the dashboard and checking for the `Pay out funds instantly` button on the Balance page.

Pricing:

1% of the payout amount

Eligibility:

Merchants who have been processing for at least 6 months with Stripe may become eligible.

New Stripe users are not immediately eligible for Instant Payouts. If you’re not eligible for Instant Payouts, you can request access at instantpayouts@stripe.com.

Troubleshooting

Root Relative URLs

There are known issues with the Root Relative URLs plugin. You will not be able to use this with Stripe.

I get an error when placing an order telling me to enable JavaScript.

This error may be caused by non-standard/poorly coded themes and JavaScript (JS) issues. Common issues include:

1. Javascript errors on the checkout page – To view the error, open up your browser error console (in Chrome: View > developer > javascript console) and look for red errors. This should indicate where the error is located and lead you to the problem, i.e., loading jquery wrong
2. Failing to load scripts – Stripe loads 2 JS files which it needs to function. If these are not loaded you will see errors. The most common reasons for not loading are:
   • A theme missing wp_head() or wp_footer() calls
   • Old overridden template files from WooCommerce inside your theme
   • Loading headers/footers in a non-standard way. WooCommerce uses get_header()’s get_header action to init the checkout and load scripts. If you are not using get_header() you either need to do so, or you need to trigger the get_header action manually using: do_action( ‘get_header ); in your custom header loader.

Apple Pay – I am getting this error “Error: Unable to copy domain association file to domain root”

That could mean your server configuration is not allowing files/paths to be written in that location. You would have to manually do this by following the step outlined here.

Apple Pay – I am getting this error “Error: Unable to verify domain – Bad Request”

Try manually doing this by following the step outlined here.

I’m getting an API error.

Ensure that you have entered the correct keys. If you are in Live Mode, you should have entered live keys (not test keys).

• If you are using test mode, keys are prepended with sk_test and pk_test
• If you are using live mode, keys are prepended with sk_live and pk_live

I’m seeing the error “Could not find payment information.”

This usually means that test mode is still enabled while using live keys, or that test keys are being used in live mode. For more details, please check the Stripe logs under WooCommerce > Status > Logs

Styling

We have full developer documentation for how to style the WooCommerce Stripe payment gateway payment card fields:

Questions and Feedback

Have a question before you download? Please fill out this pre-sales form.

Already using Stripe and need some assistance? Get in touch with a Happiness Engineer via the Help Desk.

The post Stripe first appeared on CODIBU.