Donations Block

The Donations block lets you add a payment button to any post or page for donations, tips, and other contributions, using Stripe as the payment gateway.

To use the Donations block, you will need to connect to Stripe. Your site must also have an active Jetpack Security or Complete plan.

Adding the Block

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

See Jetpack Blocks for detailed instructions on adding blocks.

After adding the Donations block, you can set it by One-time donation, Recurring Monthly, or Yearly donations.

How to set up and manage payments

For full instructions on connecting your Stripe account, adding new buttons, viewing related fees, and managing your buttons, visit our WordPress.com support article on this topic.

Block Toolbar

Click the block to display the toolbar. You can use the currency selector in the toolbar to select the currency for your buttons.

Privacy Information

This feature is deactivated by default, and unlocking it requires an upgrade to a Jetpack Security or Complete plan. Because this is not a formal feature 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 recommend reviewing its privacy policy and documentation.

Data Used
Site Owners / Users To process a payment, the Stripe account ID, Amount being charged ( from product information ), and Currency ( from product information ) is sent to Stripe.	Site Visitors To facilitate new signup and renewals, the following is sent to Stripe (governed by Stripe TOS): Name, Credit Card number, CVV, and 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 We plan to store anonymized analytics about which step in the purchase process was reached to improve 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 We create a 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. To renew the subscription, on our servers, we store the Safely encrypted Stripe ID of the credit card connected to the subscription, the 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 credit card ID to the WordPress.com user id, allowing for one-click payments on other subscription products sold on the WordPress.com network.