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.

Braintree for WooCommerce (formerly PayPal Powered by Braintree)lets you accept credit cards and PayPal payments on your WooCommerce store via Braintree. Customers can save their credit card details or link a PayPal account to their WooCommerce user account for fast and easy checkout.

Braintree for WooCommerce includes full support for WooCommerce Subscriptions and WooCommerce Pre-Orders for both the credit card and PayPal gateways! Click here for more information about Subscriptions and Pre-Orders compatibility.

Requirements

• PHP 5.4+ (you can see this under WooCommerce > Status)
• WooCommerce 2.6+
• An SSL certificate
• A Braintree Direct account
• cURL support (most hosts have this enabled by default)

Installation

1. Ensure your store meets the plugin requirements.
2. Download the extension from your WooCommerce dashboard.
3. Go to Plugins > Add New > Upload and select the ZIP file you just downloaded.
4. Click Install Now and then Activate.
5. Click Configure and read the next section to learn how to setup the plugin.

Getting started

Follow the steps below to connect the plugin to your Braintree Direct account:

1. 1. Login to your Braintree Control Panel.
   2. Select the gear icon in the upper right corner and click API.

1. 1. From here, you can click View to view an existing set of API keys or Generate New API Key to create a new set.

1. 1. When viewing keys, copy the Public Key, Private Key, and Merchant ID.

1. 1. Now, login to your WooCommerce site and go to WooCommerce > Settings > Payments and select either of the Braintree gateways.
   2. Paste the copied API keys into the associated fields under the Connection Settings.
   3. Click Save changes.

That’s it! You’re ready to start accepting payments. Keep reading if you want to tweak settings and customize the checkout process.

Credit card settings

You can configure the following settings for the Braintree for WooCommerce credit card gateway:

• Enable / Disable: Allow customers to use this gateway to checkout.
• Title: The text shown for the payment during checkout and on the Order Received page.
• Description: The text shown under the gateway’s title during checkout. Limited HTML is allowed. If you enable test mode, this section will also display a notice along with test credit card numbers.
• Card Verification (CSC): Require customers to enter their card security codes when checking out.
• Transaction Type: Controls how transactions are submitted to Authorize.Net. Defaults to “Charge” to automatically capture payments. Click here to learn more about capturing payments.
• Charge Virtual-Only Orders: If Transaction Type is set to “Authorization”, enable this to automatically capture charges for orders with only virtual products. For downloadable products, this will grant downloads access right away.
• Capture Paid Orders: If Transaction Type is set to “Authorization”, enable this to automatically capture charges when orders move to a paid status.
• Accepted Card Logos: Determines which card logos are displayed during checkout. This has no impact on which cards are accepted by your merchant account.
• Tokenization: Let customers save their payment methods for future use at checkout. The Vault must be enabled in your Braintree account to use tokenization. This is required for Subscriptions or Pre-Orders.
• Detailed Decline Messages: Display detailed messages to customers to provide reasoning for declines instead of a generic error message when possible. Click here to read more about detailed decline messages.
• Debug Mode: Enable when you’re having issues processing transactions. You can choose to log API requests directly on the checkout page, save them to the WooCommerce > Status > Logs page, or both. As a best practice, please do not enable this setting unless you’re having issues with the plugin.
• Environment: Switch between “Production” and “Sandbox” credentials. Set to “Production” to process payments. Enable “Sandbox” to send transactions to your Braintree sandbox account. Click here to sign up for a Braintree sandbox account.
• Share connection settings: If using the credit card and PayPal gateways, select this setting to share credentials between the gateways so you don’t have to enter them twice.
• Merchant ID, Public Key, Private Key: API key credentials required to connect the plugin to Braintree. Click here for instructions on locating those keys.
• Merchant Account IDs: Use if you have different merchant accounts for multi-currency support. Click here to read more about Braintree multi-currency.
• Dynamic Descriptors: Determine how your store is represented on customer credit card statements. Click here to read more about dynamic descriptors.
• Fraud Settings: Optionally select the fraud tool you’d like to use for your payments. Click here to read more about fraud and verification tools.
• 3D Secure: Optionally enable different 3D secure verifications if enabled under your Braintree account. Click here to read more about 3D secure.

PayPal settings

To use the Braintree PayPal gateway, you must have PayPal enabled in your Braintree account under Settings > Processing.

If you want to use PayPal without credit card processing, click here to read more about configuring this correctly.

You can configure the following settings for the Braintree for WooCommerce PayPal gateway:

