Collections Referrals: Follow the Funds

What must be clear before an ISO introduces a collector?

The receiving partner needs to know which entity is collecting what kind of obligation and under whose authority. Start with the business role and payment flow. A company that collects for clients and a company collecting purchased receivables should not receive identical introductions merely because both accept payments through a website.

MerchantBridge's suggested preparation begins with an aggregate business description. It does not require a debtor list, account balances tied to names or copies of collection correspondence. A focused introduction can expose the unresolved questions without exposing consumer records.

Sources: Consumer Financial Protection Bureau: Regulation F: Section 1006.2 definitions; MerchantBridge Advisors: Related MerchantBridge industry overview

Does owning the debt remove the regulatory question?

No automatic conclusion follows. CFPB Regulation F includes both a principal-purpose route and a collecting-for-another route in its debt-collector definition, with specified exclusions. Ownership by itself does not settle the analysis. Applicable federal and state requirements need review based on the actual business and obligations.

The ISO should record the merchant's stated role and licensing position without certifying either. Distinguish consumer from commercial obligations, identify relevant jurisdictions and flag any uncertainty for qualified review. Do not rely on a label such as receivables company to bypass those questions.

How do two fictional flows differ?

Consider an agency that receives a fictional $1,000 payment for a client, retains a contractually agreed $100 fee and remits $900. The gross amount collected is $1,000, even though the agency's fee revenue is $100. The referral should explain collection and remittance responsibilities instead of presenting only fee revenue as payment volume.

Now consider a business collecting $1,000 on a receivable it owns. There may be no client remittance in that example, but the ownership, authority and regulatory questions remain. Neither example establishes whether a payment arrangement is lawful, accepted or correctly priced; they show why a short revenue figure cannot replace a funds-flow description.

Which questions belong in the handoff checklist?

Ask for confirmed business facts and explicitly mark gaps. These fields are an advisory workflow, not a universal provider application.

• Legal collector, obligation owner and authority to collect.
• Consumer or commercial obligation types and jurisdictions served.
• Gross customer collections versus fee revenue and client remittances.
• Payment channels, recurring permissions if applicable and typical payment amounts.
• Who handles mistaken payments, refunds and allocation questions.
• Whether client funds are received, held or distributed, and by which entity.

When should an ISO narrow or hold the request?

If the business performs several roles, separate them. One company may collect for clients in one division and own receivables in another. A summary that blends both can leave the receiving partner unable to determine which flow is proposed. Ask for a fictional example of each and identify the unresolved operational responsibility.

Hold the affected flow if the collector cannot explain its authority or the destination of receipts. More consumer documents will not fix an unclear business description at this stage. Once the scope is intelligible, discuss the referral using the referrer's details and let the prospective partner determine its requirements and decision. Do not promise compensation, acceptance or exclusive handling.