How should restricted-industry guidance be documented?
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, and when it was observed. Share general documentation practices only; do not post a merchant identity or confidential decline notice.
10 replies
Document the lender, product, industry description or code, source, effective date, and any stated exception path. A restriction for one product should not automatically be applied to every product from the same company.
Industry labels are not always consistent. If a guide says “financial services,” the record should preserve that wording instead of expanding it into an assumed list of every finance-related business. Exceptions should be marked as requiring approval.
We should also avoid copying a generic restricted list into a lender profile. If there is no lender-specific source, the field should stay unavailable and the deal can be marked for manual review.
Versioned source records solve most of this. Keep the exact source language, observation date, product scope, and reviewer decision so a later change does not erase the basis for the previous guidance.
How should we handle a lender rep approving an exception by email when the public guide still lists the industry as restricted?
Record the restriction and the exception separately. The exception should identify its scope and require confirmation for each new deal unless the lender publishes a broader change.
A one-off approval should never rewrite the general rule. It is evidence that exceptions may exist, not that the restriction disappeared.
The matcher can return “restricted—exception review available” instead of pass or fail when that distinction is sourced.
That wording is much safer than treating an exception as guaranteed. The ISO still knows there may be a path without overselling it.
And the merchant gets a truthful explanation: the industry needs manual approval, so timing and outcome are uncertain.