• Enable / Disable: Allow customers to use this gateway to checkout.
• Title: The text shown for the payment during checkout and on the Order Received page.
• Description: The text shown under the gateway’s title during checkout. Limited HTML is allowed.
• Button Color: Choose the color of the “Pay with PayPal” button. You can see how this will look under the Preview section.
• Button Size: Choose the size of the “Pay with PayPal” button. You can see how this will look under the Preview section.
• Button Shape: Choose the shape of the “Pay with PayPal” button. You can see how this will look under the Preview section.
• PayPal Credit: For US merchants, enable the PayPal Credit button beneath the standard “Pay with PayPal” button.
• Buy Now on Product Pages: Enable to add the “PayPal Buy Now” button on product pages. Click here to read more about this express checkout option.
• Enable Cart Checkout: Enable to allow customers to checkout with PayPal from the Cart. Click here to read more about this express checkout option.
• Transaction Type: Controls how transactions are submitted to Authorize.Net. Defaults to “Charge” to automatically capture payments. Click here to learn more about capturing payments.
• Charge Virtual-Only Orders: If Transaction Type is set to “Authorization”, enable this to automatically capture charges for orders with only virtual products. For downloadable products, this will grant downloads access right away.
• Capture Paid Orders: If Transaction Type is set to “Authorization”, enable this to automatically capture charges when orders move to a paid status.
• Tokenization: Let customers link their PayPal account for future use at checkout. Requires Advanced Fraud Tools to be enabled on your Braintree account. Click here to learn more about fraud tools and setup. This is required for Subscriptions or Pre-Orders.
• Detailed Decline Messages: Display detailed messages to customers to provide reasoning for declines instead of a generic error message when possible. Click here to read more about detailed decline messages.
• Debug Mode: Enable when you’re having issues processing transactions. You can choose to log API requests directly on the checkout page, save them to the WooCommerce > Status > Logs page, or both. As a best practice, please do not enable this setting unless you’re having issues with the plugin.
• Environment: Switch between “Production” and “Sandbox” credentials. Set to “Production” to process payments. Enable “Sandbox” to send transactions to your Braintree sandbox account. Click here to sign up for a Braintree sandbox account.
• Share connection settings: If using the credit card and PayPal gateways, select this setting to share credentials between the gateways so you don’t have to enter them twice.
• Merchant ID, Public Key, Private Key: API key credentials required to connect the plugin to Braintree. Click here for instructions on locating those keys.
• Merchant Account IDs: Use if you have different merchant accounts for multi-currency support. Click here to read more about Braintree multi-currency.
• Dynamic Descriptors: Determine how your store is represented on customer credit card statements. Click here to read more about dynamic descriptors.

Multi-currency setup

If you want to accept payments in multiple currencies, you can add credentials for different merchant accounts. When used alongside a currency switcher plugin, you can then route payments to the different accounts based on the currency. We recommend Aelia Currency Switcher (requires purchase), which works seamlessly with Braintree for WooCommerce.

Follow the steps below to add more merchant accounts to accept multi-currency payments:

• Install and activate a currency switcher plugin, such as Aelia Currency Switcher.
• Go to WooCommerce > Settings > Payments and select the Braintree gateway you want to update.
• Under the Merchant Account IDs section, select the currency for this merchant account from the drop-down menu and click Add merchant account ID.
• Enter the merchant account ID in the newly created field.
• Repeat steps 3 and 4 as needed for each currency / merchant ID.
• Click Save changes.

Dynamic Descriptors setup

Dynamic Descriptors let you control how your charges appear on customer credit card statements for specific purchases. This can help you avoid customer disputes / chargebacks due to confusion or non-recognition. Dynamic Descriptors must be enabled by your Braintree representative.

Braintree has very specific formatting requirements for these fields, so we highly recommend running a test transaction to confirm your format is valid.

Once enabled by Braintree, you can configure Dynamic Descriptors in the gateway settings. There are three format options for the Name field – please note that components must be separated by an asterisk:

• • [3 letters]*[up to 18 letters]: 3 letters to represent the company name, up to 18 letters to represent the product name. For example, SKY*WOOCOMMERCEPLUGINS.

• • [7 letters]*[up to 14 letters]: 7 letters to represent the company name, up to 14 letters to represent the product name. For example, SKYVERGE*WOOCOMMPLUGINS.

• • [12 letters]*[up to 9 letters]: 12 letters to represent the company name, up to 9 letters to represent the product name. For example, SKYVERGECORP*WCPLUGINS.

For the Phone field (optional), you must enter exactly 10 characters. This field can only contain numbers, dashes, parentheses, or periods.

