Support Home > Utilities > Recurring Payments Block

Recurring Payments Block

The Recurring Payments Block lets you add a payment button specifically for recurring donations, using Stripe as the payment gateway.

The following video shows the process of adding a Recurring Payments block and setting up a payment button:

Requirements

To use the Recurring Payments Block, you will need to connect to Stripe.

You will also need a paid Jetpack plan.

Adding the Recurring Payments Block

You can add the Recurring Payments Block by searching and/or selecting it from the Jetpack section of the block selector:

See Jetpack Blocks for detailed instructions on adding blocks.

How to set up and manage recurring payments

For full instructions on how to connect your Stripe account, add new buttons, view related fees and manage your buttons, visit our WordPress.com support article on this topic.

Troubleshooting

If you’re having any trouble with the Recurring Payments Block, please check the ‘Tips’ section at the bottom of this WordPress.com support page. If your question is not answered there, please contact support for help.

Privacy Information

This feature is deactivated by default, and unlocking it requires an upgrade to a paid Jetpack plan. Because this is not a formal module within Jetpack, there is no way to deactivate it entirely. If you have access to this feature but are not actively using it, there is no code running on your site that’s interacting with it.

Please note that payments are processed via Stripe, so we also recommend reviewing its privacy policy and documentation.

Data Used
Site Owners / Authors

 

In order to process a payment, the Stripe account ID, Amount being charged ( from product information ), Currency ( from product information ) is sent to Stripe.

Site Visitors / Purchasers

 

To facilitate new signup and renewals, the following is sent to Stripe (governed by Stripe TOS): Name, Credit Card number, CVV, Expiry date.

Note – the credit card details are not stored by us – this data is collected and stored by Stripe. WordPress.com systems are fully PCI compliant.

Activity Tracked
Site Owners / Users

 

Email-related events (you will receive an email from Jetpack when a payment has been completed) are tracked – sends, opens, and clicks.

Site Visitors / Users

 

We plan to store anonymized analytics about which step in the purchase process was reached for the purpose of improving the user experience.

Cookies may be stored to implement content blocking in the future.

Data Synced (Read More)
Site Owners / Users

 

We sync the following meta around payments/products: all information regarding new products being created / edited.

We also sync the following meta from Stripe with Oauth connection: Account ID, secret and public keys necessary to facilitate the payment, country, timezone, default currency, and the account name.

Site Visitors / Users

 

We create new WordPress.com account for the user, or use the account associated with the email customer gives us. An explanation of WordPress.com data used can be found here.

History of signups and billing facilitated via this feature is stored on WordPress.com servers for accounting and subsequent renewal purposes.

For the purpose of renewing subscription, on our servers we store: Safely encrypted Stripe ID of the credit card connected to subscription, User id that initiated the purchase, Details about the product, Payment history for the subscription, Last 4 digits of the credit card and the brand – what is known in the industry as “safe details”.

Also, we connect the ID of the credit card to the WordPress.com user id, which allows for one-click payments on other subscription products sold on WordPress.com network.

  • Table Of Contents

  • Categories

  • Contact Us

    Need more help? Feel free to contact us.