Merchant Account for SaaS With Annual Plans: The Deferred Delivery Problem

Underwriters read an annual plan billed upfront as deferred delivery: months of service the acquirer is liable for if the company stops. That exposure sets the reserve and the volume cap, so the file must show the annual share and the remaining term. Pro-rata refunds, a cancellation path and a renewal reminder turn disputes into refunds. A SaaS outside the US adds entity, director and bank account with the IBO package.

A merchant account for a SaaS that sells annual plans is underwritten as a deferred delivery risk. When a customer pays twelve months upfront, the acquirer has paid the merchant for a year of service not yet rendered and stays liable if it never is. If the company stops, every unexpired month can come back as a "service not provided" dispute the acquirer ends up holding. That exposure, not the software, is what the underwriter prices, through the reserve, the volume cap and the proration, cancellation and descriptor terms. For a team outside the US, the IBO (Independent Business Operator) package on the IBO package supplies the entity, the director and the bank account that file needs.

Why an annual plan reads as a year of undelivered service

Monthly SaaS is delivered almost as fast as it is billed: by the time a cardholder disputes, most of the service is consumed. An annual plan reverses that ratio. A month after the charge, one twelfth of the service has been delivered and eleven twelfths are still a promise. Underwriters call this shape deferred delivery and treat it like pre-orders, event tickets and travel: the money is in, the obligation is open, and the obligation is the risk.

The scenario the underwriter tests is not fraud, it is disappearance. A company that shuts down, sunsets the product or stops answering support leaves every annual subscriber with a legitimate claim. Under card network rules, the window to dispute a service not provided typically runs from the date the service was due, not from the charge date, within an outer limit counted from the transaction, so a plan sold in January is still disputable late in the year. If the merchant is gone, the acquirer pays those chargebacks itself. Your accountant calls the same money deferred revenue; the underwriter only asks how much service you still owe and what stands behind it.

How the unearned service shapes reserves and the volume cap

The underwriter reads the file for the size of the open obligation: the larger the prepaid annual share, the longer the acquirer stays exposed after each charge. Four tools answer that exposure, set in the approval or monitored once the MID is live. The monthly volume cap guide on this blog describes the controls; here is how annual plans move each one.

What a monthly-plus-annual mix does to the file

An annual-heavy SaaS is typically priced rather than refused; the reserve and the cap are the price, and what you control is the measurement. A file that reports total volume with no split invites the reviewer to assume all of it is prepaid and none of it refundable. An annual plan chosen by established customers also reads differently from a discounted one pushed at first-time buyers, who are the customers most likely to churn. Present the mix as facts.

• The split by count and by volume. The share of subscriptions on annual terms and the share of dollars from annual charges; the two rarely match.
• The remaining term. How far the average annual subscriber is into the year; a book that renewed last month carries more open obligation than one spread across the year.
• Refunds and disputes per plan. Separate ratios show whether the annual discount attracts buyers who ask for the money back.
• The renewal calendar. The months in which annual renewals concentrate, so the cap and the reserve are set for the spike, not tripped by it.

Proration and cancellation terms the underwriter reads

Deferred delivery weighs most where the customer has no exit except the bank. The underwriter reads your proration and cancellation terms as what turns a chargeback into a refund you control, and checks them on the live checkout. The refund policy guide on this blog covers the policy itself; these are the annual-term lines.

• Refund of the unused term. Refunding unexpired months pro rata on cancellation or shutdown turns the acquirer's exposure into a merchant process. A strict "annual plans are non-refundable" line tells the reviewer that every unhappy subscriber will go to the issuer.
• Proration on plan changes. Upgrades charged for the difference over the remaining term, downgrades credited or applied at renewal, both stated on the pricing page; an unexplained mid-term charge is disputed as unrecognised.
• A cancellation path inside the account. One control the customer can reach without writing to support, a confirmation email, and no retention flow blocking the exit.
• Renewal disclosure. The renewal date and amount shown before the first charge, restated on each receipt, and a reminder before an annual rebill. Card networks expect it; a missing reminder is a common root of "I did not authorise this" disputes.
• Shutdown terms. What happens to prepaid customers if the product is discontinued: a refund of the unused term or a migration. Writing it down answers the underwriter's central question.

The descriptor when the tool is not named after the company

A SaaS brand is often not the legal entity's name. The customer signed up for a product; the merchant agreement, the bank account and the settlements sit under a company name that may share no word with it, and a package from the inventory page carries an entity name you did not choose. The descriptor is where the two names meet, and on an annual plan the statement line may be the customer's only reminder of the charge for twelve months. The billing descriptor guide on this blog covers the format.

