Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.methodfi.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Handling Partial Results

Connect may not discover every liability a user has. Design your product to treat partial results as the normal case.

​
Why Results May Be Incomplete

Not all liabilities appear on credit reports. Some debts (private loans between individuals, certain employer-provided benefits, some BNPL arrangements) are never reported to credit bureaus and won’t be found by Connect. Reporting delays. New accounts may not appear on a credit report for 30–60 days after opening. A user who just opened a credit card last week won’t see it in Connect results yet. Unmatched institutions. Method’s network covers 15,000+ institutions, but some smaller or newer creditors may not yet be supported. The tradeline exists on the credit report, but Method can’t create an actionable Account from it because the institution isn’t in Method’s network. Closed accounts. The first Connect returns both open and closed accounts. Closed accounts may have limited product availability (e.g., no payments, no updates).

​
Show what was found, supplement where possible

After Connect completes, display the discovered accounts. If you have access to additional bureau data the user, you can supplement the discovered set by ingesting raw credit report tradelines via Manual Connect: 
curl https://production.methodfi.com/entities/ent_au22b1fbFJbp8/manual_connect \
  -X POST \
  -H "Method-Version: 2025-12-01" \
  -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" \
  -H "Content-Type: application/json" \
  -d '{
    "bureau": "transunion",
    "tradelines": [
      {
        "type_code": "18",
        "portfolio_type_code": "revolving",
        "designator_code": "individual",
        "number": "5555555555555555",
        "creditor_name": "CAPITAL ONE",
        "creditor_code": "01DTV001",
        "balance": 500000,
        "highest_balance": 750000,
        "credit_limit": 1000000,
        "term": null,
        "next_payment_minimum_amount": 15000,
        "last_payment_amount": 20000,
        "payment_history": ["1", "1", "1"],
        "past_due_amount": 0,
        "delinquency_charge_off_amount": 0,
        "opened_at": "2016-11-25",
        "last_activity_date": "2024-05-01",
        "reported_date": "2024-05-01",
        "next_payment_due_date": "2024-06-01",
        "last_payment_date": "2024-05-01",
        "delinquency_first_start_date": null,
        "narrative_codes": [
          { "code": "FE", "description": "CREDIT CARD" }
        ]
      }
    ]
  }'
Manual Connect requires the full bureau tradeline schema (creditor codes, payment history, delinquency dates, narrative codes, etc.) — it is not a lightweight “user enters a missing account” flow. If you need that pattern, talk to your CSM about the right approach for your use case.

​
Enable Connect subscriptions for ongoing discovery

New liabilities that appear on future credit reports will be automatically discovered. See Connect Subscriptions.

​
Handle zero results gracefully

If Connect returns zero accounts (thin credit file), don’t show an empty state. Explain that the credit report didn’t contain tradelines and offer Manual Connect as the path forward.

​
Account-level product gaps

Even when an account is discovered, it may not support all products. Always check the products array before making assumptions: 
const account = await method.accounts.retrieve('acc_eKKmrXDpJBKgw');

if (account.products.includes('payment')) {
  // Safe to initiate payments
} else {
  // Data-only — can retrieve balances but can't send money
}
For the full Connect API, see the Connect reference.