Withdrawal button and payment processors
Do you sell online to consumers in the EU and take payment with Stripe or PayPal? The withdrawal button does not refund on its own: you are the one who refunds, in your usual tool. BackToMe covers the regulatory side of this European obligation (Directive (EU) 2023/2673): collection, an acknowledgement sent to the customer by email, dated archiving, notification to the merchant. The refund is still carried out by you in your PSP's interface: BackToMe never needs your payment API keys, which reduces your risk surface and preserves your existing architecture.
0 € today · Cancel in one click · 30-day money-back guarantee
How the button fits into your payment stack
- The consumer clicks the withdrawal button and confirms their request.
- BackToMe archives the request (reference number, date, a file impossible to alter afterwards) and sends an acknowledgement of receipt to the consumer by email (PDF), in accordance with the European withdrawal obligation (Directive (EU) 2023/2673).
- Real-time notification to the merchant (email, dashboard, optional HTTPS webhook) with the customer reference (order, subscription, invoice) entered by the consumer.
- You process the refund in your usual PSP interface (Stripe Dashboard, PayPal, Adyen, etc.) within the fourteen days provided for by law (Consumer Rights Directive 2011/83/EU).
- You mark the withdrawal as "Closed" in BackToMe, adding an internal note if needed (PSP refund number, bank transfer, goodwill gesture, etc.).
Compatible with every PSP
The regulatory function of the button (collection, archiving, acknowledgement) is completely independent of your means of payment collection. The button works identically whether you use:
- A card PSP (Stripe, Adyen, Mollie, Checkout.com, SystemPay/Lyra…)
- PayPal, Apple Pay, Google Pay
- A marketplace or subscription PSP (Stripe Billing, Stripe Connect, PayPal Subscriptions, Lemonway, MangoPay…)
- Bank transfer, SEPA direct debit, GoCardless
- Several PSPs in parallel on the same site
Why BackToMe does not trigger the refund
Three technical and legal reasons:
- Security. Handing refund API keys to a third party widens your attack surface and complicates your PCI-DSS audit (if applicable). The merchant keeps full control of their payment flows.
- Business decision. A refund often involves a check (return of the goods received, a statutory exception under the Consumer Rights Directive (2011/83/EU), partial goodwill gesture, pro rata digital service). That decision belongs to the merchant, not to an automated process.
- Compliance with the refund deadline (Consumer Rights Directive 2011/83/EU). The legal 14-day period runs from the withdrawal. The correctness of the refund (exact amount, standard costs included, identical payment method unless otherwise agreed) remains your operational responsibility; BackToMe provides you with the clock and the proof, not the execution.
The case of subscriptions
For a subscription (Stripe Billing, PayPal Subscriptions, etc.), you handle the cancellation of the subscription on your side (immediately or at the end of the paid period) and the possible refund of the last instalment collected. If the service has been partially used with express consent to immediate start (a statutory exception under the Consumer Rights Directive 2011/83/EU), the pro rata is calculated according to your pricing and remains in your hands. BackToMe provides you with the dated proof of the request and the 14-day counter to support you.
Test the button in five minutes
7-day free trial. Install the button on your site, simulate a withdrawal, check that the acknowledgement and the merchant notification are received. Switch to legal mode when you are ready.
Start the free trial