Skip to main content

​
Overview

The funder registry is a persistent, org-scoped directory of every lender and funder your organization has encountered. Each entry carries metadata (contact info, type, states served) and, critically, a list of transaction description aliases — the strings that appear in bank statement ACH descriptions when that funder pulls or pushes money. When the parser runs, the registry is injected into the loan classification and position detection prompts. The LLM uses the aliases to match transaction groups to known funders, even when the raw description is buried under sponsor bank names and ACH rail metadata. A transaction reading ACH DEBIT ORIG CO NAME GREENLINE FUNDING CO ENTRY DESCR PAYMENT PPD gets resolved to “Greenline Funding” because the registry carries that alias.

​
How it works

Two-tier initialization. Pathway ships a set of global default funders (the major MCA companies, common lenders). When your organization first accesses the registry, these defaults are atomically copied into your org’s own namespace. From that point forward, your copy is independent — you can add funders, remove ones you’ll never see, and customize aliases without affecting anyone else. Prompt injection. During classification, the registry serializes into a reference table inside the LLM prompt: 
funder_id, funder_name, funder_aliases
1, Greenline Funding, ['GREENLINE FUNDING', 'GREENLINE CAP', 'GRN FUNDING']
2, Libertas Funding, ['LIBERTAS', 'LIBERTAS FUNDING LLC']
...
The model returns funder IDs rather than free-text names. Each matched position gets enriched with the full funder record — contact info, website, type — so the debt board can display it without a second lookup. Corrections feed forward. When an underwriter reassigns a position to a different funder or adds a new alias, that correction lives in the registry for every subsequent parse. The system does not need to re-learn what it has already been told. Over time, each organization’s registry converges toward a complete map of the funders they actually encounter.

​
Managing funders

Access the funder directory from your organization settings, or through the embeddable funder directory view. Each funder entry supports:
FieldPurpose
TitleDisplay name (e.g. “Greenline Funding”)
AliasesTransaction description strings the parser should match against
TypeLender, MCA funder, factoring company, debt consolidator, ISO/broker, or bank
ContactName, email, phone, address — surfaces on position cards in the debt board
States servedGeographic coverage, useful when submitting deals
RankSort order in your directory
You can:
  • Add funders your org works with that aren’t in the defaults
  • Edit aliases when you encounter a new description variant for a known funder
  • Delete funders you’ll never see
  • Reset to global defaults if needed

​
API

Funder management is available through the API for organizations that want to sync their registry programmatically. 
GET    /funders          # List all funders for your org
GET    /funders/:id      # Get a single funder
POST   /funders          # Create a new funder
PATCH  /funders/:id      # Update funder metadata or aliases
DELETE /funders/:id      # Remove a funder
POST   /funders/reset    # Reset to global defaults
The transaction_description_aliases array in funder_meta is the field that drives classification. Adding an alias here is the most direct way to teach the parser about a new description variant.