By Alexander Flores, Debt Buyer & Triton Financial Solutions, LLC · Level 2: Intermediate · Last updated: November 3, 2026
Taking payments is the part of running a collection agency that nobody plans for until a processor says no. New agencies apply for a standard merchant account, get declined or frozen, and lose weeks of cash flow. Established agencies get hit with reserves, rate changes or a termination notice after a bad month of disputes.
This guide explains why processors underwrite collection agencies differently, what they look at, how the card network and ACH rules shape your risk, and where federal debt collection law limits the fees you can pass to consumers. Every rule below links to its primary source, checked live on November 3, 2026. It is general industry information, not legal advice.
What is a high-risk merchant account for a collection agency?
It is a card or ACH processing account underwritten for a business the acquirer considers riskier than average. For collection agencies, that usually means deeper review, a possible reserve, tighter dispute monitoring and contract terms that let the processor hold funds.
“High risk” is not a legal category. It is an underwriting label that each acquiring bank and processor applies under its own policy. Two agencies with the same profile can get different answers from different processors, and the same processor can change its view after a few months of data.
What merchant category code do collection agencies use?
Visa assigns collection agencies merchant category code (MCC) 7322. Its October 2026 Merchant Data Standards Manual describes 7322 merchants as those that “collect payments of overdue receivables under contract or collect overdue receivables that they have purchased from a third party.”
That definition covers both contingency agencies and debt buyers that collect their own paper. The manual also tells credit-reporting businesses (MCC 7321) to use 7322 when they are primarily collecting defaulted debts. The MCC matters because acquirers, issuers and risk tools often key their rules to it. In the manual pages we reviewed, Visa does not itself label 7322 “high risk.” That treatment comes from acquirer underwriting.
Source: Visa Merchant Data Standards Manual, October 2026.
Why do processors treat collection agencies as high risk?
Processors price the chance of disputes, regulatory trouble and losses they might have to absorb. Collections carries all three: payers are often reluctant, payments are card-not-present, and complaints can turn into chargebacks or ACH returns.
From the acquirer’s seat, the common concerns are:
| Underwriting concern | Why it applies to collections | What the processor may ask for |
|---|---|---|
| Dispute and fraud ratio | Consumers may dispute a payment they later regret, or claim they never authorized it | Several months of processing statements, dispute history |
| Card-not-present volume | Most payments come by phone, portal or text-to-pay | Description of payment channels and authorization scripts |
| Regulatory exposure | FDCPA, Reg F, state licensing and UDAAP issues can lead to refunds or enforcement | State licenses, compliance policies, complaint log |
| Recurring payments | Payment plans create repeated debits that can be disputed | Authorization language, copies sent to consumers |
| Client trust funds | Agencies collect money owed to clients | Trust account setup, remittance process, bond where required |
None of these mean an agency can’t get an account. They mean the file you submit has to answer these questions before the underwriter asks.
What do processors review in a collection agency application?
Expect a file review closer to a bank onboarding than a retail signup. Most processors want to see that you are licensed where you collect, that you document consent, and that your dispute history is under control.
A practical document checklist:
- Entity and ownership documents, including beneficial owners.
- State collection licenses and bonds for each state you collect in. Our state collection licensing map is a starting point.
- Processing history, usually several months of statements, if you have them.
- Payment-channel descriptions: phone, portal, IVR, text-to-pay, and who takes each payment.
- Authorization scripts and recurring-payment terms, including how the consumer gets a copy.
- Compliance policies: FDCPA and Reg F procedures, complaint handling, refund policy.
- Fee disclosure, especially whether you charge any convenience or processing fee (see below).
- Data security posture, such as your PCI DSS validation level or your use of a hosted payment page that keeps card data off your systems.
If you are still setting up, our guide on how to start a collection agency covers licensing order and timing, and the collection CRM guide covers payment-portal features to look for.
How do reserves work on a collection agency merchant account?
A reserve is money the processor holds back from your deposits to cover future chargebacks or losses. The size, type and release schedule are set in your contract, not by a public rule, so read that section before you sign.
Common reserve structures you may see in a processing agreement:
| Reserve type | How it works | What to negotiate |
|---|---|---|
| Rolling reserve | A percentage of each day’s sales is held for a set period, then released | The percentage, the hold period, and a review date to reduce it |
| Upfront (capped) reserve | A fixed amount is funded at the start or built up to a cap | The cap amount and when it is released |
| Delayed funding | Deposits settle later than normal | The delay length and when standard funding resumes |
There is no published industry-standard reserve percentage for collections, and we won’t guess one. What you can control is the evidence: a low dispute rate, clean authorizations and a stable payment mix give you grounds to ask for a reduction at the review date.
What chargeback limits apply to collection agencies?
Card networks monitor merchants and acquirers that have too many disputes or fraud reports. Visa’s current program sets a U.S. “excessive merchant” threshold at a ratio of 150 basis points (1.5%) with at least 1,500 fraud reports plus disputes per month.
Visa folded its earlier fraud and dispute programs into the Visa Acquirer Monitoring Program (VAMP). Per Visa’s fact sheet:
- The VAMP ratio is the count of fraud reports plus disputes, divided by the count of settled card-not-present transactions.
- Thresholds took effect June 1, 2025, after an advisory period that ended September 30, 2025.
- The U.S. excessive-merchant threshold dropped from 220 to 150 basis points on April 1, 2026, with a minimum monthly count of 1,500 fraud reports plus disputes.
- Disputes resolved through pre-dispute tools are excluded from the ratio.
Source: Visa VAMP fact sheet.
The 1,500 minimum count means many small agencies won’t reach the Visa program at all. Your processor, though, can set stricter internal limits in your contract and act well before a network program would. Your contract’s dispute terms matter more day to day than the network threshold. We’ll cover dispute root causes and controls in a separate piece on chargebacks in collections.
What ACH rules matter for collection payments?
ACH debits run on Nacha’s Operating Rules. For collectors, three rules matter most: account validation for online debits, return-rate thresholds, and written authorization for recurring debits under Regulation E.
| Rule | What it requires | Source |
|---|---|---|
| WEB debit account validation | Online (WEB) debit originators must use a fraud detection system that includes account validation on first use of an account number or a change to it. Effective March 19, 2021 | Nacha |
| Unauthorized return threshold | Unauthorized debit returns (codes R05, R07, R10, R29, R51) above 0.5% trigger Nacha scrutiny | Nacha |
| Overall return level | Returns for any reason above 15% can prompt a Nacha inquiry into origination practices | Nacha |
| Preauthorized transfers | Recurring debits from a consumer’s account must be authorized in a writing signed or similarly authenticated by the consumer, and the consumer gets a copy | 12 CFR 1005.10(b) |
Unauthorized returns are the number to watch. A payment plan set up on a recorded call with no authenticated authorization and no copy sent is the kind of entry that comes back as unauthorized.
Can a collection agency charge a convenience fee?
Only when the agreement creating the debt expressly authorizes it or the law permits it. FDCPA section 808(1) and Regulation F bar collecting “any amount,” including fees, that doesn’t meet that test. A processor’s surcharge setting doesn’t change the rule.
The statute says a debt collector may not collect “any amount (including any interest, fee, charge, or expense incidental to the principal obligation) unless such amount is expressly authorized by the agreement creating the debt or permitted by law.” Regulation F repeats it at 12 CFR 1006.22(b). See 15 U.S.C. 1692f.
What changed is the CFPB’s guidance, not the law:
| Date | Event | Source |
|---|---|---|
| July 5, 2022 | CFPB advisory opinion said pay-to-pay or “convenience” fees for paying online or by phone violate §808(1) unless expressly authorized by the agreement or by law, including fees a third-party processor collects and shares with the collector | 87 FR 39733 |
| May 12, 2025 | CFPB withdrew 67 guidance documents, including the pay-to-pay advisory opinion, and said it would not prioritize enforcing withdrawn guidance | 90 FR 20084 |
The withdrawal removed an interpretation. It did not amend the FDCPA or Regulation F, and private plaintiffs and state regulators can still bring claims under the statute. State law adds another layer. Visa’s own surcharging Q&A (version dated February 15, 2024) says Visa understands that Connecticut, Maine, Massachusetts, Oklahoma and Puerto Rico prohibit surcharging, and that Colorado, Minnesota, New Jersey and New York have requirements. Visa adds that its list may contain errors and isn’t legal advice.
Visa’s own card rules also limit surcharges to credit cards (never debit or prepaid), require 30 days’ notice to your acquirer, and cap the surcharge at the lower of your merchant discount rate or 3%. Source: Visa merchant surcharging Q&A.
The practical takeaway: many agencies simply absorb processing costs and offer a no-fee payment option. Confirm any fee with counsel against the account agreement and the consumer’s state before turning it on.
How can an agency keep a high-risk merchant account in good standing?
Treat your processor like a regulator that can freeze your cash. Keep dispute and return rates low, document every authorization, disclose clearly, and answer underwriting reviews quickly with organized files.
Practical habits that help:
- Use clear descriptors. A billing descriptor that names your agency and a phone number cuts “I don’t recognize this charge” disputes.
- Send receipts and plan confirmations right away, with the amount, date and how to cancel.
- Respond to pre-dispute alerts where your processor offers them. Visa excludes disputes resolved this way from the VAMP ratio.
- Validate bank accounts before the first WEB debit, as Nacha requires.
- Keep two processors if your volume supports it, so one account review doesn’t stop all payments.
- Review your payment mix monthly: dispute ratio, unauthorized return rate and refund volume by channel.
- Keep card data off your systems with a hosted payment page or tokenization, and keep your PCI DSS validation current.
For the broader compliance picture, see our compliance hub and Regulation F guide.
Why does payment processing matter when you buy or sell debt?
Payment infrastructure decides how fast a portfolio produces cash. Buyers with stable processing, clean dispute records and compliant fee practices collect sooner and carry less risk, which is something sellers reasonably ask about when vetting buyers.
For buyers: before you bid on a large file, check that your processor limits, reserve terms and payment channels can handle the added volume. A sudden jump in volume or disputes can trigger a review at the worst time. Browse portfolios and buyer resources on our buyers page and in DebtHub.
For sellers: ask buyers how they take payments, whether they charge convenience fees, and how they handle disputes. The answers say a lot about how your former customers will be treated. If you’re preparing a sale, our sellers page explains the process.
DebtMarket is the confidential debt brokerage desk of Triton Financial Solutions, LLC. We are not a collection agency. Portfolios are shared NDA-first with 200+ qualified buyers, with no public auction, and complete files close in 1-14 days.
Key takeaways
| Topic | What to remember |
|---|---|
| Classification | Collection agencies use Visa MCC 7322; “high risk” is an acquirer underwriting label |
| Underwriting | Expect a file review: licenses, authorizations, dispute history, fee practices |
| Reserves | Set by contract; negotiate the percentage, hold period and review date |
| Card disputes | Visa’s U.S. excessive-merchant threshold is 150 bps with a 1,500 monthly count minimum (since April 1, 2026) |
| ACH | Validate accounts for WEB debits; watch the 0.5% unauthorized return threshold |
| Convenience fees | FDCPA §808(1) and Reg F still apply even though the CFPB’s 2022 opinion was withdrawn in 2025 |
Sources (all checked live November 3, 2026)
- Visa Merchant Data Standards Manual (October 2026): https://usa.visa.com/content/dam/VCOM/download/merchants/visa-merchant-data-standards-manual.pdf
- Visa Acquirer Monitoring Program fact sheet: https://corporate.visa.com/content/dam/VCOM/corporate/visa-perspectives/security-and-trust/documents/visa-acquirer-monitoring-program-fact-sheet-2025.pdf
- Visa merchant surcharging Q&A (version 02152024): https://www.visa.com/vcom-assets/content/dam/VCOM/global/support-legal/documents/merchant-surcharging-qa-for-web.pdf
- Nacha, Supplementing Fraud Detection Standards for WEB Debits: https://www.nacha.org/rules/supplementing-fraud-detection-standards-web-debits
- Nacha, ACH Network Risk and Enforcement Topics: https://www.nacha.org/rules/ach-network-risk-and-enforcement-topics
- 15 U.S.C. 1692f (FDCPA §808): https://www.law.cornell.edu/uscode/text/15/1692f
- 12 CFR 1006.22 (Regulation F): https://www.consumerfinance.gov/rules-policy/regulations/1006/22/
- 12 CFR 1005.10 (Regulation E): https://www.consumerfinance.gov/rules-policy/regulations/1005/10/
- CFPB, Debt Collection Practices (Regulation F); Pay-to-Pay Fees, 87 FR 39733 (July 5, 2022): https://www.federalregister.gov/documents/2022/07/05/2022-14230/debt-collection-practices-regulation-f-pay-to-pay-fees
- CFPB, Interpretive Rules, Policy Statements, and Advisory Opinions; Withdrawal, 90 FR 20084 (May 12, 2025): https://www.federalregister.gov/documents/2025/05/12/2025-08286/interpretive-rules-policy-statements-and-advisory-opinions-withdrawal
- PCI Security Standards Council, PCI DSS: https://www.pcisecuritystandards.org/standards/pci-dss/
This article is general industry information for an Intermediate audience. It is not legal advice. Processor terms, card network rules and state fee laws change, so confirm current requirements with your processor, the card networks and counsel before you change payment practices.