Before revoking a Mollie payment mandate in the PayRequest Customer Portal, check every service that depends on it. Mollie states that revocation cancels all connected Mollie subscriptions. Confirm the provider result, the PayRequest subscription record and the service agreement separately; a removed payment method is not evidence that an invoice was settled or an existing payment refunded.
This checklist is for customers changing how they pay and billing teams handling that request. Its four-record worksheet distinguishes the authorization from the commercial agreement and money movement. It is a proposed review process, not a report of a payment we canceled in a customer account.
What Does the Portal Action Change?
PayRequest's Customer Portal documentation describes payment-method management. In the reviewed shop-portal implementation, confirming a Mollie mandate removal sends a revoke request and reloads the active mandate list. That method does not call subscription cancellation.
Mollie’s mandate-revocation documentation says that connected Mollie subscriptions are canceled when their mandate is revoked. The reverse is different: canceling one Mollie subscription leaves the customer’s mandates unaffected. The portal method’s lack of a separate cancellation call does not negate this provider-side consequence. Check any connected provider subscriptions, the local PayRequest record and the agreed service end independently. This article concerns that Mollie flow; other saved methods can behave differently.
Keep Four Records Separate
Use this worksheet before telling the customer the change is complete. Give each row an owner and record what you actually observed.
| Record | Question to resolve | Evidence to retain |
|---|---|---|
| Mandate | Which authorization was revoked? | Identifier, action time and confirmed result |
| Subscription | Does service continue, change payment method or end? | Subscription identifier, current status and agreed date |
| Invoice | Is there an issued amount still to resolve? | Invoice identifier and current balance |
| Payment | Was a payment already created? | Transaction identifier and current provider status |
A disappearing row answers less than this worksheet. The reviewed portal list displays valid mandates, so absence is not a complete authorization history. If removal failed or the list cannot load, ask the seller to check rather than repeatedly clicking.
Check Before and After Removing the Mandate
First confirm you are in the intended seller's portal and identify the correct method. Note the subscription's next billing date and any invoice already issued. Ask the billing owner whether another subscription uses the same authorization; do not assume a method belongs to only one service.
If service should continue, agree the replacement payment route first. Follow the seller's supported setup and wait for confirmed authorization where required. A submitted form or return from a provider page should not be treated as proof that the replacement is usable.
After confirming removal, reopen the payment-method area and ask the seller to verify the result. Review the related subscription and existing payments independently. Do not promise that an already-created payment was stopped or that money will be refunded based on this action alone.
Worked Example: Two Services, One Authorization
Suppose a fictional customer has hosting and maintenance subscriptions at Mollie connected to the same mandate. They want maintenance to end while hosting continues. Revoking that shared mandate would cancel both connected provider subscriptions, so it is not a selective maintenance-cancellation action.
Before removal, the seller reviews the individual subscription change and the hosting payment route. If revocation has already happened, they inspect both provider subscription statuses, both PayRequest records and any payments already created. They then agree how hosting should continue and how any outstanding invoice should be settled. A replacement authorization alone is not evidence that this review is complete.
This example illustrates why the four records matter. It does not assert that every PayRequest subscription shares a mandate, or prescribe a legal cancellation date. Use the actual agreement and configured billing workflow.
Send a Confirmation That Matches the Evidence
A useful message is: “Authorization [identifier] was revoked on [time]. Service [identifier] is [confirmed status] from [date]. Invoice [identifier] has [verified balance]. Payment [identifier] is [provider status]. Your next step is [specific action].” Leave a field unresolved when it has not been verified.
For a failed or pending payment, give the customer a clear owner and follow-up time. PayRequest's mandate-management guide covers authorization issues and alternative billing routes. Avoid retrying collection without first resolving what the customer requested.
Review the Change in PayRequest
Use the Customer Portal for the supported customer payment-method workflow, then coordinate the commercial change through Subscriptions. Close the request only when the authorization result and the service decision are both understood.
Prepared by the PayRequest Team with AI assistance. Product documentation and the relevant portal code were reviewed on 9 October 2026; examples are illustrative, not customer results.
