Understand unsupported refunds
Follow this guide to use Stripe/core CRM refund controls because the module provides no refund action. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goNo module route — use approved Stripe and CRM finance procedures
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What you’ll accomplish
Use Stripe/core CRM refund controls because the module provides no refund action. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Do not look for an iDEAL refund button in the module.
- Follow the organisation’s provider refund and CRM reconciliation process.
Fields and options to review
Module refund controllerNot implemented
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Rules the system enforces
- The supplied module implements or omits this behaviour exactly as described.
How to confirm it worked
- Understand unsupported refunds completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Protect credentials and invoice/payment data.
- Verify Stripe state before any retry or manual finance correction.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.