Payment capability

Recurring payment processing for high-risk subscriptions.

Recurring payment processing charges a saved customer credential automatically on a set schedule, the engine behind subscriptions, memberships, auto-refills, and installment plans. For high-risk merchants it has to be underwritten as core infrastructure, because the rebill model, refund policy, and chargeback pattern decide whether the account survives.

$0 monthly fees
1,600+ U.S. businesses served
15+ years in merchant services
$400M+ monthly processing volume

Risk problem

Subscription revenue breaks when rebills, card updates, and processor risk are handled separately.

Recurring revenue fails quietly, one declined rebill at a time. Cards expire, get reissued after a breach, or hit their limit, and every failed charge is silent churn unless the system catches and retries it. Subscription billing also concentrates the exact patterns high-risk underwriters watch most: free-to-paid trial conversions, the refund spike when a customer forgets they subscribed, and the dispute filed as "I never authorized this." When the gateway, the card updater, and the processor's risk team are wired together, a failed rebill becomes a retry and a dispute becomes a representment (a defended chargeback). When they are handled separately, the same events become involuntary churn and a rising chargeback ratio that can cost the account. That is why rebill cadence, trial terms, refund policy, and chargeback history belong in the underwriting conversation from the first call, not after the first billing cycle.

Get Pricing

Mechanics

How recurring billing works in the Midnight Payments flow.

Gateways such as Authorize.net and USAePay store the card as a vault token (a stand-in for the real card number) and charge it on the schedule you set, so customers are billed without you holding raw card data and rebills survive a card reissue.

Account-updater services refresh expired or reissued card numbers automatically, recovering the involuntary churn that silently drains subscription revenue when a card changes.

Subscription-heavy merchants disclose trial structure, rebill cadence, refund policy, and chargeback history up front, because those terms drive both the underwriting decision and the dispute exposure later.

Recurring-billing reporting surfaces failed rebills, retry outcomes, and rising dispute signals early, so an account-risk problem is visible before it compounds into a ratio event.

Account fit

Included with the right merchant account structure.

Recurring billing is a core capability of the merchant account, not a separately priced add-on. It ships under the same posture as the rest of the relationship: $0 monthly fees, no long-term contract, and daily ACH settlement on the funds it collects. Because the rebill engine and the underwriting are set up together, the billing model your business actually runs is priced into the account from the start instead of bolted on after approval. See how Midnight Payments handles fees before you request terms.

FAQ

Common recurring billing questions.

For cross-cutting approval and pricing questions, see the full FAQ.

Can high-risk merchants run subscriptions?

Yes, when the processor understands the vertical, the rebill model, and the chargeback exposure before approval. Subscriptions are not the problem; an unreviewed subscription model is. The offer structure, trial terms, and refund policy are underwritten up front so the account is built to carry recurring volume instead of being surprised by it.

Which gateways support recurring billing?

Authorize.net and USAePay are the common options, both supporting tokenized rebills on a set schedule. The right fit depends on your cart, integration method, and whether you also need account-updater and dunning (failed-payment retry) features. NMI is available for more complex or multi-MID setups.

What is tokenization and why does it matter for rebills?

Tokenization replaces the stored card number with a vault token held by the gateway, so you can re-charge a customer every cycle without keeping raw card data on your systems. It shrinks your PCI scope and lets rebills keep running even after a card is reissued, as long as an account updater refreshes the token.

How do failed rebills and expired cards get handled?

Account-updater services refresh reissued or expired card numbers automatically, and dunning logic retries a failed charge on a schedule before the subscription lapses. Together they recover involuntary churn, the revenue lost not because a customer canceled but because a card silently stopped working.

What should subscription merchants disclose during review?

Trial structure, billing cadence, refund policy, current processor status, and chargeback history. Free-trial-to-paid conversions and forgot-I-subscribed refunds are the patterns underwriters watch most, so disclosing them up front leads to a more stable account than letting them surface in the first billing cycle.

Do free trials and negative-option billing affect approval?

They are underwritten, not automatically disqualifying. Trial-to-paid offers carry known dispute risk, so the review looks at how the trial terms, billing disclosure, and cancellation path are presented to the customer. Clear disclosure at signup is both a compliance posture and the best defense against "I never authorized this" chargebacks.

Are there monthly fees on recurring billing?

No. Recurring billing ships under the same $0 monthly fee posture as the rest of the account, with no long-term contract and daily ACH settlement. The cost lives in processing fees on the volume you run, not a separate monthly charge for enabling rebills.

Get reviewed

Find out whether recurring billing fits your account.

Share your category, volume, current processor status, and payment model so the account can be reviewed around the real risk.