Use the Web Payments API and Google / Apply Pay to vastly improve your checkout process!

4.0.0 2023-04-12 14:02 UTC

This package is auto-updated.

Last update: 2024-04-12 16:11:30 UTC


Web Payments

Web Payments for Craft Commerce

Use the Web Payments API and Apply & Google Pay to vastly improve your checkout process!



After installing the plugin:

  1. Create a Stripe payment gateway.
  2. Select the gateway in the plugin options.
  3. Register your domain with Stripe and Apple Pay (Simply add your domain here).
  4. Output the button where ever you want using the template tag below.
  5. ???
  6. Profit.

{{ craft.webPayments.button(options) }}

Place this twig where you want the payments button to appear.


Pass a twig object as the only parameter to configure the button.


An array of items to buy. Use this OR cart.


The ID of the purchasable.


The Qty being purchased.


A Craft Commerce Order (i.e. the current cart). Use this OR items.


A boolean or string. If true a shipping address will be required. Can also be set to one of: 'shipping', 'delivery', 'pickup', true, false (default). This will also change how the UI refers to the shipping of the products. For example, in English speaking countries you would say "pizza delivery" not "pizza shipping". Setting this to true will default the working to "shipping".


An array of additional details to request. Any of: name, email (email is always collected, so you don't need to add it), phone.


An object of events to trigger once the payment is complete.


A URL to redirect to once the payment is completed. Can include {number}, which will output the order number.


JavaScript that will be executed once the payment is complete. Has access to the cwp object. Currently this only has cwp.number (the order number).


The variable the button will be set to in JS. Useful if you want to dynamically update the items in the virtual cart.


Customize the appearance of the button:

    type: 'default' | 'donate' | 'buy', // default: 'default'
    theme: 'dark' | 'light' | 'light-outline', // default: 'dark'
    height: '64px', // default: '40px', the width is always '100%'


{{ craft.webPayments.button({
    items: [
            qty: 1,
            options: {
                giftWrapped: 'yes',
    requestShipping: 'delivery',
    js: 'window.pay_item_' ~,
}) }}
{{ craft.webPayments.button({
    cart: craft.commerce.carts.cart,
    requestDetails: ['name', 'phone'],
    onComplete: {
        redirect: '/thanks?number={number}',
        js: 'window.paymentCompleted(cwp.number);',
}) }}

Dynamic Updating

You can dynamically update the button via JS.

Use the js option to define the variable you want the button to be bound to:

{{ craft.webPayments.button({
    items: [{ id: 1, qty: 1 }],
    js: 'window.payButton',
}) }}

You can then get the current items and update them:

const items = [ ...window.payButton.items ];
items[0].options = { giftWrapped: 'yes' };
window.payButton.items = items;

You can't update the items directly (i.e. window.payButton.items[0].id = 2). The items are immutable, and therefore must be set to a new array if you want to update them. Above we are cloning the existing items into a new array before modifying them.

If you passed in a cart you can simply call refresh() to update the button with the latest contents of the cart.


Note that you can't update the button while the payment dialog is active.

If you need to reload the button (i.e. if the DOM has changed) you can use the reload() function.

window.payButton = window.payButton.reload();

reload() will return a new instance of the button, so you'll want to replace your existing variable with that new instance.


  • When using a cart, actually use the cart to keep fields / options persistent
    • Remove cart option (if items isn't set, use active cart)
    • Remove clear cart option
  • Support line item options when using items
  • On payment complete event (i.e. clear active cart, redirect to thanks)
  • JS hooks to update items (if not using commerce cart)
  • JS hook to refresh cart data (if using commerce cart)
  • Option to use default Apple / Google Pay buttons (rather that Stripe's button)
  • Use billing address from Stripe (don't set billing address to shipping)
  • Make shipping address optional
  • Settings:
    • Select Stripe gateway
    • Button config defaults
    • Map request details (name, phone) to order fields
  • Write setup instructions
  • Browser test JS
  • Test with Commerce Lite
  • Add flag to order marking this as an order completed via web payments
  • Add subscription support