GDPress vs Payment Page – Stripe Payment Forms for Donations, Subscriptions & Recurring Payments

GDPress is providing tools for privacy and more. Major features in GDPress include : a privacy request form a menu in the admin_bar to see at once confirmed privacy requests and since version 2.0 a set of tools to help you comply with GDPR * a set of protection and wellness tools, because protecting personal data starts with a healthy and protected installation to prevent potential data breach. * a RoPA assistant to help you building your Records of Processing Activities – a GDPR obligation (Article 30). * a logging of all events related to export/erase requests by/for the data subject (see settings page). * a specific wp role for dpo. * and a dedicated Privacy/GDPR/ISO27701 dashboard for your d.p.o. ! GDPR compliancy is a never ending process. Technical Details n/a Privacy GDPress is not calling any external web services and is not using any external software other than WordPress core. GDPress stores events related to the data subject and core privacy processes if archive setting is set. Archives are under the authority of the Data Protection Officer for legal purpose ONLY. They are retrieved to the data subject, but not deleted. Accountability/Auditability These are legal obligations in GDPR. In front of your local data protection authority or a judge : * You are accountable of your actions to reach GDPR compliancy and must prove it (activating this plugin is not enough). * If sued, you will have to provide some evidence : you acted lawfully and replied to the request of the data subject (archive all activities for Legal Purpose is allowed in GDPR and must be declared in your Records of Processing Activities). Other Major Obligations Records of Processing Activities, expecting WordPress team to publish it for core. And for any theme or plugin, adding a new Privacy Section in readme.txt is a must do. Communication of a personal data breach to the data subject (and to your local D.P.A.) Privacy by design This concept is in GDPR too. In wp, Privacy is a component like Gutenberg, Admin, wp-cron … Privacy by design is or should be declined and included in ALL wp components. Should all components publish their “Privacy Section” just like the above recommandation for themes and plugins ? Pending Questions Privacy settings in core : only one setting on a unique page that cannot be amended (no hook) : the privacy policy page any privacy request is a personal data and should be retrieved to the data subject removing an export request do not delete the export file (security issue, potential data breach) external processors to be identified (privacy by design) Gutenberg blocks coherence with embed handlers and oembed providers as set on the server side (privacy by design) oEmbed responses cached in transients (no more postmeta html cached) for blog posts or oembed providers (privacy by design) ability to remove blocks in Gutenberg such as “/map” for Mapbox (privacy by design) future “Icon” component : from Dashicons to svg (privacy by design) Nowadays, emails such as “θσερ@εχαμπλε.ψομ” are valid but rejected by wp function is_email() (privacy requests rejected) Web standards should apply and this can be a legal issue : one of the “variety of privacy issues around the world” !

Payment Page builds Stripe payment forms on WordPress without requiring WooCommerce. Create one-time or recurring forms, connect an eligible Stripe account, and publish a form with the plugin shortcode or native Elementor widget. 🎯 BUILT FOR Freelancers invoicing clients and collecting retainer deposits Coaches & Consultants taking deposits and selling session packages Yoga, Fitness & Wellness studios selling memberships and class packs Nonprofits accepting one-time and recurring donations Agencies invoicing monthly maintenance and managing client billing Creators & Educators selling courses, gated content, and subscriptions ⚡ KEY FEATURES One-page Stripe forms — cards, Apple Pay, Google Pay, SEPA Direct Debit, Alipay, and WeChat Pay, subject to account, country, currency, browser, device, and recurring-payment eligibility 22 payment-form setting templates — 10 bundled in the plugin and 12 delivered from the public template endpoint 11 separate Elementor full-page layouts — page designs are distinct from the payment-form setting templates Stripe Connect onboarding — start the released OAuth onboarding flow from WordPress without copying API keys into the plugin settings One-time and recurring plans — one-time, daily, weekly, monthly, quarterly, every six months, annually, and every three years Donation forms & custom amounts — let customers choose the amount for donations or invoices Custom form fields — collect additional information relevant to the payment Prefill form fields — pass values into a form via query strings Elementor widget and shortcode — place a released payment form in a page layout Post-payment actions — configure confirmation emails, redirects, success/failure messages, and HTTP requests PayPal Standard Checkout — an alternative one-time gateway with no Payment Page platform fee 💰 PRICING — FREE TO START, ONLY PAY WHEN YOU EARN The free version includes the core plugin and applies a 2% Payment Page platform fee to Stripe transactions. Stripe’s own processing fees and terms still apply. Payment Page does not apply that platform fee to PayPal payments. Upgrade to Pro to: Remove the 2% Payment Page platform fee — Stripe processing fees and terms still apply Unlock ACH Direct Debit through Stripe Financial Connections, subject to Stripe eligibility Priority support See pricing →. Review the governing EULA and the terms shown at checkout before purchasing; the marketing listing does not state a refund duration while public summaries are being reconciled. 🔌 INTEGRATES WITH Stripe — Stripe Connect integration for cards, SEPA Direct Debit, Apple Pay, Google Pay, Alipay, and WeChat Pay; ACH Direct Debit is Pro. Availability depends on the connected account and transaction. PayPal — Standard Checkout for one-time payments Elementor — native payment-form widget HTTP endpoints — send a configurable HTTP request after payment 🔒 SECURITY Stripe card fields are rendered with Stripe Elements rather than ordinary WordPress inputs. Site owners still remain responsible for securing WordPress, restricting access, keeping software updated, showing required notices, and completing the compliance steps that apply to their business and integration. 🆚 WHY CHOOSE PAYMENT PAGE Payment Page focuses on standalone WordPress payment forms when a WooCommerce cart and catalog are unnecessary. The released plugin combines Stripe Connect onboarding, defined one-time and recurring plans, configurable form fields and actions, 22 form-setting templates, and a native Elementor widget. Payment-method availability remains subject to the selected gateway, account, country, currency, browser, device, plan, and recurring-payment support. Read the documentation → · See pricing →