For the URL field (optional), you may enter your URL in 13 characters or less.

Fraud and verification tools

By default, Braintree includes Basic fraud verification tools. However, there are more sophisticated fraud prevention tools – Advanced or Kount Direct – which you can optionally enable through your Braintree account.

We recommend enabling Advanced fraud tools, since they provide additional protection and are easily enabled. Click here to read more about the available fraud tools.

To turn on Advanced Fraud Tools, login to your Braintree account, go to Settings > Fraud Management and enable Advanced Fraud Tools. You can then update the gateway settings.

To enable Kount Direct fraud tools, contact your Braintree representative. They can provide the Kount Merchant ID required in the gateway settings.

3D Secure

If you’d like to use 3D Secure verification tools like Verified by Visa, you must first contact your Braintree representative. You can then configure 3D Secure in the payment gateway settings with two fields:

• Level: Choose “Standard” to accept any payments not explicitly rejected during verification, or “Strict” to only accept payments that explicitly pass. If set to “Strict”, failures caused due to connection / availability errors will be rejected as well.
• Supported Card Types: Determine which card types 3D Secure validation should apply to.

Using PayPal without credit cards

If you’d like to use PayPal without credit cards, you’ll need to pay careful attention to a few settings to ensure everything is configured correctly. You have two options for how to set this up, based on whether you want to allow customers to link their PayPal account for future purchases.

Using PayPal for one-time purchases

You can let customers use Checkout with PayPal for one-time purchases without configuring anything for the Braintree credit card gateway, and leave the credit card gateway disabled. However, you cannot enable tokenization with this setup, so customers can’t link their PayPal account to WooCommerce for future purchases.

This setup is not compatible with Subscriptions or Pre-Orders.

Using PayPal with linked accounts

By using the Checkout with PayPal and PayPal Vault workflows, you can let your customers link their PayPal accounts to your store for faster future purchases and for Subscriptions / Pre-Orders support.

This requires a bit of extra setup since Braintree requires using Advanced Fraud Tools with the PayPal Vault. Instead of setting up everything only in the Braintree PayPal gateway settings, follow the steps below:

1. Go to WooCommerce > Settings > Payments and select the Braintree (Credit Card) gateway. You can leave this gateway disabled to hide it at checkout.
2. Enter your API keys under the Connection Settings.
3. Configure the Fraud Tool setting to “Advanced”. Click here for instructions on ensuring advanced fraud tools are enabled for your Braintree account.
4. Click Save changes.
5. Click Payments and select the Braintree (PayPal) gateway and configure the following settings:
   • Enable the gateway.
   • Enable Share connection settings.
   • Enable Tokenization.
6. Click Save changes.

This ensures that advanced fraud tools are available so you can use the PayPal Vault.

Support Apple Pay

You can support Apple Pay payments with Braintree for WooCommerce with some additional configuration steps.

1. 1. Follow these instructions to enable Apple Pay in your Braintree account.
   2. Next, follow these instructions to register your domain for Apple Pay.
   3. You may then enable Apple Pay on your site by going to WooCommerce > Settings > Payments > Apple Pay.

Managing orders

As a site administrator, you can use the Braintree for WooCommerce gateway to manually capture charges and automatically refund / void transactions as needed.

Capture charges

If the gateway’s Transaction Type is configured to “Authorization”, you can manually capture these payments from the WooCommerce Orders page. Click here to read more about capturing charges.

Automatic refunds

You can process refunds for both the credit card and PayPal gateways directly in WooCommerce without needing to log into your Braintree control panel. Click here to read more about issuing automatic refunds from WooCommerce.

Void transactions

You can void transactions directly in WooCommerce in the following circumstances:

• If the Transaction Type is set to “Authorization”, you can void when the transaction has been authorized but not yet captured.
• If the Transaction Type is set to “Charge”, you can void when the transaction has not yet been settled (i.e. funds haven’t been transferred from the customer’s account to your Braintree account).

Braintree does not accept partial voids. If a transaction is no longer eligible to be voided, you must refund the order. Click here to read more about voiding transactions in WooCommerce.

Gateway features

Your customers can take advantage of the following features when your site uses Braintree for WooCommerce.

Express checkout

Braintree for WooCommerce offers a few tools to help expedite PayPal checkout for your customers – Cart Checkout and Buy Now buttons.

When the Enable Cart Checkout setting is enabled, a PayPal Checkout option will be offered on the cart page. This lets customers log into PayPal, set up account details, and proceed to checkout with these details prefilled in the billing / shipping sections – all they need to do is click Place order to complete the purchase.