• Lead with the product name. The brand the customer typed into the checkout, not the entity, with a support URL or phone number beside it. A descriptor that reads as an unknown LLC is a common root of a dispute on a charge the customer approved.
• Declare the trading name on the application. Acquirers typically accept a product-name descriptor when the application lists it as the trading name and the website ties it to the legal entity. Whether a formal trade-name registration is needed depends on the acquirer and the state; ask your ISO and a professional.
• Show the entity on the site. Legal name in the footer, in the terms of service and on the receipt, so the KYB reviewer can walk from the brand to the entity to the bank account.
• Keep it identical on every charge. The same descriptor on the first charge, on each renewal and on the annual rebill a year later, restated on the receipt and the reminder; a change reads as a different merchant.

Where the IBO package fits, with one condition

A team outside the US faces a second problem: the acquirer expects a US entity, a US-resident person to sign the merchant agreement and the personal guarantee, and a US bank account for settlements. The IBO package supplies that half of the file. The IBO is a real, KYC-verified US resident who serves as the nominee director of a fresh US LLC or C-Corp; every IBOCore director has zero criminal record, a credit score of 650 or more, and serves one merchant only. The package arrives the same day the payment confirms with:

• The US entity with its EIN, incorporated in the director's home state, never a Wyoming shell, with articles, operating agreement, EIN letter, government ID and proof of address.
• A business bank account at Bluebanc or Relay in the company's name with full operational access: inbound and outbound wires, debit card, no minimum balance.
• A professional email on the company domain and a dedicated US residential proxy.
• Director collaboration on verification calls and signatures, with zero interference in the business.
• 24/7 support in a private Telegram group with an account manager.

The IBO package costs $999 setup, then $2,999 per month from 30 days after delivery, whatever the vertical or the billing model. The setup fee is paid in USDT or USDC on ERC20 or TRC20. The document template pack ($499, one-time) includes a refund policy and a terms of service template. The state filing and the EIN show the director as the principal. At the time of writing, under FinCEN's interim final rule of March 2025, domestic companies and US persons are exempt from beneficial ownership reporting, while companies formed under foreign law that register in a US state remain subject to it; verify current FinCEN guidance with a professional, as IBOCore gives no legal or tax advice.

Questions merchants ask

Will an acquirer refuse a SaaS that only sells annual plans?

Refusal is not the usual answer; pricing is. An annual-only product carries the largest open obligation per dollar, so the underwriter typically responds with a higher or longer reserve, a cap set on the renewal spike and a close reading of the refund terms. Pro-rata refunds, a renewal reminder and a clear remaining-term picture make the file workable. The acquirer decides each file.

Should I present annual revenue as monthly to keep the ticket small?

No. Twelve instalments are a different product with a different disclosure, and describing one model while running the other typically ends a MID once the statements are reviewed. If you want a smaller ticket, sell a monthly plan and say so. If you sell annual, show the ticket, the split and the calendar, and let the underwriter size the cap and the reserve on real numbers.

Does the reserve go away once the annual cohort has been delivered?

Reserves are reviewed, not automatic. Acquirers typically revisit a reserve after a period of clean processing, when the dispute ratios by count and by dollars have held and the renewal months have passed without a refund spike. The request comes from you, with statements attached, and lands better when the descriptor, the terms and the billing model have not changed since the application.

High-risk MID metrics acquirers watch

Once live, your chargeback ratio (CB ratio) is chargebacks divided by transactions; Visa VDMP and Mastercard ECP programs trigger when you breach network thresholds. Rolling reserves (often 10% for 180 days) protect the acquirer against future disputes. MATCH (Terminated Merchant File) is the industry blacklist after a forced termination. MCC (Merchant Category Code) must reflect your real vertical; miscoding is a scheme violation.

• Representment: fighting a chargeback with delivery proof and logs.
• RDR / Ethoca alerts: pre-chargeback refund tools that protect your CB ratio.
• Statement descriptor: keep it recognizable to cut "friendly fraud" disputes.
• Processing cap: volume limit until the acquirer trusts your history.

MID stacking without structure

Spreading volume across many MIDs without separate entities looks like ratio gaming or transaction laundering to risk teams. The durable pattern is one IBO package per MID, clean descriptors, honest MCC, and reserves treated as a cost of doing high-risk volume.

FAQ: quick answers

How fast can I get an IBO package on IBOCore?

Available inventory ships the same day after payment. You receive Articles, EIN letter, registered agent details, bank onboarding pack and signer contact through your merchant dashboard. Processor onboarding typically follows over the next one to two weeks.

Where can I look up payment-processing jargon?

Use the Resources glossary on IBOCore (/resources) for 580+ definitions: MID, chargeback ratio, MATCH, rolling reserve, MCC, RDR, KYB and high-risk vertical vocabulary.