Introducing the Simple Payment Widget

Since the introduction of the Simple Payment Button, we’ve been looking for more ways to streamline payments on WordPress.com and Jetpack-enabled sites. Today, we’re introducing a new variant of the Simple Payment Button, available to WordPress.com Premium and Business plan subscribers and to Jetpack sites on Premium and Professional plans.

Take payments anywhere on your site with the Simple Payment Widget

Use the Simple Payment Widget to add a quick payment option to the sidebar or footer of your WordPress.com or Jetpack site. (If you have Jetpack site, make sure its running version 6.3.3 or higher.) Then add the widget to your site via the Customizer, by going to Personalize → Customize → Widgets.

Screen Shot 2018-08-06 at 11.40.15

Using the Customizer

You’ll be able to select an existing Simple Payment Button or create a new one to add to your sidebar, header, or footer.

Screen Shot 2018-08-06 at 15.06.55

Simple Payment Widget on a Site’s Footer

The widget also gives you the ability to manage all of your products or services from the Customizer — set pricing, add images, and write product description right in the widget settings:

Screen Shot 2018-08-07 at 16.05.10

Edit a Product on the Customizer

Once you’ve create multiple payment buttons, you can choose between them any time you add the Simple Payment Widget. And any button you create or edit via the Customizer is instantly available to use on the rest of your site, on any post or page.

Screen Shot 2018-08-07 at 15.11.30

Add a product created on the Customizer to any page or post.

We hope you enjoy this new feature and make the most of it. Let us know what you think in the comments! And if you run into any issues setting up your new widget, take a look at the support documentation or reach out to support.

Altre ricette simili a questa:

VAI ALLA RICETTA


Nessun commento...

Inserisci un Commento

Devi effettuare il Login per inserire un commento.

[an error occurred while processing this directive]
[an error occurred while processing this directive]