When the Buy Now on Product Pages setting is enabled, a Buy Now button is displayed on product pages, which lets customers make purchases via PayPal without going through the standard cart / checkout flow.

Saved payment methods

When Tokenization is enabled, customers can save payment methods during the checkout process or from their My Account area. This lets them quickly save payment details or link their PayPal account for faster future purchases and also lets your site support Subscriptions and Pre-Orders. Click here to read more about managing saved payment methods.

Frequently asked questions

Q: Does Braintree for WooCommerce work with WooCommerce Subscriptions or WooCommerce Pre-Orders?
A: Yes! Both the credit card and PayPal gateways include full Subscriptions and Pre-Orders support. Please note that in order to use these plugins with Braintree, you must:

• Have the Braintree vault enabled in your Braintree account for credit card transactions
• Have the PayPal Vault enabled for PayPal transactions
• Enable the Tokenization setting for the credit card and / or PayPal gateways
• For PayPal transactions, enable Advanced Fraud Tools in your Braintree account and configure that in the PayPal gateway settings

Q: Why don’t my subscriptions display inside the Braintree control panel?
A: Braintree for WooCommerce doesn’t use Braintree’s subscription handling – instead, it tokenizes the customer’s payment method and then lets the Subscriptions plugin handle charging the payment method. This is a far more flexible method and supports many features not provided through Braintree’s control panels, such as changing payment dates and amounts.

Q: How does Braintree for WooCommerce impact my site’s PCI compliance?
A: Braintree for WooCommerce is PCI DSS v3.0 SAQ-A compliant and uses Braintree’s hosted fields to process payments. Sensitive payment information is never passed through your site server, as it’s tokenized client-side before it’s sent to Braintree. The hosted fields aren’t quite the same as Braintree’s v.zero SDK, but works in a similar way and is just as secure. We use hosted fields since it offers better customization options for the payment form, letting you create a more intuitive checkout.

Q: My credentials are correct, but I still don’t see PayPal at checkout. What’s going on?
A: To use PayPal, you’ll first need to enable PayPal in your Braintree account – login to your account, go to Settings > Processing, and enable the PayPal payment method.

Q: Why do I see a “customer with id xxxxxxxx not found” error at checkout?
A: If you’ve recently switched Braintree accounts (e.g. from Sandbox to Production), you’ll need to clear the Braintree customer ID in the user’s profile on the Users page.

Q: How do I use Braintree’s Address Verification System (AVS) with this plugin?
A: You can enable AVS in your Braintree account. Click here for instructions.

Q: What countries can I use Braintree for WooCommerce in?
A: You can use Braintree for WooCommerce in any countries where Braintree accounts are available!

Q: I set up the gateway with my different merchant accounts, but processing is still going through a single account. What’s gone wrong?
A: This plugin can switch accounts based on payment currency, but it can’t handle switching the currency itself. If you want to use multiple currencies, we recommend using Aelia Currency Switcher(requires purchase) since it’s compatible with Braintree for WooCommerce – the gateway will then handle routing the payments based on their selected currency. Click here to read more about accepting multiple currencies with Braintree for WooCommerce.

Q: Does Braintree support Venmo or Apple Pay?
A: Venmo is mobile-only, which means it’s not available for eCommerce / website payments. Apple Pay is supported as of version 2.2.0! Click here to learn more about using Apple Pay.

Troubleshooting

Having a problem? Follow these steps to make sure everything is setup correctly:

• Please ensure that your site meets the plugin requirements.
• Check the FAQs to see if they address your question.
• Confirm that your API credentials are correct.
• Confirm that you’re not using production API credentials when the gateway’s Environment is set to “Sandbox” (or vice versa).
• Enable Debug Mode and review the errors codes/messages provided by Braintree under WooCommerce > Status > Logs. In some cases, such as a transaction being held for review or declined, the plugin cannot change the issue and it must be resolved in your Braintree account. If the error code indicates an issue with the plugin, please submit a support ticket and include the logs to help us troubleshoot.

Theme issues

Braintree for WooCommerce loads important javascript on the checkout page. Some themes (particularly those based on the Starker base theme) cause conflicts with this javascript. There are two primary issues:

