First-Party vs. Third-Party Collections: Whose Merchant Account?
First-party vs. third-party collections payment processing: whose merchant account gets the money, and what that means for descriptors and disputes.

Photo: Pixabay
On this page 6 sections
- First-Party vs. Third-Party Collections: How the Payment Flow Differs
- Early-Out Collections and the Merchant of Record
- Collection Agency Billing Descriptors and "Unrecognized" Disputes
- Who Owns the Chargeback Liability
- First-Party Collections Compliance When You Collect in the Creditor's Name
- Contract Clauses That Settle Payment Flows Before the First Call
Key takeaways
- Match the merchant of record to the name the consumer hears on the call. Early-out payments settle to the creditor's account, and third-party payments settle to the agency's.
- Running creditor-name calls through the agency's account invites "unrecognized" disputes. Putting the creditor's name on the agency's descriptor creates a worse problem.
- A contract moves chargeback costs between agency and creditor, but the dispute ratio stays on whichever account processed the payment.
- Put the payment flow, descriptor, dispute duties and card-token ownership in the service agreement before the first call goes out.
If your agency collects in the creditor's name, card payments belong in the creditor's merchant account. If you collect in your own name, they belong in yours. In first-party vs. third-party collections payment processing, the merchant of record should match the name the consumer hears on the phone and later reads on the card statement. That one choice sets the billing descriptor. It also decides who absorbs chargebacks, whose processing agreement carries the risk, and how a regulator reads your relationship with the creditor.
Trouble starts at agencies that run both kinds of work. Take a hypothetical: an agent calls as "the billing office at Riverside Medical," takes a card over the phone, and runs it through the agency's own account. Three weeks later the patient sees an unfamiliar company name on the statement and files a dispute. Each piece of that process worked as designed. Nobody designed the pieces to work together.
First-Party vs. Third-Party Collections: How the Payment Flow Differs
First-party collection, also called early-out, puts the agency in the role of the creditor's business office. Its accounts are early-stage delinquencies that haven't been charged off. Calls, letters and portals all use the creditor's name, and the consumer believes they are paying the hospital, utility or lender directly. Early-out pricing tends toward flat per-account or monthly fees rather than a percentage of what gets recovered.
Third-party collection works the other way. An agency doing this work identifies itself by its own name, works accounts that are in default or charged off, and earns a contingency fee. It collects the money, deposits it, and remits the creditor's share. Check your state's rules on trust accounting and remittance timing, because that part of the flow can fall under state collection law rather than card processing rules.
Payment flow follows from the model. In early-out work, the money belongs to the creditor and should reach the creditor directly. In third-party work, the consumer is dealing with the agency. That makes the agency the natural merchant of record: the company whose merchant account processes the sale and whose name the card networks treat as the seller.
Collection payments arrive through three channels, and all three have to line up: keyed entries by phone agents, online portal payments, and recurring payment plans. If a program gets the phone channel right but sends portal payments to a different account, it still produces mismatches.
Early-Out Collections and the Merchant of Record
Agencies can choose from three basic setups, plus a hybrid for shops that run both programs.
| Setup | Whose account | Descriptor shows | Who takes disputes | Fits |
|---|---|---|---|---|
| Creditor's account, agency as user | Creditor | Creditor's name | Creditor | Early-out / first-party |
| Agency's account, agency's name | Agency | Agency's name | Agency | Third-party |
| Agency's account, creditor's name | Agency | Creditor's name | Agency | Neither. Avoid it |
| Hybrid, separate programs | Each program on its own account | Matches each program | Matches each program | Agencies doing both |
Creditor's account, agency as authorized user. Agents key payments into the creditor's virtual terminal for phone payments, or the agency's portal posts to the creditor's gateway. Consumers see a descriptor that matches what they heard on the call. The creditor keeps a processing relationship built for a hospital or utility rather than a collection agency, and your agency skips its own high-risk underwriting. Two trade-offs come with this setup. First, your agency depends on the creditor's systems and reports to bill its fees. Second, because your agents handle the creditor's card data, your agency may have PCI compliance obligations of its own. Expect the creditor to ask for proof.
Agency's account, agency's name. This is the standard third-party setup. Your agency is underwritten as a collection agency, which acquirers commonly treat as a high-risk category. Plan for reserves, closer monitoring and stricter limits on which card types you accept. Our guide to whether collection agencies can accept credit cards covers the network rules on that point. Expect the application to go through high-risk merchant processing underwriting rather than a standard small-business review.
Agency's account with the creditor's name on the descriptor. This is the setup that gets agencies in trouble. A descriptor identifies the merchant of record, so putting another company's name on your account misrepresents who the merchant is. It also makes the account look like it's processing payments for another business, and processors and card networks scrutinize accounts that appear to do that. Raise it with your processor before you try anything like it, and assume an account found running this way is at risk of termination. If you collect in the creditor's name, use the creditor's account. Don't borrow the creditor's name for yours.
Hybrid. An agency that runs early-out for one client and third-party recovery for another should keep the two programs on separate accounts or separate merchant IDs. Each payment then settles where it belongs, and each descriptor matches its program.
Collection Agency Billing Descriptors and "Unrecognized" Disputes
A billing descriptor is the short text on the consumer's card statement. It shows up days or weeks after the call, by which time the consumer has forgotten the agent's name and doesn't connect "XYZ RCVRY SVCS" to the hospital bill they paid. Consumers paying a collection account may already be wary of the charge, so an unfamiliar name gives them a ready reason to dispute it.
Illustrative example, not a benchmark. An agency runs early-out for a regional hospital. It calls in the hospital's name and takes 600 card payments a month through its own account under its own name. Assume one patient in 100 doesn't recognize the charge and disputes it. That's six disputes every month. Each lost dispute costs the agency the payment plus its processor's chargeback fee. That fee is the processor's own pricing, not a network fee.
Fees are the smaller problem here. Six disputes on 600 payments is one dispute for every 100 transactions. Processors watch that ratio on every account, and they watch it more closely on a collection account. Call recordings will win some of those disputes. Every one of them still counts toward your ratio, though, and every one needs someone to build a response file. Move the same payments to the hospital's account under the hospital's descriptor and those disputes lose their main cause, because the patient recognizes the name.
Whichever account you use, these habits cut down on "I don't recognize this" disputes:
- Have agents read the exact descriptor text on the call ("This will show as RIVERSIDE MED BILLING on your statement").
- Send an email or text receipt at the time of payment that shows the descriptor text and a callback number.
- Ask your processor whether your descriptor can include a customer-service phone number. Support depends on the processor and the setup.
- Display the descriptor text on your portal's confirmation page. It belongs on the list of features in our piece on self-service payment portals for debtors.
Bank debits raise the same question. The company name on an ACH debit should be one the consumer recognizes, so confirm the naming requirements with your processor. Our article on TEL and WEB entries for collection agencies covers the authorization and return issues that apply on top of that.
Who Owns the Chargeback Liability
The merchant of record owns the chargeback with its acquirer, whatever your service agreement says. A contract can make the agency reimburse the creditor for lost disputes, or make the creditor absorb them. What it can't change is whose dispute ratio goes up, whose reserve gets adjusted, and whose account the processor reviews.
First-party setups have a practical gap here. Disputes land on the creditor's account, but the agency holds the evidence: the call recording, the authorization script, portal login and IP data, and the signed payment-plan terms. Dispute response windows are short, so the agreement needs a fast route for that evidence to get from the agency to whoever answers the dispute.
Recurring payment plans add another layer. When an agency sets up installments on the creditor's account, the stored card credentials sit in the creditor's gateway. A consumer who says "I canceled the plan with the agent" files the dispute through the creditor, and the agency's cancellation log becomes the creditor's evidence.
In third-party setups, all of this stays with the agency. That is simpler to run but carries more risk, because a collection account that develops a dispute problem has less room to recover than a typical retailer. If you've already been turned down, our article on why collection agency merchant accounts get declined walks through the common underwriting objections.
First-Party Collections Compliance When You Collect in the Creditor's Name
This section is general information, not legal advice. Confirm your program's structure with counsel who handles consumer collections.
Federal collection law treats outside collectors differently from creditors collecting their own debts. It's tempting to assume that calling in the creditor's name puts your agency on the creditor's side of that line. Don't assume it. Using the creditor's name changes what the consumer hears, but it doesn't settle how the law classifies the company making the call. Ask counsel where each of your programs falls.
Early-out programs turn on a second question, and it belongs on your counsel's list: was the debt already in default when your agency received it? The answer can depend on the credit agreement, the creditor's own policies and how courts in your jurisdiction have read the law. Watch for accounts that age into default while they're still in an early-out queue, because that's a common compliance gap. Federal regulations add further requirements for covered collectors, so ask counsel how they apply to each program you run.
State law is a separate layer. State licensing statutes have their own definitions of a collection agency, and those definitions don't always line up with federal law. Confirm your licensing obligations state by state. Card convenience fees in collections raise their own federal and state questions, so get a legal review before you add one.
Your payment flow also affects how the relationship looks from the outside. An agency that deposits consumer payments into its own account and then remits them looks more like a third-party collector than one whose agents post payments straight into the creditor's account. When an agency talks like a first-party shop but moves money like a third-party operation, fix the inconsistency before a regulator or a plaintiff's lawyer points it out. Federal enforcement priorities shift over time too, and we're following proposals such as the House bill that would restructure the CFPB.
Contract Clauses That Settle Payment Flows Before the First Call
Mismatches start in service agreements that cover compliance and fees but leave payments to "operational details." Put these terms in writing before an agent dials:
- Merchant of record. Name the account each channel (phone, portal, recurring) settles to. State that the agency won't process the creditor's accounts through any other account.
- Descriptor and callback number. Specify the exact descriptor text and phone number consumers will see. Require notice before either one changes.
- Dispute handling. Set who receives chargeback notices and the deadline for the agency to deliver evidence. List which records (recordings, authorizations, cancellation logs) the agency keeps and for how long.
- Cost allocation. Assign processing fees, chargeback fees and losses on disputes caused by agency error. Decide how disputes that agents could have prevented get handled.
- PCI responsibilities. Require current PCI compliance documentation for the agency's agents and systems. Our guide to PCI compliance for collection call centers covers the recording and agent-desktop issues that come up most.
- Token and data ownership. Spell out who owns stored card credentials and payment-plan data, and what happens to active plans when the contract ends. Tokens don't always transfer between gateways, so plan how consumers on installment plans will re-enroll.
- Refund authority. Define who can issue refunds or reverse payments, and up to what amount.
- Default handoff. Fix the point at which an account leaves the early-out program, so later payments move to the correct account and descriptor.
For a new early-out client, decide which account each channel settles to and get that decision in writing before the first call. If you're setting up a separate account for your own third-party work, contact the MannyPay team to talk through how your programs are structured before you apply. Underwriting decides whether an account is approved.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


