A payment sub-ISO is a sales organization that markets and sells merchant accounts under a sponsoring registered ISO’s card-network registration, rather than holding its own direct registration with Visa or Mastercard. Think of it as a licensed reseller operating inside a larger compliance and banking framework.
Three things every merchant and payments professional should know upfront:
- Fees layer up. Each party in the chain, including the sub-ISO, takes a cut of the transaction spread, so merchants typically pay more than they would with a direct processor relationship.
- Sponsorship risk is real. If the sponsoring ISO loses its registration or changes its underwriting policies, every merchant account under that sub-ISO is affected.
- Vetting is your first priority. Before signing anything, confirm who the registered ISO and acquiring bank are, and get a full fee breakdown in writing.
The sections below unpack the full ecosystem, typical costs, contract terms, and the exact questions you should ask before committing.
Table of Contents
- How does a sub-ISO fit into the U.S. payments ecosystem?
- How do sub-ISO fees and revenue splits typically work?
- What contract terms and onboarding steps should you expect?
- What questions should you ask a sub-ISO before signing?
- Sub-ISO vs. registered ISO vs. direct processor: which path fits you?
- Key Takeaways
- What we see in practice with sub-ISO arrangements
- Davincipay supports merchants who need clarity on processing costs
- Useful sources and references
How does a sub-ISO fit into the U.S. payments ecosystem?
ISOs are sales and distribution partners that recruit, onboard, and support merchants on behalf of processors and acquiring banks. They do not process transactions themselves. A sub-ISO sits one level below a registered ISO in that hierarchy.
The four core parties:
- Sub-ISO: The front-line sales channel. Signs merchants, handles initial onboarding, and earns residuals from transaction volume.
- Registered ISO (sponsor): Holds the card-network registration. Provides compliance infrastructure, underwriting decisions, and banking relationships to the sub-ISO.
- Acquiring bank: Clears and settles funds. Merchant IDs (MIDs) are issued under the acquirer’s sponsorship.
- Payment processor: Routes transactions technically, handles authorization, and connects to card networks.
How a card transaction flows:
- A customer swipes or enters card details at a merchant’s checkout.
- The payment processor routes the authorization request to the card network and issuing bank.
- The acquiring bank clears and settles funds into the merchant’s account.
- Residuals flow back through the chain: processor to registered ISO, registered ISO to sub-ISO, sub-ISO to its agents.
The merchant’s MID lives under the acquirer, not the sub-ISO. That means the sub-ISO has no direct control over the account’s ultimate fate. Some large registered ISOs, informally called “Super ISOs,” manage entire networks of sub-ISOs and agents, providing full-service underwriting and risk management at scale. Layered markup occurs at every handoff, which is why the merchant at the end of the chain often sees the highest effective rate.
How do sub-ISO fees and revenue splits typically work?
The cost structure in a sub-ISO arrangement follows interchange-plus logic, with each party adding its own margin on top. ISO models differ from PayFac models in how risk, revenue, and onboarding responsibility are distributed, and sub-ISOs sit at the most layered end of that spectrum.
Here is a simplified example illustrating how revenue distribution might work on a given monthly processing volume.
| Party | Typical Share |
|---|---|
| Interchange (card networks/issuers) | A substantial portion |
| Acquiring bank margin | A modest margin |
| Registered ISO (sponsor) residual | A noticeable residual |
| Sub-ISO residual | A smaller residual |
| Agent/sales rep residual | A smaller residual |
These figures are illustrative and actual splits vary significantly by sponsor agreement, merchant risk category, and volume tier. High-risk merchants, including those in nutraceuticals, telehealth, or subscription commerce, typically see higher effective rates at every layer.
Common practices that obscure true cost include tiered pricing buckets (qualified, mid-qualified, non-qualified), per-item fees buried in statement footnotes, and monthly minimums that inflate low-volume months.
What contract terms and onboarding steps should you expect?
Most sub-ISO merchant agreements share a common set of clauses and a predictable underwriting sequence.
Common contract clauses to review carefully:
- Exclusivity provisions that prohibit the merchant from processing with any other provider during the contract term.
- Rolling reserves that hold back a percentage of settlements (often 5–10%) for a defined period to cover potential chargebacks.
- Termination fees that apply if the merchant exits before the contract term ends, sometimes calculated as a multiple of monthly fees.
- Processing caps that limit monthly volume and trigger re-underwriting if exceeded.
- Reserve triggers tied to chargeback ratios or refund rates that can increase the reserve percentage mid-contract.
Underwriting checklist merchants should prepare:
- Government-issued ID and business formation documents (articles of incorporation, EIN letter)
- Three to six months of business bank statements
- Three to six months of processing statements showing chargeback history
- Business website URL and product/service descriptions
- MCC (merchant category code) classification documentation for regulated verticals
Realistic onboarding timeline: straightforward low-risk merchants can expect approval in three to seven business days. High-risk verticals, including supplements, telehealth, and subscription billing, typically require two to four weeks. Common delays include incomplete bank statements, chargeback ratios above card-network thresholds, and unclear business models that require additional underwriting review.
What questions should you ask a sub-ISO before signing?
Vetting a sub-ISO comes down to three categories: sponsorship transparency, pricing clarity, and operational accountability. Use this checklist on your first call.
Sponsorship questions:
- Who is the registered ISO, and which acquiring bank holds the MIDs?
- Can you provide a sponsor letter confirming the relationship?
- How long has the sponsorship agreement been in place?
Pricing questions:
- Will you provide a sample merchant statement with interchange line items broken out?
- Is pricing interchange-plus or tiered? If tiered, what are the qualification criteria?
- Are there per-item fees, monthly minimums, or statement fees beyond the processing rate?
Support and liability questions:
- Who is the contract counterparty: the sub-ISO or the registered ISO?
- Who handles chargeback disputes, and what is the typical response time?
- Where do funds settle, and what is the settlement timeline?
Operational questions:
- What is the underwriting SLA from application to live processing?
- What triggers a reserve increase, and how is the merchant notified?
- What are the termination terms, and is there a migration path if you exit?
Pro Tip: Ask for the name of the acquiring bank before the call ends. A sub-ISO that cannot or will not name its acquiring bank is a significant red flag. Every legitimate arrangement has a named acquirer on record.
Sub-ISO vs. registered ISO vs. direct processor: which path fits you?
The right structure depends on your volume, risk tolerance, and how much operational control you need.
| Factor | Sub-ISO | Registered ISO | Direct processor relationship |
|---|---|---|---|
| Setup speed | Fast (days to weeks) | Slow (months, card-network approval) | Moderate |
| Setup cost | Low | High (registration fees, compliance build) | Moderate to high |
| Margin control | Limited (sponsor takes a cut) | Full control over residuals | Maximum control |
| Compliance burden | Sponsor handles most of it | Full responsibility | Full responsibility |
| Volume requirement | Low to moderate | High (typically $1M+ monthly) | Very high |
| Underwriting flexibility | Sponsor-dependent | Self-directed | Self-directed |
Sub-ISO status fits organizations that want fast market entry, low overhead, and a sales-focused model. Registering as a direct ISO makes sense when monthly volume justifies the compliance investment and you want full margin control. Going direct to a processor is typically reserved for very high-volume merchants with dedicated compliance teams.
Key Takeaways
A payment sub-ISO operates under a sponsoring registered ISO’s card-network registration, which means merchants benefit from faster onboarding but absorb layered fees and inherit the sponsor’s compliance and underwriting decisions.
| Point | Details |
|---|---|
| Sub-ISO definition | A sub-ISO sells merchant accounts under a registered ISO’s sponsorship, with no direct card-network registration of its own. |
| Layered fee risk | Each party in the chain takes a margin, so merchants typically pay higher effective rates than with a direct processor. |
| Sponsorship dependency | If the sponsoring ISO loses its registration or changes underwriting policies, your merchant account is directly affected. |
| Vetting priority | Always get the acquiring bank’s name, a sample statement with interchange line items, and termination terms in writing before signing. |
| Davincipay’s role | Davincipay specializes in high-risk merchant processing, including underwriting support and chargeback mitigation for merchants navigating complex sub-ISO arrangements. |
What we see in practice with sub-ISO arrangements
The most common failure mode we encounter at Davincipay is not a bad actor sub-ISO. It is a merchant who signed without reading the reserve clause. A rolling reserve that holds 10% of settlements for 180 days can create a serious cash flow problem for a supplement brand or telehealth provider processing $50,000 a month. By the time the merchant notices, the reserve balance is already substantial and the termination fee makes exit painful.
The second pattern is statement opacity. Merchants in high-risk verticals often receive bundled statements that show a single effective rate with no interchange line items. They have no way to verify whether the sub-ISO’s markup is reasonable or whether they are being charged non-qualified rates on transactions that should qualify for standard interchange.
Davincipay’s experience with high-risk sectors, including nutraceuticals, telehealth, subscription commerce, and digital services, consistently shows that merchants who ask for interchange-plus pricing and a named acquirer before signing are far better positioned than those who accept a bundled rate and a vague sponsor reference. The remediation steps we recommend are straightforward: request a full statement audit, identify the acquiring bank, and compare the effective rate against interchange-plus benchmarks for your MCC.

Davincipay supports merchants who need clarity on processing costs
High-risk merchants comparing sub-ISO arrangements often discover the real cost only after they are locked into a contract. Davincipay offers a direct alternative: transparent underwriting, interchange-plus pricing, and dedicated chargeback mitigation for merchants in nutraceuticals, telehealth, subscription billing, and other complex verticals.

If you are dealing with opaque sponsor terms, unexpected reserve requirements, or a processing relationship that no longer fits your volume or risk profile, Davincipay can help you evaluate your options and, where needed, support a clean migration to a more transparent processing structure. We work with domestic and international acquiring relationships, so merchants in regulated categories have real options rather than a single sponsor-dependent path.
Apply now to start the underwriting review, or visit Davincipay to learn more about our services for high-risk ecommerce businesses.
This article is general information, not legal or financial advice. Confirm current card-network rules, fee structures, and contract terms with a qualified payments professional or legal counsel before signing any merchant agreement.
.png)

.webp)
