Start a mandate
Composite scenario · Subscriptions · nutra

Thirty days’ notice on the only MID

A subscription merchant processing everything through one acquirer gets a termination notice. The job: stay live, then never be in that position again.

Composite scenario: built from the kinds of mandates we handle, with details changed and combined. It does not describe a specific client. Results depend on the business, the providers and the file.

Model
Trial-to-subscription, card-not-present
Volume
Mid six figures a month
Trigger
Acquirer exiting the vertical
Timeline
Notice period of about a month
01

The situation

All volume ran through a single MID. Ratios were acceptable but rising, mostly “I don’t recognise this charge” disputes from an unclear descriptor and buried rebill terms.

The acquirer was de-risking the vertical portfolio-wide, so arguing the decision wasn’t an option. The question was what would be live on day 31.

02

What we changed

  • Fixed what underwriters would see first: checkout rebill disclosure, refund policy, descriptor and support contacts, so the file read as a well-run subscription business.
  • Built the underwriting pack from existing statements and ratio history, and applied to acquirers that actively board the vertical, in parallel, with full disclosure.
  • Added dispute alerts and a faster refund path before the new MIDs went live, so the new acquirers saw ratios moving the right way.
  • Put routing in front of the MIDs with health checks, so volume shifts if any one route degrades.
03

What held

  • Processing continued without a gap through the notice period.
  • Two MIDs live instead of one, plus a third in underwriting as standby.
  • Fewer unrecognised-charge disputes once the descriptor and rebill terms were fixed.
The lesson

The best time to board a backup acquirer is while the primary still likes you.

Talk about your situation High-risk merchant accounts