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 Account Edge Cases

​
1. Accounts Requiring Verification

Some liability accounts discovered through Connect may appear in restricted_products with capabilities that require elevated verification (e.g., an account verification session). This is common for payment-capable accounts where Method needs additional confirmation. Create an Account Verification Session to unlock these products.

​
2. Product Limitations by Account Type

Not all accounts support all products. Credit cards support Card Brand and Payment Instruments; auto loans support Payoffs; most liability types support Updates and Balances. Always check the products array. See the Liability Types page for a breakdown.

​
3. Status Changes Mid-Operation

If an account transitions to disabled or closed while you have in-flight operations (a pending payment, an in-progress update), those operations may fail. Design your flows to:
  • Check account status before initiating operations
  • Handle account.disabled and account.closed webhooks gracefully
  • Show appropriate UI messages when an account is no longer available
See the Account Lifecycle guide for status transitions and webhook details.

​
4. Duplicate Accounts

Connect may discover the same underlying account multiple times if the user has accounts reported under slightly different names or through different credit bureaus. Method does attempt to de-duplicate these liability accounts, however instances do occur. Reach out to your CSM if this uncommon event occurs for one of your users.

​
5. Authorized User Accounts

Connect discovers all accounts on a user’s credit report, including accounts where they are an authorized user (not the primary holder). The liability.ownership field indicates the relationship: primary, authorized, joint, or unknown. Consider whether your product should treat authorized-user accounts differently (e.g., payments on authorized-user cards may not be appropriate for debt consolidation flows).

​
6. Closed / Paid-Off Accounts

Accounts with zero balance or closed status at the financial institution may still appear in Connect results (they remain on the credit report). These accounts will have status: closed and limited product availability. Filter them in your UI if they’re not relevant to your use case. When an Entity’s consent is withdrawn (via the Consent endpoint), their accounts are disabled and data access is revoked. Your application should handle this gracefully — remove the accounts from active views and inform the user.
The key principle: design your application to check account status and product availability dynamically, and listen for webhook notifications about status changes. Accounts are living objects, and your application should respond to their state changes in real time rather than assuming a static state. For the full Accounts API, see the Accounts reference.