All free tools Talk to a specialist
Free tool for subscription businesses

High-Risk Merchant Account Readiness Checklist for Subscription Businesses

Subscription businesses bill the same card again and again, so underwriters focus on how customers sign up, how they cancel, and what shows up on their statement. Tick off what you have, enter your monthly numbers, and see which gaps to close first before you apply.

Your business

Pick the closest match. This changes which items are ranked first and what product or service documentation you'll need.
How long the business has been operating, not how long you have been processing cards.
Total card sales in a typical month. If you haven't processed cards yet, enter your expected volume.
Number of card sales in the same month you use for disputes. Used for your dispute ratio and average ticket.
Disputes received in that same month. Enter 0 if none, or your best estimate if this is your first account.
This changes which documents apply and what your next step should be.
What you already have

Tick only what is ready today. Leave it unticked if it exists but is out of date or hard to find.

Monthly statements showing volume, refunds, and disputes. Not applicable if this is your first account.
Statements for the business account where card deposits will land.
Articles of incorporation or organization, EIN confirmation letter, and any business license that applies.
A page customers can find that explains how and when they get money back.
Explains how to cancel a service, booking, subscription, or membership.
Explains what customer data you collect and how you use it.
The name that appears on a customer's card statement matches the brand they bought from.
Easy to find, ideally in the header or footer and on checkout or booking pages.
Industry-specific proof of what you sell, such as product labels, licenses, or sample contracts. See the explanation in your results.

Your readiness results

Choose your industry and situation, tick what you have, and enter your numbers to see what is missing.

How this works: the rules behind your results

Every rule this checklist uses is a TouchSuite tool assumption, listed here so you can see exactly how your score and ranking are produced. None of them measure approval likelihood, and no pricing assumptions are used.

Ranking by industry

How subscription businesses should fill in the checklist

Industry: if you sell supplements, vitamins, or wellness products on a recurring plan, choose Nutraceuticals. That moves product documentation into 'Gather first'. If you run a paid dating or membership-matching service, choose Dating. That moves your cancellation policy into 'Gather first' and your billing descriptor into 'Fix next'. Boxes, software, content, coaching, and other recurring plans should choose Other.

Card transactions per month: count every approved charge in the month, including renewals, first payments, and one-time add-ons. Leave out declined attempts and failed retries from your dunning process. They never settled, and counting them makes your average ticket look smaller than what an underwriter will see on your statements.

Disputes per month: count every chargeback you received that month, even if the original charge was from an earlier billing cycle. Subscription disputes often arrive weeks after the renewal that triggered them. The tool's same-month ratio is a quick check, not the method a card brand uses.

Volume: subscription revenue is almost entirely card-not-present, and annual plans can make one month look much larger than the next. Enter a typical month. If your volume is lumpy because of annual renewals, be ready to explain that when you talk to an underwriter.

Cancellation, refund, and descriptor gaps that matter most for subscription businesses

For recurring billing, the cancellation policy is often the first page an underwriter checks. If you chose Other, the tool lists a missing cancellation policy under 'Fix next', but treat it as urgent anyway. It should say how to cancel (an online button, email, or phone), when the cancellation takes effect, and whether the current period is refunded or runs out.

Your checkout should state the price, how often the customer will be charged, and when a free or discounted trial converts to a paid plan. Renewal reminder emails and receipts showing the next billing date give customers a reason to contact you instead of their bank. Rules on automatic renewal disclosures vary by state and card brand, so confirm what applies to you with the card brands and your state.

The billing descriptor matters more when a charge repeats. A customer who signed up six months ago may not recognize an LLC name they never saw. Match the descriptor to the brand on your website and, where your processor allows, include a short support phone number or URL.

Refund policy: spell out how partial months, prepaid annual plans, and unopened boxes are handled. Vague language like 'all sales final' on a recurring plan tends to prompt follow-up questions.

Worked example: a hypothetical coffee subscription business

