LenderListMatch a deal Moderated MCA community
Email-verified discussions with role labels, lender-domain verification, and a moderation queue. Merchant PII does not belong here.
A useful placement question can include requested amount, monthly revenue, credit range, time in business, position, state, industry, average daily balance, deposit count, and recent negative days. It should not include
LenderList keeps sourced criteria active until it is corrected, replaced, or withdrawn. A six-month-old lender-confirmed buy box can still be correct, so age never removes a lender from search or matching. The date is co
A complete submission normally starts with the application, requested bank-statement period, current month activity when required, ownership details, existing position information, and the correct lender-specific documen
Comparing only the funding amount or factor rate can hide material differences. A useful comparison also identifies total payback, payment frequency, estimated payment burden, term or expected delivery period, prepayment
Restrictions should be lender-specific and sourced instead of copied from a generic industry list. A useful record identifies the lender, product, exact restricted category or code, whether exceptions exist, the source,
The matching API can be called after deal facts are normalized and before documents are routed. The response should remain advisory: show passed, failed, and unresolved checks, preserve the source timestamp, and require
A useful lender announcement states exactly what changed, the effective date, affected products, minimums or restrictions, submission contact, and a link to the current official guideline. Vague “we are funding” posts ar
A useful review describes a first-hand experience, approximate month, process stage, communication, and what happened without publishing confidential terms or merchant identity. Business owners and employees should not r
Posting standard