Ravenzoz EU Withdrawal Button & Consent For Memberships Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Since 19 June 2026, EU Directive 2023/2673 (Art. 11a) requires online sellers of in-scope distance contracts to
display a functional withdrawal button and confirm withdrawal requests on a durable medium. Sellers of digital
content with immediate access can be exempted from withdrawal, but only if they capture explicit consent and
acknowledgment from the buyer before the contract.
This plugin adds that withdrawal button, the consent-capture checkout flow, and durable-medium email
confirmations to three membership and course platforms: MemberPress, LearnDash, and Paid Memberships Pro.
This plugin helps you meet these requirements; no plugin can guarantee legal compliance. It is a technical aid, not legal advice. Consult a qualified professional to confirm the exemption
wording and process are correct for your business and target markets.
What you get
- Works with MemberPress, LearnDash and Paid Memberships Pro (auto-detected)
- Consent checkbox at checkout, with the exact wording recorded
- Two-step withdrawal function on the buyer’s account page
- Acknowledgement email sent on a durable medium
- Admin log of every consent and withdrawal
Planned Pro features
- Compliance-evidence export
- Multilingual consent templates
- EU-only geotargeting
Privacy
The plugin stores each buyer’s consent text, consent time, and (if they withdraw) the name and email address they entered, in a table in your own WordPress database. It sends acknowledgement emails through your site’s normal email system. It does not contact any external service and does not track visitors.
Screenshots
The consent checkbox shown at checkout, with a plain-language explanation alongside the exact legal
wording that gets recorded.
Step one of the withdrawal function on the buyer’s account page: name, confirmation email, and the
purchase being withdrawn from.
Step two: reviewing and separately confirming the withdrawal statement, as required by Art. 11a’s
two-step process.
The admin-facing compliance log — every consent and withdrawal, with human-readable platform and
product names rather than internal IDs.