• The theme lacks the do_action ( ‘get_header’ ); call when loading the checkout page. The Starker theme (and any child themes) is an example of this issue. This action must be added to the theme, or we recommend using a WooCommerce-compatible theme like Storefront instead.
• The theme has incorrectly modified the review-order.php template. The Braintree javascript requires the order review div to have the order_review class. When a theme has modified the template and changed or removed that div, this trigger can’t be bound and you’ll encounter errors. To fix this, ensure that your review-order.php template is up-to-date and hasn’t been incorrectly modified.

Questions & support

Need some assistance? Please check out our troubleshooting tips and frequently asked questions for common issues or contact support via the help desk if you need more help.

The post Braintree for WooCommerce first appeared on CODIBU.

• Klarna Payments is available in Australia, Austria, Belgium, Canada, Denmark, Germany, Finland, France, Italy, Netherlands, Norway,  New Zealand, Sweden, Spain, Switzerland,  United Kingdom and United States.
• You need an agreement with Klarna to be able to use this plugin.
• WooCommerce 3.0 or newer is required.
• PHP 5.6 or higher is required.

Related documentation

• v2 to v3 transition guide
  Step-by-step guide on how to switch from old plugin to Klarna Payments for WooCommerce plugin.
• Order management
  Read more about how to manage Klarna orders directly from WooCommerce.

Required WooCommerce settings

• Make sure that you have enabled pretty permalinks in your WordPress installation. Otherwise callbacks from Klarna back to your store won’t work and orders will not be updated with the correct order status/information.
• To get the order total to match between WooCommerce and Klarna you need to configure WooCommerce to display prices with 2 decimals. More information about displaying of prices and how it can cause rounding issues can be found in this article.

Configuration

1. Go to: WooCommerce > Settings > Payments > Klarna Payments.
2. Enable Klarna Payments by checking the Enable Klarna Payments checkbox.
3. Title – Payment method title. Changes what the payment method is called on the order received page as well as the email that is sent to the customer. The Title is not customizable by merchants within Woo checkout, as the title is set by Klarna.
4. Description – Enter the description of the payment method displayed in the checkout.
5. Test mode – Tick the checkbox if you make purchases using a test account.
6. Logging – Logging events in the module. The log can be found by navigating to → WooCommerce → System Status → Logs.
7. What is Klarna link – Tick the checkbox if you want to float the What is Klarna link to the right.
8. Product URLs – Tick the checkbox if you want to send product and product image URLs to Klarna.
9. Add Klarna Urls to order email – This will add Klarna urls to the order emails that are sent. You can read more about Klarna urls here.
10. Customer type – Select the customer for the store (B2C or B2B).

Country settings

Each Klarna country has its own set of country specific settings. By adding merchant credentials to a specific country you also enable Klarna Payments as an available payment method for that country. Note that you need an agreement with Klarna for each country enabled and your store needs to be able to process purchases in the local currency.

1. Description – Add a description for the specific country. If no description is added, the default description will be used.
2. Title – Add a title for the specific country. If no title is added, the default title will be used.
3. Production username – Username that you received from Klarna.
4. Production password – Password that you received from Klarna
5. Test username – Username for test purchases that you received from Klarna (if you have applied for a test account).
6. Test password – Password for test purchases that you received from Klarna (if you have applied for a test account).

Iframe settings

With the iframe settings section you have the possibility to alter the appearance of the Klarna Payments Widget displayed in the checkout. Here you can change things like background colors, button colors and text colors.

Compatibility with themes & plugins

• Klarna Payments should work with most themes. However, the plugin is only tested with the Storefront theme and we do not guarantee that it will work with other themes. Common situations when errors occur are:
  – Themes/plugins with customized template files for WooCommerce checkout page.
  – Themes/plugins that removes standard checkout fields.
  – Themes/plugins that modifies the checkout into a multi step checkout.
• The plugin and Klarna only handle product quantity that is specified as an integer. For instance you can’t send 1.5 as the product quantity to Klarna. If you sell products where you charge by length or dimension we recommend that you use the Measurement Price Calculator plugin.
• WooCommerce does not offer multi currency support. This can be handled via several different plugins. This plugin is compatible with the Currency Switcher for WooCommerce plugin from Aelia. We do not guarantee that other multi currency plugins will work together with the Klarna plugin.

Krokedil and Klarna do not offer help with adapting your theme or plugin within regular support.

Troubleshooting↑ Back to top

• If Klarna Payments isn’t displayed as an available payment method in checkout page make sure customer billing country is one of countries you have entered Klarna Payments credentials for and that selected currency matches customer billing country.

Go live

When the installation is done and you are ready to go live you need to contact Klarna integration support. Klarna will then verify the integration before the shop goes live.

The post Klarna Payments – introduction first appeared on CODIBU.