Implementation guide

Custom Website EU Withdrawal Button

Custom storefronts that do not have a mature plugin ecosystem.

Custom sites can add either a hosted withdrawal URL or a small widget script, then keep the workflow outside the core checkout code.

Install steps

1. Create a store profile with domain, merchant email, and default language.
2. Add the link or widget to footer, account, and help pages.
3. Test the confirmation step and email previews before public launch.
4. Use dashboard records and CSV exports for customer support workflows.

Create withdrawal button Check my store

Generated snippets

Exact URLs and public keys are generated in the merchant dashboard after the store is created.

<a href="https://euwithdrawalbutton.app/w/your-store-slug">Withdraw from contract here</a>


<script async src="https://euwithdrawalbutton.app/widget.js" data-store="your-public-key"></script>

CONFIRMATION BUTTON

Confirm withdrawal

API-light launch path

The initial implementation does not require order-system write access or a custom backend integration.

This keeps launch scope small while still giving customers a stable electronic withdrawal entry point.

When to go deeper

If your team later wants order matching, account cancellation, or refund automation, treat those as separate internal integrations.

The withdrawal request record can remain the source of customer-submitted intent.

Questions

Does the widget collect visitor data?

The widget loads store configuration and links to the hosted withdrawal page; request details are collected only when a customer submits the hosted form.

EUWithdrawalButton.app helps merchants implement an electronic withdrawal workflow. It is not a law firm and does not provide legal advice.