A collection agency merchant account is a dedicated processing account underwritten for consumer-debt payments, not a retail account that happens to take a card. Mainstream processors decline the category because the cardholder often doesn’t recognize the charge, even when the debt is real. We place the file with an acquirer that boards the category. The bank still decides.
What a collection agency file looks like to an underwriter
An underwriter starts with who is paying whom, for what, and whether that person expected the debit.
A shop collecting its own past-due invoices isn’t the same file as a third-party agency working paper for a hospital, a telecom, or a student lender. Purchased debt is a third shape. The bank wants the paper trail to match the website, the scripts, and the client contracts. A mismatch is a decline.
Consumer-debt payments look like forced or unexpected charges on a statement. The cardholder may have forgotten the original bill. They may never have spoken to your agency. A relative may have paid a card and said nothing. The debt can be valid and the dispute still lands. That is the risk the bank is reading, not a verdict on whether collections is legitimate work.
This is why collection agency merchant accounts sit inside what makes a business high risk. High risk here means elevated disputes, complaints, and regulatory attention. It’s not a code you disguise on the application. Honest disclosure of the model is the only version of the file that survives review. Calling the work “billing services” while taking consumer-debt payments is how an aggregator shuts you off overnight.
What they actually open: entity documents, ownership, processing history if it exists, and a plain description of the debt. They want original-creditor mix, typical payment size, cards versus ACH, and whether you take the payment by phone, portal, mail, or an office window. Volume projections with no statements get a harder look than a messy but real history.
Collections files get the same reading described in what underwriting actually looks at, with more weight on consent, the descriptor, and how you handle a person who swears they never authorized the debit. If the file can’t be placed with any acquirer we know of, we tell you that. We don’t send an application in anyway.
Cards, ACH, and running both on one business
Cards and ACH are two underwriting questions on the same business.
An acquirer that will board ACH for collections may still refuse cards. Asking for both on one application is normal. Pretending one method will hide the other isn’t.
Card rails give the cardholder a dispute button. That button is why collections volume produces chargebacks even when the original creditor’s records are clean. The person sees an unknown name, a dollar amount they didn’t plan this week, and they call the issuer. The issuer often sides with them first. You then prove authorization, identity, and the debt. That cycle costs time.
ACH pulls from a bank account the consumer named. It doesn’t erase risk. Returns, unauthorized claims, and stop-payments still exist. Some people will give a routing number more readily than a card. Others won’t give a bank account to an agency they just heard from. Neither method is safer in the abstract. Each one fails in a different way.
Running both on one business is readable when the file says so. The website, the payment page, and the application should name the same methods. A card-only account with ACH running somewhere else looks like two businesses. Underwriters treat that as a problem.
| Question the bank asks | Cards | ACH |
|---|---|---|
| What the payer sees | A statement line they may not recognize | A bank debit they may not remember authorizing |
| How a fight usually starts | An issuer dispute on an unexpected charge | A return, a stop-payment, or an unauthorized claim |
| What the file has to show | Card authorization and a matching descriptor | ACH authorization tied to that person and that debt |
| Why one method can be refused | Dispute volume on unrecognized charges | Return risk and weak consent records |
None of that is a reason to split volume across processors. That is how you lose both accounts. One honest file, both methods named, is the version that can be placed.
Descriptors, complaints, and dispute patterns
The descriptor is the single line on the card statement. If it doesn’t match how you named yourself on the call or the letter, the charge looks like a theft.
Collections descriptors that print a DBA the consumer never heard, or a generic “payment services” string, produce disputes that ignore whether the debt is owed. Use the name already in the consumer’s letters. Put a callback they can actually reach on the statement where the processor allows it. Send a receipt that repeats the original-creditor name, the account reference, and the amount.
Complaints travel. The Consumer Financial Protection Bureau publishes consumer complaint information on debt collection, and underwriters already know the category draws it. A pile of “I never authorized this payment” notes, even when you later win the dispute, tells the bank the front door is messy. The FTC’s debt collection FAQs are written for consumers. They still show the language that later shows up in a chargeback.
Don’t treat a complaint as a courtroom score. Treat it as a payments problem. A person who can reach a human, get a copy of the authorization, and see the original creditor on the receipt is less likely to open a dispute. A person who only gets a voicemail and a surprise debit will open one.
Dispute patterns in collections cluster around three scenes. A phone payment taken with no recording and no written follow-up. A portal pay where the descriptor doesn’t match the agency name on the letter. A recurring arrangement the consumer thought was a one-time deal. Each one is preventable with consent capture and a matching descriptor. None of them is fixed by arguing the debt on the form.
If disputes are already climbing, the work is operational. Clearer billing descriptors, faster replies, and a refund path for true errors move the ratio down. That is the same discipline as how to lower your chargeback ratio in any high-risk vertical.
Documents that make the file readable
A readable file is a stack an underwriter can finish without guessing.
Lead with the business: formation documents, ownership, and a one-page description of the work. First-party, third-party, or purchased paper. Named original-creditor types and the states you work. How a payment is requested: phone, mail, portal, or in office. How you record consent for cards and for ACH. That page should match the website. If the site still looks like a generic financial-services brochure, fix the site before the application.
Then the money trail. Processing statements if you have them, including chargebacks, refunds, and returns, not a summary that hides them. Business bank statements. Deposit-account proof. If a prior processor closed you, say so and include the letter. Silence reads worse than a closure you can explain.
Policies belong in the packet, in plain language. Refund and void rules. How a consumer reaches you after a debit. How you handle a dispute packet. Security language that matches how you actually take cards, not a copied paragraph. A privacy policy that names collections.
Client contracts, redacted if needed, show you aren’t inventing the portfolio. Sample letters and a payment-page screenshot show the consumer the same names the account will print. Authorization language for a card and for ACH, as you actually use it. A recorded-call policy if you take phone payments.
A debt collection merchant account is underwritten as high risk merchant services, which means the acquiring bank reads the category on purpose. You see the full schedule, including any reserve, before you sign. An honest rate doesn’t exist before that reading. If the file can’t be placed, you hear that instead of a hopeful application.
Frequently asked questions
Can a collection agency get a merchant account? Agencies get dedicated accounts when an acquirer actually boards the category. Mainstream aggregators often won’t. Difficulty tracks the file: third-party and purchased debt, phone card payments, and a messy prior statement are harder reads than first-party invoices with clean history. Nobody can honestly promise the bank’s yes.
Do I need cards, ACH, or both? Ask for the methods you actually use, on one application, with matching website copy. Cards bring issuer disputes on unrecognized statement lines. ACH brings returns and unauthorized-debit claims. Neither method hides the other. Splitting them across processors to look smaller is how accounts get closed.
Why do valid debts still produce chargebacks? The cardholder sees a name and amount they didn’t expect. Issuers give them a dispute path. Your job is authorization, a matching descriptor, and a way to talk to the person before they call the bank. Winning the underlying debt doesn’t automatically win the card dispute.
How do I know if I already have a merchant account? Look at the processing statements and the merchant ID, not the software logo on your portal. An aggregator account sits under someone else’s master account and can be switched off without a dedicated underwriting conversation. A dedicated account is in your entity’s name, with an acquiring bank behind it.
Can you remove a MATCH listing if a collections account was terminated? No. Only the acquirer that placed the listing can request removal, and only in the narrow cases Mastercard publishes. We don’t sell removal. If you have a listing, disclose it. Hiding it ends the next application.