Disconnect Stripe and restore paused subscriptions

This guide shows you what Disconnect Stripe does in this version, and what it does not do. Read the next section before you select it: in this version a disconnect can’t be undone from MapleGather.

Who can do this: Admins who hold the billing:configure-processor permission. That is usually your org’s primary admin or owner. A Finance sub-role does not hold it. For that role the processor page opens read-only, with no Disconnect Stripe button.

Before you start

In this version Disconnect Stripe only records that a disconnect was requested, with a 48-hour reversal deadline. Exactly this happens, and nothing more:

The Stripe section switches to the setup view (Connect Stripe to accept payments, with a Connect Stripe button), as if Stripe were not connected. MapleGather still keeps your Stripe account on the connection.
No subscription is paused. Every subscription keeps its current status, and no member’s subscription changes because of the disconnect.
Members are not told. No portal notice and no email is sent.
Nothing happens at 48 hours. No step completes the disconnect, and nothing changes when the deadline passes.
You can’t reverse it from the page. Selecting Connect Stripe again does not reconnect — see Reconnecting.

If you only want to change your statement descriptor, you do not need to disconnect. It lives on the Settings tab. See Connect Stripe and configure your payment processor.

Steps

Open the Payment processor page at /admin/billing/payment-processor. (The Billing & payments sidebar link has no page of its own yet.)
In the Stripe section, select the Settings tab, then select Disconnect Stripe. (The PayPal section has its own, separate disconnect.)
Read the confirmation, headed “Disconnect Stripe”. It says “This version only records the disconnect. Stripe keeps taking live payments and recurring charges, this page then shows Stripe as not connected, and connecting Stripe again is refused while the account stays linked.” — see Before you start.
Select Disconnect Stripe to go ahead, or Keep connected to keep your connection.
Disconnecting needs a recent sign-in. If yours isn’t recent enough, MapleGather refuses the disconnect and the dialog shows the refusal; nothing is disconnected. The Stripe section has no Confirm your identity step yet, so sign out, sign back in, and disconnect again.

Verify

You’ll know the disconnect was recorded when the Stripe section goes back to Connect Stripe to accept payments, with a Connect Stripe button. The page shows no countdown or 48-hour warning.

If the disconnect was refused for a recent sign-in, nothing was recorded and the Stripe section stays connected. MapleGather records a completed disconnect for audit.

Reconnecting

Reconnecting after a disconnect isn’t possible in this version. Selecting Connect Stripe takes you to Stripe’s sign-in as usual, but when you come back MapleGather refuses the connection because your org still has a connected Stripe account on record (stripe.already_connected). You return to the same Connect Stripe to accept payments view with the error “Stripe sent you back, but connecting the account failed:” followed by the reason (“Organization already has a connected Stripe account”), and nothing is reconnected. Trying again gives the same result.

There is also no subscription to restore, because the disconnect paused none. A subscription you paused yourself is resumed from the member’s record: Resume, then Resume subscription (see Pause or cancel a member’s subscription).

If something goes wrong

“Disconnect already staged” — the dialog shows this when the disconnect was already recorded, for example by another admin or in another browser tab while this page was open. Nothing more was changed. Select Keep connected and reload the page: it shows the setup view. The disconnect can’t be undone from MapleGather in this version (see Reconnecting).
“You don’t have permission to do that.” — the dialog shows this when your sign-in isn’t recent enough; nothing was disconnected (see the next item).
The disconnect is refused for a recent sign-in — despite its wording, the message above is about how recently you signed in: the check is on how recently you signed in, not on your permissions. Sign out and sign back in, then disconnect again. Make a note of anything you have typed on this page first: signing out does not keep unsaved changes, including a part-typed statement descriptor.
The Disconnect Stripe button is missing — your role does not hold the billing configuration permission. Ask your org’s primary admin to grant it.
Your checkout routing disappears — routing needs two connected processors. Disconnecting one removes the routing card and drops any routing edits you had not saved. Checkout then falls back to your org’s own default-processor setting. That setting is held separately from the routing card, and it can still name the processor you just disconnected, so confirm it names a processor you still have connected before you take any more payments. Your saved routing choices are not deleted — they become live again as soon as a second processor is connected. See Route checkout between Stripe and PayPal.