Understand unsupported refunds
Use Stripe/core CRM refund controls because the module provides no refund action.
Exact navigationNo module route — use approved Stripe and CRM finance procedures
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm 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 this guide covers
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.
Exact step-by-step process
- Do not look for an iDEAL refund button in the module.
- Follow the organisation’s provider refund and CRM reconciliation process.
Fields, choices and supported possibilities
Module refund controllerNot implemented
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Code-backed validations and workflow rules
- The supplied module implements or omits this behaviour exactly as described.
Expected result and verification
- 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.