Start with the way your business earns recurring revenue
A monthly membership is different from a prepaid annual service or a product shipped every six weeks. Describe the offer precisely, including any one-time purchases you process alongside subscriptions.
- Memberships and ongoing services: explain what customers can access, when that access begins and how you handle a pause or cancellation.
- Recurring product deliveries: show how billing dates relate to stock availability, shipment and customer support. For category-specific preparation, see supplement payment processing.
- Coaching and education memberships: distinguish recurring access from a fixed program paid in installments. Explore processing for coaching and digital education for that delivery context.
These descriptions start a review; they do not establish eligibility. Include your actual products, customer locations and business country so the discussion reflects the business you intend to operate.
How merchant accounts, payment gateways and subscription billing work together
A billing system determines when and how much to charge; the gateway passes payment requests and results between your tools and the processing service. The merchant processing relationship covers accepting card payments under the agreed account terms. One provider may combine several of these roles. Stripe’s subscription payment processing overview
Before choosing an arrangement, identify who handles each job and which questions need a written answer:
| Part of the setup | Role in a renewal | What to confirm |
|---|---|---|
| Merchant account and processing relationship | Provides the arrangement for accepting card payments, with account conditions and funding terms. | Which bank or provider reviews the business, what the written account terms cover, and who answers funding or account questions. |
| Gateway or payment interface | Connects the checkout or billing software to payment processing and returns transaction results. | How the checkout or billing system submits payment requests, receives results and references the saved payment method. |
| Subscription billing software | Manages the recurring amount and schedule and the billing actions supported by that product. | Which system controls amounts, schedules, invoices and configured customer communications, and who administers it. |
These jobs may sit with separate providers or within a combined product. Authorize.net, for example, documents a recurring-billing feature that generates transactions on a subscription schedule. That is a named product capability, not a feature every gateway or merchant account automatically includes. Authorize.net recurring billing documentation
Your team also owns the offer, delivery and customer-support decisions. NUMUS’s role here is processing placement and guidance; confirm each software feature and integration with the provider responsible for it. Use our account, gateway and billing responsibility guide for a fuller worksheet before the conversation.
Bring a recurring-offer brief
You do not need to solve every technical question before contacting us. A concise brief helps separate what is already working from what still needs confirmation. Complete this for each materially different recurring offer.
| Bring this detail | Write down |
|---|---|
| Offer and delivery | The product or service, what the customer receives, and whether delivery is immediate, ongoing or scheduled. |
| Amount and cadence | The price, billing interval, one-time charges, and whether the amount can change. Distinguish ongoing subscriptions from a fixed installment total. |
| Trial and first payment | Any free or discounted period, when the first paid charge occurs, and the customer-facing explanation. Write “no trial” if none applies. |
| Enrollment and authorization | Where customers see and accept the recurring terms, with a sample journey that contains no customer payment data. |
| Customer changes | How customers request cancellation, a pause, a payment-method update or a refund, and who handles each request. |
| Current payment tools | Your storefront, gateway, billing product and membership or fulfillment system; note which must stay. |
| Processing profile | Actual or clearly labeled projected monthly card volume, typical charge size and relevant processing history. |
Mark an unknown as a question rather than guessing. This is a preparation aid, not a universal bank document list. The provider reviewing your business may ask for additional information. Our merchant account application checklist helps organize the wider application.
Compare subscription payment processing for your current setup
Start with the change you need to make. That helps keep a processing review focused on the right provider and avoids treating every recurring-payment issue as the same problem.
- Launching a recurring offer: map the billing model and required customer actions before comparing account and software options.
- Keeping your existing billing tools: compare processing eligibility, written costs and funding terms, then confirm the supported connection to those tools.
- Investigating failed renewals or customer changes: identify the payment result and the responsible system first. Bring the unresolved issue to the provider that controls the relevant account, billing setting or integration.
A useful processing conversation should cover the account and the work needed around it. Ask for clear answers on:
- Eligibility and scope: whether the actual offer, products, geography and expected volume fit the proposed arrangement.
- Written costs and funding: transaction and recurring fees, separate gateway or billing charges, payout terms, any reserve and other conditions that apply to the offer.
- Technical compatibility: the supported connection between your existing tools and the proposed provider, who performs setup, and how that connection will be checked.
- Operating responsibilities: where staff see a renewal’s payment result, who handles a failed collection, and how billing changes reach customer support and delivery teams.
- Support and exit: who handles account versus software questions, and what the agreement says about termination and moving to another provider.
Check compatibility at the feature level. WooCommerce’s own gateway documentation lists different support for changing recurring amounts, payment dates and payment methods across its extensions. If you use that platform, check the exact extension and actions your business needs; this is a provider-specific example, not a NUMUS integration claim. WooCommerce subscription gateway compatibility
Use your real sales mix when comparing written processing quotes. A headline rate alone does not describe the complete proposal.
When reviewing operations, ask which record proves that a particular renewal was paid. Stripe’s documented model, for example, gives subscriptions, invoices and payments distinct records and statuses. Confirm the meaning of the labels in your own tools rather than relying on another provider’s terminology. Stripe subscription lifecycle documentation
Already accepting recurring payments?
Start with an inventory of the systems and data you would need to keep. Do not assume stored payment credentials, billing schedules and transaction history move together.
Stripe’s payment-data export documentation illustrates why those questions are separate: its supported export process transfers eligible card information to a qualifying receiving processor, while subscriptions and payment history are outside that export. This describes Stripe’s process, not a universal migration rule or a NUMUS migration promise. Stripe payment-data export documentation
Before setting a switch date, ask the current and proposed providers to confirm what can move, how schedules will be handled, who owns the transition and how results will be checked. Keep the existing arrangement’s termination obligations in that discussion. Read our processor switching guide for the broader planning questions.