All numbers here are invented for illustration. A coffee subscription business, 14 months old, chooses Other as its industry and 'Switching processors' as its situation. It enters $40,000 in monthly card volume, 1,000 card transactions, and 6 disputes. It has processing statements, bank statements, formation documents, a refund policy, a privacy policy, and visible contact info. It does not have a published cancellation policy, its descriptor shows the LLC name instead of the brand, and it has not pulled together product documentation.

The tool shows 6 of 9 items in place (67%), which falls in the 'Partially ready' band. The dispute ratio is 6 / 1,000 = 0.60%, and the average ticket is $40,000 / 1,000 = $40.00. The missing items appear in this order: cancellation policy (Fix next), then product documentation and billing descriptor (Finish before you apply). Because it is switching, the next step is to have recent statements ready and a one- or two-sentence reason for the switch.

For this business, a $40 average ticket should line up with its statements. If many customers prepay annual plans, the average will run higher in renewal months, and the owner should mention that up front. Publishing a cancellation page and changing the descriptor to the brand name are both changes the business controls and can make before applying.

Estimates are based on published industry averages and are not a quote. Actual rates depend on card mix, ticket size, industry, and underwriting. This checklist does not predict approval and is not an offer of an account.

What a strong result looks like for subscription businesses

A strong result means every applicable item is ticked, your stated average ticket matches your plan pricing and your statements, and your dispute history comes with an explanation. Example: 'disputes rose in January after holiday gift subscriptions renewed, and we added a renewal reminder email in February.' Underwriters tend to want to see that you noticed a problem and acted on it.

Watch your seasonal patterns. Gift subscriptions bought in November and December often renew in January or later, and recipients who never chose to be billed may dispute. Annual plans bunch renewals into specific months. Know when your spikes happen before an underwriter asks.

When you review statements from your current processor, list every recurring line item you are paying for, such as gateway, account updater, recurring billing, or compliance fees. You don't need this for the checklist, but you will want to compare those line items if you switch. When your list is ready, talk to a payments specialist at TouchSuite about your plan structure and history.

Frequently asked questions

We offer a free trial that converts to a paid plan. What should we have ready?

Have screenshots of your checkout showing the trial length, the price after the trial, and the conversion date. Add copies of any reminder emails you send before the first charge, and a cancellation policy that covers cancelling during the trial. The checklist cannot tell you how an underwriter will view your trial, but clear, documented terms answer the questions they usually ask.

Should failed renewal retries count as transactions in the calculator?

No. Count only approved, settled charges. Failed retries never became transactions, so including them lowers your average ticket and dispute ratio compared to what your statements show. Underwriters compare your stated numbers with your statements, so keep them consistent.

We sell both monthly and annual plans. Which average ticket do we report?

Enter a typical month's total card volume and approved transaction count, and use the average the tool calculates. If annual renewals cluster in certain months, note which months and roughly what share of subscribers are on annual plans, so the variation on your statements doesn't come as a surprise.

Our previous processor closed our account after a wave of renewal chargebacks. Is it worth applying again?

Choose 'Account frozen or closed' and the tool will list processing statements first if they are missing. Get the closure notice in writing, your last statements, and details of any held reserve. Ask whether you were reported to a list such as Mastercard MATCH. Then write down what you changed: clearer renewal disclosures, reminder emails, an easier cancel button, or a fixed descriptor. The checklist does not predict approval, but a documented fix gives an underwriter something concrete to review.

We sell supplements on a monthly auto-ship plan. Is that nutraceuticals or other?

Choose Nutraceuticals. The tool will move product documentation into 'Gather first' and ask for labels, ingredient lists, supplier information, and support for any claims on your site. Your auto-ship cancellation terms still matter, so make sure that policy is published as well.

Put this checklist on your website

Accountants, business attorneys, consultants, and trade associations that work with supplement brands, moving companies, tech support firms, and membership sites can embed this free readiness checklist with one line of code. It stays up to date automatically.