# December Updates Source: https://docs.methodfi.com/changelog/2024/december ## New Features ### New Method Dashboard title We’re thrilled to announce early access to the **all-new Method Dashboard**, purposefully redesigned to harness the full potential of our API’s V2 capabilities. This intuitive interface is crafted to empower both technical and non-technical team members with: * Role-based access control * Advanced data visualization * Custom reporting capabilities * Universal search functionality * Self-service team management * Key rotation tools * SSO and Passkey authentication Everyone across your team can now use the new Method Dashboard: * **CX** – monitor and troubleshoot any issues associated with end-user data. * **Engineering** – create API keys and monitor webhooks. * **Finance** – view high-level metrics to better understand billing. **How to access?** Dashboard v2 is available for all teams, including existing ones, ensuring a seamless transition to the new interface. Log in with your email at [app.methodfi.com](https://app.methodfi.com) to explore the new features! ### Vehicles API title The [Vehicles API](https://docs.methodfi.com/reference/entities/vehicles/overview) enables your application to access detailed vehicle information with minimal PII. This data can help you unlock valuable insights and drive better decision-making. **Key Use Cases** * **Increase conversion** with pre-filled vehicle details by optimizing loan repayment terms using the vehicle's depreciation curve. * **Enhance credit risk underwriting** by leveraging vehicle ownership details. * **Enable personalized financial management** by correlating vehicle data with user behavior insights. For example, you can retrieve data such as the vehicle's `VIN`, `year`, `make`, `model`, `color`, and `style`. The Vehicles API is now available to all teams on Method’s V2 API (version: 2024-04-04). Contact your Method CSM to get access! *** ## Improvements ### Account Verification Limits To bolster system security and performance, we've introduced new verification limits: * **Account Verification Session limits**: Up to 10 failed attempts per session. * **Account-level verification limits**: * Maximum of 5 sessions per verification type. * Maximum of 10 total sessions across all types. For more details, visit [Account Verification Sessions Errors](https://docs.methodfi.com/reference/errors/account-verification-session-errors). *** ## SDK Updates * Released [version 1.1.5](https://github.com/MethodFi/method-python/releases/tag/v1.1.5) of `method-python`. * [Vehicles API](https://docs.methodfi.com/reference/entities/vehicles/overview) is now available in `method-python`. * Released [version 1.1.6](https://github.com/MethodFi/method-node/releases/tag/v1.1.6) of `method-node`. * [Vehicles API](https://docs.methodfi.com/reference/entities/vehicles/overview) is now available in `method-node`. # November Updates Source: https://docs.methodfi.com/changelog/2024/november ## New Features ### Payment Posted Confirmation title We’re excited to announce [`posted`](https://docs.methodfi.com/reference/payments/overview#possible-enum-values:~:text=The%20Payment%20has%20been%20posted%20to%20the%20destination%20Account), a new payment status that closes the loop on payments by confirming when they have successfully landed in your users’ accounts. With **real-time account data**, Method now provides a level of visibility that was previously unavailable in the U.S. financial system. By knowing if and when a payment has been applied, you can deliver timely and actionable updates to your users—boosting confidence and creating a seamless payment experience. **Key highlights:** * **Enabled for all payments**: The feature is live for all teams and payments processed via Method’s V2 API (version: `2024-04-04`) going forward. * **No action required**: Start using this feature immediately—just consume the new status in your integration. * **75% coverage**: We expect approximately 75% visibility into posted status, with improved coverage as more accounts are subscribed to updates. * **Unlock new use cases**: Use the posted status to notify users via push notifications, emails, or in-app messages, keeping them informed and engaged. * **Account subscription required**: In a future release, the posted status will only be available for accounts subscribed to updates. ### New Method Brand title We’re excited to introduce Method’s new visual identity, marking a new chapter in our journey under the same thesis we had on day one: consumer financial data is a walled garden, and we’re going to be the ones to open it up. The updated design features: * A new icon and wordmark * A refined color palette centered around Method Opal: a bold, fresh, and vibrant cyan * A new [website](https://methodfi.com/) Read more about the redesign [here](https://methodfi.com/blog/rebranding-method). *** ## Improvements ### Detailed Webhook Errors [Webhook Errors](https://docs.methodfi.com/reference/errors/webhook-errors) now includes detailed explanations of issues that caused your webhook to be disabled. Webhook objects now feature an `error` field following the common Method error format. The error codes for webhook errors are: * 25001 – `WEBHOOK_DISABLED_FAILED_OTHER`: Indicates five consecutive failures not classified as 4XX, 5XX, or timeouts. * 25002 – `WEBHOOK_DISABLED_RECEIVED_4XX_ERROR`: The endpoint returned client errors (4XX) five times. * 25003 – `WEBHOOK_DISABLED_RECEIVED_5XX_ERROR`: The endpoint returned server errors (5XX) five times. * 25004 – `WEBHOOK_DISABLED_TIMEOUT_ON_RESPONSE`: No valid response received within 5 seconds for five consecutive attempts. ### New List Endpoints We’ve expanded our API capabilities by introducing list functionality for the following resources, allowing you to retrieve comprehensive collections, such as all updates or credit scores, for a specific account or entity. * [Attributes](https://docs.methodfi.com/reference/entities/attributes/list) * [Credit Scores](https://docs.methodfi.com/reference/entities/credit-scores/list) * [Connects](https://docs.methodfi.com/reference/entities/connect/list) * [Identities](https://docs.methodfi.com/reference/entities/identities/list) * [Entity Verification Sessions](https://docs.methodfi.com/reference/entities/verification-sessions/list) * [Card Brands](https://docs.methodfi.com/reference/accounts/card-brands/list) * [Account Updates](https://docs.methodfi.com/reference/accounts/updates/list) * [Payoffs](https://docs.methodfi.com/reference/accounts/payoffs/list) * [Sensitive](https://docs.methodfi.com/reference/accounts/sensitive/list) * [Account Balances](https://docs.methodfi.com/reference/accounts/balances/list) * [Account Verification Sessions](https://docs.methodfi.com/reference/accounts/verification-sessions/list) ### Elements API * Removed the ability to pass in `card_brand` in the `products` array when creating an [Element Token](https://docs.methodfi.com/reference/elements/tokens). *** ## SDK Updates * Released [version 1.1.4](https://github.com/MethodFi/method-python/releases/tag/v1.1.4) of Method Python client (`method-python`). * All new `list` endpoints are now available in the Python client. * Added `posted` as an enum value for the `payment.status` field. * Released [version 1.1.5](https://github.com/MethodFi/method-node/releases/tag/v1.1.5) of Method Node.js client (`method-node`). * All new `list` endpoints are now available in the Node.js client. * Added `posted` as an enum value for the `payment.status` field. # October Updates Source: https://docs.methodfi.com/changelog/2024/october ## New Products ### Events API title The [Events API](https://docs.methodfi.com/reference/events/overview) allows your application to monitor specific changes to Method resources. * For example, you can now be notified when an entity's credit score increases (event type: `credit_score.increased`) or if new derogatory marks appear (event type: `attribute.credit_health_derogatory_marks.increased`) * Events deliver detailed and actionable notifications across all Method products and resources, making webhooks more targeted and specific. This ensures you receive alerts for the updates that matter to your application and users. * Events are classified into two types: * Literal changes: Direct updates to a specific field in a resource. * Computed changes: Interpreted states derived from multiple field changes or comparisons across different records. * The Events API is now available to all teams on Method’s V2 API (version: 2024-04-04). This launch includes 10 initial events, with over 100 additional events planned for release in the coming weeks. ### Attributes API title The [Attributes API](https://docs.methodfi.com/reference/entities/attributes/overview) offers a powerful summary of financial profile metrics across all Method API resources. * For example, it provides real-time indicators on credit utilization, payment reliability, account age, and derogatory marks, allowing developers to access these metrics directly without piecing together data from multiple endpoints. * Powered by Method’s real-time data integrations, it provides up-to-date insights ensuring your application accesses the most current data for faster, more informed decisions. * This initial release emphasizes credit health attributes, offering a holistic view of financial stability and risk. * For information on accessing the Attributes API, please reach out to your Method CSM. *** ## Improvements ### Card Brands API * Improved our card network integrations (Visa and Mastercard) to deliver lower latencies on Card Brands API requests. * Expanded coverage across all card products, including providing a reliable unique ID associated with each card product (for example all Chase Sapphire Reserve's across all entities will return the same brand ID) * Brand ID is returned within `card_brand.brands[x].id` in the format `brand_*`. ### Credit Scores API * We've upgraded our Credit Scores API to use VantageScore 4.0, the latest version of the scoring model. * VantageScore 4.0 provides more predictive scoring by incorporating machine learning techniques and trended credit data, which analyzes credit behaviors over time rather than just a snapshot. * This upgrade enables more accurate credit risk assessment, especially for consumers with limited credit history. *** ## SDK Updates * Released [version 1.1.2](https://github.com/MethodFi/method-python/releases/tag/v1.1.2) of Method Python client (`method-python`). * [Entity Attributes API](https://docs.methodfi.com/reference/entities/attributes/overview) is now available in the Python client. * [Events API](https://docs.methodfi.com/reference/events/overview) is now available in the Python client. * Released [version 1.1.3](https://github.com/MethodFi/method-node/releases/tag/v1.1.3) of Method Node.js client (`method-node`). * [Entity Attributes API](https://docs.methodfi.com/reference/entities/attributes/overview) is now available in the Node.js client. * [Events API](https://docs.methodfi.com/reference/events/overview) is now available in the Node.js client. * Released [version 2 of Method API Postman Collection](https://www.postman.com/methodfi/method-api/collection/8d5j00b/method-api-v2). # September Updates Source: https://docs.methodfi.com/changelog/2024/september ## Improvements ### Performance & Infrastructure * Improved idempotency locking mechanism to handle simultaneous idempotent requests received across different regions / PoP. * Under-the-hood liability payment rail improvements to faster settlement time across all major FIs. * Card Brand has been optimized for increased success speed. * Expanded checks for invalid update payload from upstream data providers. ### Payment Coverage * Released new integration with SoFi Personal Loans for near real-time payment settlement speed. * Payment channels for Sallie Mae, US Bank, and AMEX have been revamped and optimized for speed of posting. * Additional personal loan payment channels have been enabled - improving payment coverage and speed to posting. * BMO Harris credit cards are now fully payable when account is connected via Method Connect. ### Developer Experience * `micro_deposits` verification sessions are now simulatable in dev. * Speed of `micro_deposists` simulation in dev environment has been increased. * Expanded Card Brand simulated response in dev environment. * Improved Student Loans [updates](https://docs.methodfi.com/reference/accounts/updates/overview) documentation for dev environment responses. * Element now throws an error if any of the requested products are not enabled for the requesting team. ### Account Connectivity * Improved account update stability for Quicken Loans, Home Depot (Citi), Credit One, and other major FIs. * "Instant Link" verification was optimized across all networks. * Visual interaction during the manual Connect Element flow have been streamlined to optimize for conversion. ### Reporting * Daily emailed reconciliation reports now include the team name in the subject line. * e.g. (`Method: Daily ACH Report`) -> (`Method: Daily ACH Report for ${team_name}`) *** ## SDK Updates * Released [version 1.1.0](https://github.com/MethodFi/method-python/releases/tag/v1.1.0) of Method Python client (`method-python`). * [Request ID](/reference/request-id) is now easily accessible via the `last_response` property - we highly recommend logging the request ID for faster issue resolution. * This update also includes security updates and test coverage expansion. * Released [version 1.1.1](https://github.com/MethodFi/method-node/releases/tag/v1.1.1) of Method Node.js client (`method-node`). * [Request ID](/reference/request-id) is now easily accessible via the `last_response` property - we highly recommend logging the request ID for faster issue resolution. * This update also includes security updates and test coverage expansion. # April Updates Source: https://docs.methodfi.com/changelog/2025/april ## New Features ### Dashboard Updates sso We're continuing to improve the Dashboard experience with a few powerful updates: * **SSO Support** – You can now log in using Single Sign-On. Reach out to your Method CSM to enable SSO for your team. * **Multi-Team Search** – If you're a member of multiple teams, you can now quickly search and switch between them with ease. * **PDF Export** – It is now possible to download Entity and Account details as a PDF. Contact your Method CSM to get access to this feature. ## Improvements ### Entity Attribute Handling We've updated how Entity Attributes are requested. You must now explicitly specify which attributes you'd like to retrieve using a new payload format. Some attributes are restricted by default. Reach out to your Method CSM to get access to these attributes. ```js theme={null} const response = await method .entities('ent_TYHMaRJUUeJ7U') .attributes .create(); ``` ```js theme={null} const response = await method .entities('ent_TYHMaRJUUeJ7U') .attributes .create({ attributes: [ "credit_health_credit_card_usage", "credit_health_derogatory_marks", "credit_health_hard_inquiries", "credit_health_soft_inquiries", "credit_health_total_accounts", "credit_health_credit_age", "credit_health_payment_history", "credit_health_open_accounts", "credit_health_entity_delinquent" ] }); ``` For more details, refer to the [Entity Attributes API](https://docs.methodfi.com/reference/entities/attributes/create). ### Entity Subscription Creation Entity subscription creation has been updated to support a new payload format. ```js theme={null} const response = await method .entities('ent_TYHMaRJUUeJ7U') .subscriptions .create('credit_score'); ``` ```js theme={null} const response = await method .entities('ent_TYHMaRJUUeJ7U') .subscriptions .create({ enroll: 'credit_score', }); ``` To enroll in an Entity Attribute subscription, use this format: ```js theme={null} const response = await method .entities('ent_TYHMaRJUUeJ7U') .subscriptions .create({ enroll: 'attribute', payload: { attributes: { requested_attributes: [ 'credit_health_credit_card_usage', 'credit_health_derogatory_marks' ] } } }); ``` For more details, refer to the [Entity Subscriptions API](https://docs.methodfi.com/reference/entities/subscriptions/create). ## SDK Updates * Released [version 1.1.14](https://github.com/MethodFi/method-node/releases/tag/v1.1.14) of `method-node` * Released [version 1.1.13](https://github.com/MethodFi/method-python/releases/tag/v1.1.13) of `method-python` # August Updates Source: https://docs.methodfi.com/changelog/2025/august ## New Features ### Opal opal We're excited to introduce [Opal](/opal/overview), our new embedded UI that can easily be dropped into your existing onboarding flow, enabling a white-labeled, seamless connection to Method. It replaces our current Element UI, allowing you to customize the copy, themes, and other UI components to maintain continuity in your interface and prevent users from feeling like they are moving to a third-party app. Opal has four different components: * **Identity Verification (IDV):** collects, confirms, and verifies a user’s identity * **Connect (CXN):** surfaces all of a user's liability accounts * **Account Verification (AVF):** verifies credit card details and tokenizes them for payments and checkout use cases * **Transactions (TXN):** enables users to select cards that they wish to link transaction data **How it works:** * Opal is a drop-in SDK, designed for quick and easy integration with minimal effort to implement * Launch with a single token that’s generated with a mode (e.g., connect, card connect, etc.) and whatever additional parameters you choose * Once launched, Method handles all of the business logic of the flow, automatically orchestrating all of the information the user needs to provide and determining what part of the flow to route the user to next * Tokens are persistent - users can pick up exactly where they dropped off * UI is embedded via JavaScript, React, or React Native For more information, please visit the [Opal Quickstart](/opal/quickstart) page. # December Updates Source: https://docs.methodfi.com/changelog/2025/december ## New features ### Payment Instruments API Method now supports inbound funding workflows. We’ve added a new `PaymentInstrument` type: `inbound_achwire_payment` which allows liability accounts (e.g., loans, credit cards) to receive direct payments via ACH or wire transfer. * This feature provisions a unique virtual account number and routing number linked to a specific Method Account, effectively making the underlying liability routable. Third parties can send funds directly to these credentials, and Method automatically applies the funds to the associated account, without requiring you to explicitly create a Payment. **How it works:** 1. **Create Instrument**: Create a Payment Instrument of type `inbound_achwire_payment` for a specific Method Account 2. **Receive Banking Details**: Method returns unique `account_number` and `routing_number` 3. **Share with a Third Party**: Provide these banking details to a third party (e.g., payroll provider, refinance lender, or another bank) 4. **Inbound Transfer**: When funds are sent to these credentials, Method receives the inbound ACH or wire transfer 5. **Automatic Application**: Method automatically applies the received funds to the associated account Available when passing `Method-Version: 2025-12-01` in the request header. ## Improvements ### Simulate API The [Simulate API](/reference/simulations/overview) now supports retrieving micro-deposit amounts and simulating inbound ACH / wire payments for inbound\_achwire\_payment Payment Instruments — making it easier for developers to test account verification and inbound payment flows in the development environment. **[Retrieve Micro-deposit Amounts](/reference/simulations/verification-sessions/get-microdeposit-amounts)** * This endpoint enables developers to retrieve the exact micro-deposit amounts required to complete ACH account verification flows in the development environment. **[Simulate Inbound ACH/Wire Payments](/reference/simulations/payment_instruments/create)** * This endpoint allows developers to simulate receiving an inbound payment and triggers the same automatic payment application logic used in production. This API is available in the development environment only. For more information, visit the [Simulations API](/reference/simulations/overview) documentation. ### Webhooks We added support for a new webhook event type: `account.number.update`. * This account-level webhook is triggered when an account number has been updated, allowing developers to be notified of account number changes without polling. For more information, visit the [Webhooks API](/reference/webhooks/overview) documentation. ### Entities API The Entities API now supports updating `metadata` via `PUT /entities/{ent_id}`. * This enables developers to update an Entity's metadata without recreating the Entity, simplifying lifecycle management. For more information, please refer to the [Update an Entity](/reference/entities/update-entity) documentation. # February Updates Source: https://docs.methodfi.com/changelog/2025/february ## New Features ### Dashboard Payment Details Page payment details We've upgraded the Payments experience with a brand-new dedicated Payment Details Page Now, you get more insights and control than ever before: * **Payment Timeline** –> Track the full journey of your payments, end to end. * **Enhanced Payment Info** –> Quickly see whether a payment was made via electronic or paper. * **Check Images** –> For paper payments, view the check image (if available) directly within the details page. ## Improvements ### Payments API We've added two new fields to the Payments API to provide better visibility into payment details: * `destination_payment_method`: Indicates how the payment was delivered to the recipient - either `electronic` or `paper` * `destination_status`: New status `cashed` available to track when paper checks have been processed For more information, see our [Payments API documentation](https://docs.methodfi.com/reference/payments/overview). ## SDK Updates * Released [version 1.1.9](https://github.com/MethodFi/method-python/releases/tag/v1.1.9) of `method-python` * Released [version 1.1.10](https://github.com/MethodFi/method-node/releases/tag/v1.1.10) of `method-node` # January Updates Source: https://docs.methodfi.com/changelog/2025/january ## New Features ### Account Attributes API account attributes We've released a brand new [Account Attributes API](https://docs.methodfi.com/reference/accounts/attributes/overview) that's powered by Method's real-time data integrations for up-to-date insights. It provides: * Real-time indicators for individual account usage patterns * Account utilization metrics * Account standing information * Delinquency data (period, outcome, and amount) For access to the Account Attributes API, please contact your Method CSM. ## Improvements ### Entity Attributes API We've enhanced the [Entity Attributes API](https://docs.methodfi.com/reference/entities/attributes/overview) with two new attributes: * `credit_health_open_accounts`: Total number of open accounts * `credit_health_entity_delinquent`: Entity delinquency status, rating and a list of delinquent accounts **Pro tip**: Leverage both the Account Attributes API and the Entity Attributes API to get a holistic view of an entity's credit health. ### Method Dashboard We've made significant performance and usability improvements to the [Method Dashboard](https://app.methodfi.com): * Pages load 3x faster. We also made navigating between pages feel a lot better. * Charts load 2x faster. We also fixed hovering over the bars so it works well. * Universal Search is now keyboard navigable. You can use your up/down arrows and hit enter. * Added the ability to right click on a table row and open it in a new tab. * Created better financial account logos. We will continue to fix bad ones. * Changed the layout of information on details pages to make reading easier. Please reach out in Slack with any feedback. We will put your requests at the top of our to-do list. ### Payment Dry-run We've added a new `dry_run` boolean flag to the `POST /payments` endpoint. When enabled, it will simulate a payment without triggering the actual payment flow. You'll receive accurate information about the payment timeline, helping you preview the payment flow and communicate accurate timing to your users before initiating an actual payment. For more information, see our [Payments API](https://docs.methodfi.com/reference/payments/overview). ## SDK Updates * Released [version 1.1.8](https://github.com/MethodFi/method-python/releases/tag/v1.1.8) of `method-python` * Released [version 1.1.9](https://github.com/MethodFi/method-node/releases/tag/v1.1.9) of `method-node` # July Updates Source: https://docs.methodfi.com/changelog/2025/july ## New Features ### Message-Level Encryption (MLE) MLE We’ve added support for end-to-end encryption of sensitive data transmitted between your application and Method’s API, available to everyone. Here’s what’s new: * **Hybrid Encryption:** Uses AES-GCM (for payload encryption) and RSA-OAEP-256 (for key encryption) to ensure confidentiality even if network traffic is intercepted. * **Public Key Registration:** Register your RSA public key with Method via a `.well-known` endpoint or direct upload. * **Encrypted Requests & Responses:** Send encrypted payloads using the `Method-MLE: jwe` header; Method encrypts responses using your public key. * **Key Management:** Support for key rotation, deprecation, deletion, and webhook notifications for Method key changes. You can find a [quickstart guide here](/reference/message-level-encryption#quickstart). For more information, please refer to the [Message Level Encryption documentation](/reference/message-level-encryption). ### Card Brand API Card Brands We’ve expanded the Card Brand object to provide a more structured format with richer brand details — making it easier to identify, display, and integrate specific card products with consistent issuer, network, and branding data. Available when passing `Method-Version: 2025-07-04` in the request header. ```json theme={null} { "id": "cbrd_eVMDNUPfrFk3e", "account_id": "acc_yVf3mkzbhz9tj", "network": "visa", "issuer": "Chase", "last4": "8623", "brands": [ { "id": "brand_AMxtjQzAfDCRP", "name": "Chase Sapphire Reserve", "url": "https://static.methodfi.com/card_brands/1b7ccaba6535cb837f802d968add4700.png" } ], "status": "completed", "shared": false, "source": "network", "error": null, "created_at": "2024-03-19T01:05:37.247Z", "updated_at": "2024-03-19T01:05:37.247Z" } ``` ```json theme={null} { "id": "cbrd_Accm7P6t6mYQP", "account_id": "acc_LxwEqNicr66yP", "brands": [ { "id": "pdt_15_brd_1", "card_product_id": "pdt_15", "description": "Chase Sapphire Reserve", "name": "Chase Sapphire Reserve", "issuer": "Chase", "network": "visa", "network_tier": "infinite", "type": "specific", "url": "https://static.methodfi.com/card_brands/1b7ccaba6535cb837f802d968add4700.png" } ], "status": "completed", "source": "method", "error": null, "created_at": "2025-08-12T00:56:50.139Z", "updated_at": "2025-08-12T00:56:50.139Z" } ``` **Key Changes**: * `network` and `issuer` are now nested inside each brand object. * Added `card_product_id`, `description`, and `type` fields. * Removed `last4` and `shared` fields. For more information, please refer to the [Card Brand API](/reference/accounts/card-brands/overview). ### Card Products API We've added a new `Card Products` directory accesible via our API allowing you to retrieve all `Card Brand` objects associated with a given `Card Product`. Available when passing `Method-Version: 2025-07-04` in the request header. ```bash cURL theme={null} curl https://production.methodfi.com/card_products/pdt_17 \ -H "Method-Version: 2025-07-04" \ -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" ``` ```json theme={null} { "id": "pdt_17", "name": "Chase Freedom", "issuer": "Chase", "type": "specific", "brands": [ { "id": "pdt_17_brd_1", "description": "Chase Freedom", "network": "visa", "network_tier": "signature", "default_image": "https://static.methodfi.com/card_brands/fb5fbd6a5d45b942752b9dc641b93d1f.png" }, { "id": "pdt_17_brd_2", "description": "Chase Freedom", "network": "visa", "network_tier": "standard", "default_image": "https://static.methodfi.com/card_brands/6cb697528b0771f982f7c0e8b8869de3.png" } ] } ``` For more information, please refer to the [Card Products API](/reference/card-products/overview). ## Improvements ### Connect API We now support asynchronous Connect requests. You'll receive a `connect.available` webhook when an Async Connect is completed. Async Connect requests can be created by either: * Setting the `Prefer: respond-async` header * Specifying `products` and / or `subscriptions` in the request body The Connect object will now include `requested_products` and `requested_subscriptions` fields in the response body. ```bash cURL theme={null} curl https://production.methodfi.com/entities/ent_qKNBB68bfHGNA/connect \ -X POST \ -H "Prefer: respond-async" \ -H "Content-Type: application/json" \ -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" \ -d '{ "requested_products": ["card_brand"], "requested_subscriptions": ["card_brand"] }' ``` ```json theme={null} { "id": "cxn_4ewMmBbjYDMR4", "entity_id": "ent_qKNBB68bfHGNA", "status": "completed", "accounts": [ "acc_eKKmrXDpJBKgw", "acc_GV8WbmJW7KGRy", "acc_MLPKh9gQDDbT8", "acc_LbXE8wVYJLrKt", "acc_J3P9fayDFjpAy", "acc_eFFRV9zmpLREK" ], "requested_products": ["card_brand"], "requested_subscriptions": ["card_brand"], "error": null, "created_at": "2024-04-12T14:56:46.645Z", "updated_at": "2024-04-12T14:56:46.645Z" } ``` For more information, please refer to the [Connect API](/reference/entities/connect/overview). ### Webhook API We've added a new `refs` object to webhook payloads. This object contains the `entity` ID of the Entity that the webhook is related to. ```json theme={null} { "webhook_id": "whk_cSGjA6d9N8y8R", "id": "pmt_zR3nJG3c99P3X", "type": "payment.update", "op": "update", "path": "/payments/pmt_zR3nJG3c99P3X", "event": "evt_knqJgxKUnqDVJ", "refs": { "entity": "ent_qKNBB68bfHGNA" } } ``` We have also added the following new webhooks: * `card_brand.available` * `connect.available` * `method_jwk.create` * `method_jwk.update` For more information, please refer to the [Webhooks API](/reference/webhooks/overview). ### Entity and Account Products The `product_id` field in the `Product` object and the Retrieve endpoint are now deprecated. We've added the `latest_successful_request_id` field to the `Product` object. This field will contain the ID of the most recently successful Product resource. For more information, please refer to the [Entity Products API](/reference/entities/products/overview) and [Account Products API](/reference/accounts/products/overview). # June Updates Source: https://docs.methodfi.com/changelog/2025/june ## New Features ### Webhook HMAC Signature Verification We’ve added support for HMAC-SHA256 signatures to further secure your webhook integrations. Here's what's new: * **Signed Webhooks:** When you provide an `hmac_secret` during webhook registration, Method now includes a `method-webhook-signature` header on each webhook request. This signature is an HMAC-SHA256 digest, computed using your `hmac_secret` as the shared secret and the message format `${method-webhook-timestamp}:${raw_payload}`. * **Timestamp Header:** Every webhook request now includes a `method-webhook-timestamp` header (UNIX timestamp in seconds), allowing you to validate the freshness of requests and prevent replay attacks. * **Verification:** You can verify the webhook by recreating the HMAC digest locally and comparing it using a timing-safe equality check. For more information, please refer to the [Webhook API](/reference/webhooks/overview). ## Improvements ### Connect API * **Automatic Execution of Account Products and Subscriptions:** You can now optionally include `products` and `subscriptions` arrays in the request body when creating a `Connect` for an entity. These will automatically execute upon a successful connection. * **Expand Query Parameter:** A new `expand` query parameter has been added to the `Connect` object, allowing you to include additional properties within the `accounts` object. ```js theme={null} const connect = await method .entities('ent_TYHMaRJUUeJ7U') .connect .create( { products: ['attribute', 'card_brand'], subscriptions: ['card_brand', 'transaction'], }, { expand: ['accounts.update'] } ); ``` For more information, please refer to the [Connect API](https://docs.methodfi.com/reference/entities/connect/overview) and [Expanding Resources](/reference/expanding). ## SDK Updates * Released [version 1.2.4](https://github.com/MethodFi/method-node/releases/tag/v1.2.4) of `method-node` * Released [version 1.2.4](https://github.com/MethodFi/method-python/releases/tag/v1.2.4) of `method-python` # March Updates Source: https://docs.methodfi.com/changelog/2025/march ## New Features ### Transactions API transactions We’re excited to launch our new [Transactions API](https://docs.methodfi.com/reference/accounts/transactions/overview) which gives real-time notifications directly from the card networks on credit/debit card purchases. Key benefits include: * **Real-Time Alerts** -> Instantly notify users about new charges. * **Intelligent Categorization** -> Automatically categorize spending using merchant category codes (MCCs). * **Enhanced Security** -> Flag unusual transactions and identify spending in unfamiliar locations. * **Multi-Currency Support** -> Monitor transactions in both USD and foreign currencies. * **Refund Visibility** -> Gain complete insight into refund statuses. For access to the Transactions API, please contact your Method CSM. ### Payment Instruments API Our new [Payment Instruments API](https://docs.methodfi.com/reference/accounts/payment-instruments/overview) enables you to create and retrieve card credentials for checkout processes. This API provides seamless access to card details and network tokens, streamlining payment experiences across your app or platform. For access to the Payment Instruments API, please contact your Method CSM. ### Simulate Credit Scores API In `development` environments, you can now leverage the [Simulate Credit Scores API](https://docs.methodfi.com/reference/simulations/credit-scores/create) to simulate custom credit scores. This feature lets you: * Simulate scores for test entities. * Customize score values, sources, and models. * Include contributing factor data for more realistic testing scenarios. ## Improvements ### Entity Attributes API We've made significant improvements to the [Entity Attributes API](https://docs.methodfi.com/reference/entities/attributes/overview). * **Credit Health Hard Inquiries**: The `credit_health_hard_inquiries` attribute now includes two additional fields in its metadata history: * `institution_name`: Identifies the institution that performed the inquiry. * `inquiry_date`: Provides the date the inquiry occurred. * **New Soft Inquiries Attribute**: A new `credit_health_soft_inquiries` attribute has been added. It mirrors the structure of hard inquiries to consistently track soft credit checks along with the associated institution name and inquiry date. ### Updates API The [Updates API](https://docs.methodfi.com/reference/accounts/updates/overview) response now includes a new field: * `data_as_of`: A timestamp indicating when the data in the record was last confirmed to be accurate, providing clear insight into the freshness and reliability of the information returned. ### Card Brands API The [Card Brands API](https://docs.methodfi.com/reference/accounts/card-brands/overview) is now subscribable. This enhancement allows your system to automatically receive updated card brand information in real time. For example, if a user loses their card and receives a new one, the API will promptly reflect these changes, ensuring that your records are always accurate and up to date. ### Accounts API We've expanded the [Accounts API](https://docs.methodfi.com/reference/accounts/overview) to support additional account types: * `BNPL` (Buy Now, Pay Later) * `Fintech` ### Account Verification Sessions API The [Account Verification Sessions API](https://docs.methodfi.com/reference/accounts/verification-sessions/overview) now supports the `network` verification type. For more information, please see the [Network Verification Sessions API reference](https://docs.methodfi.com/reference/accounts/verification-sessions/update-network). ## SDK Updates * Released [version 1.1.13](https://github.com/MethodFi/method-node/releases/tag/v1.1.13) of `method-node` * Released [version 1.1.12](https://github.com/MethodFi/method-python/releases/tag/v1.1.12) of `method-python` # May Updates Source: https://docs.methodfi.com/changelog/2025/may ## Improvements ### Transactions API A new `merchant` property has been added to the `Transaction` object. This field provides the merchant name and logo associated with each transaction. This property is not available by default. You can enable it by contacting your Method CSM. For more information, please refer to the [Transactions API](https://docs.methodfi.com/reference/accounts/transactions/overview). ### Card Brand API The `CardBrand` object now includes a `source` property. Possible values are: * `method` – sourced from Method’s internal systems * `network` – retrieved directly from the card network * `null` – source is unavailable For more information, please refer to the [Card Brand API](https://docs.methodfi.com/reference/accounts/card-brands/overview). ## SDK Updates * Released [version 1.2.2](https://github.com/MethodFi/method-node/releases/tag/v1.2.2) of `method-node` * Released [version 1.2.2](https://github.com/MethodFi/method-python/releases/tag/v1.2.2) of `method-python` # November Updates Source: https://docs.methodfi.com/changelog/2025/november ## Improvements ### Simulate API The [Simulate API](/reference/simulations/overview) now supports simulating Card Brand subscription behaviors. **[Simulate Card Brand API](/reference/simulations/card-brands/create)** * Card Brand simulations let developers designate a card brand for an account with an active Card Brand Subscription by specifying a `brand_id`. This triggers a `card_brand.available` webhook containing the ID of the designated card brand, allowing developers to test card brand-driven workflows in the development environment. This API is available in the development environment only. For more information, visit the [Simulations API](/reference/simulations/overview) and [Card Brand API](/reference/accounts/card-brands/overview) documentation. # October Updates Source: https://docs.methodfi.com/changelog/2025/october ## Improvements ### Accounts API The [Accounts API](/reference/accounts/overview) now includes a new `sub_type` field under the `liability` object. This field provides additional context about a liability account by specifying its sub-type (for example, distinguishing between a `secured` and `unsecured` `personal_loan`). For more information, please see Account Liability Sub-Types. ## SDK Updates * Released [version 2.0.0](https://github.com/MethodFi/method-node/releases/tag/v2.0.0) of `method-node` * Released [version 2.0.0](https://github.com/MethodFi/method-python/releases/tag/v2.0.0) of `method-python` These major releases include default support for the **`2025-07-04` API version**, which introduces the new [Card Products API](/changelog/api-versions/2025-07-04) and updated [Card Brand schema](/changelog/api-versions/2025-07-04#card-brand-api). See the [2025-07-04 API Version](/changelog/api-versions/2025-07-04) for more details. # September Updates Source: https://docs.methodfi.com/changelog/2025/september ## New Features ### Dashboard Updates **Card Brands Directory** card brands directory We released a new tab in the Method Dashboard – Card Brands – displaying Method's proprietary catalog of credit card brands and metadata. This dataset underpins the Card Brands API, which enables exact 1:1 product matching for each credit card in a user’s wallet, meaning you can identify the specific card brand a user is holding. For example, instead of just knowing a user holds a Chase Visa, you can determine if they hold a Chase Sapphire Reserve, Freedom Unlimited, or any co-branded product. For access to the Card Brands Directory, please contact your Method CSM. **New Role: Restricted Member** You can now invite teammates as a Restricted Member. This role is the same as the Member role, except Restricted Members have no access to view end-users PII. ## Improvements ### Simulate API The [Simulate API](/reference/simulations/overview) now supports simulating Connect and Attributes behaviors for an entity — making it easier for developers to test how Method responds to various data changes without needing to trigger them in production. **[Simulate Connect API](https://docs.methodfi.com/reference/simulations/connect/create)** * You can now configure Connect behaviors such as new\_credit\_card\_account. This is useful when testing account-creation flows or verifying how your system handles new data returned from a subsequent Connect. For example, after configuring this behavior, the next time you execute Connect for that entity, a new credit card account will appear in the response — helping you simulate real-world user events like a customer opening a new card. **[Simulate Attributes API](https://docs.methodfi.com/reference/simulations/attributes/create)** * Similarly, you can configure Attribute behaviors such as new\_soft\_inquiry to test how your system reacts to changing credit attributes. On the next Attributes request for that entity, the configured behavior will be applied (e.g., a new soft inquiry will be present). This API is available in the development environment only. These new simulation capabilities give you greater control when testing entity lifecycle scenarios and verifying downstream logic — without needing real production data or user actions. For more information, visit the [Simulations API](/reference/simulations/overview) documentation. # January Updates Source: https://docs.methodfi.com/changelog/2026/january ## New Features ### Forwarding Requests API The [Forwarding Requests API](/reference/forwarding-requests/overview) allows you to securely proxy sensitive data (such as card details) to third-party services without your system ever handling the raw data. This enables use cases like payment processing, tokenization, and partner integrations while maintaining the PCI compliance of existing solutions. **Key capabilities:** * **Secure data transmission**: Send templated HTTP requests to whitelisted third-party endpoints. * **Dynamic data injection**: Use template placeholders (e.g., `{{my_binding.card.number}}`) instead of raw values. * **Binding resolution**: Bind placeholders to Method resources (currently [Payment Instruments](/reference/accounts/payment-instruments/overview)), allowing Method to securely append the underlying data without ever touching your company database. * **Destination whitelisting**: Requests can only be sent to pre-approved URLs to prevent data exfiltration. * **Transparent responses**: The third-party response is forwarded directly back to your application without requiring you to make changes to the way you ingest third-party response data. For more information, visit the [Forwarding Requests API](/reference/forwarding-requests/overview) documentation. ### Secrets API The [Secrets API](/reference/secrets/overview) allows you to securely store sensitive configuration values (such as API keys or credentials) for use within Method. Secrets are encrypted at rest and never exposed back to client applications. **Key capabilities:** * **Encrypted storage**: Store sensitive values and receive a Secret ID (`sec_...`) in return. * **No client exposure**: Secret values are never returned in API responses. * **Forwarding integration**: Secrets can be inserted into [Forwarding Requests](/reference/forwarding-requests/overview) for authenticating with third-party services. For more information, visit the [Secrets API](/reference/secrets/overview) documentation. ### Opal Appearance Customization You can now customize the visual appearance of [Opal](/opal/overview), Method's embeddable UI, to better match your application's branding or autofit to your users' devices. When opening Opal with the client SDK, specify an `appearance` option with one of the following values: * `light`: Standard light theme (default) * `dark`: Dark theme for low-light environments * `system`: Automatically matches the user's device settings If no appearance is specified, Opal defaults to the `light` theme. For more information, visit the [Opal Libraries](/opal/libraries) documentation. ## Improvements ### Payment Instruments API This release introduces several improvements to the [Payment Instruments](/reference/accounts/payment-instruments/overview) product, focused on lifecycle management and subscription control. **Lifecycle Management for Inbound ACH/Wire** A new endpoint allows you to close inbound ACH/Wire payment instruments when they are no longer needed. This is useful for decommissioning payment routes after a refinance completes or when a funding relationship ends. * **New endpoint**: `DELETE /accounts/:accountId/payment_instruments/:pmtInsId` * **Behavior**: Supported only for `inbound_achwire_payment` instruments. Updates instrument status to `closed` and sets `chargeable` to `false`. For more information, see the [Payment Instruments API](/reference/accounts/payment-instruments/overview) documentation. **Granular Subscription Types** The `payment_instrument` [subscription](/reference/accounts/subscriptions/overview) has been split into two more specific subscription types, giving you more flexibility in determining which webhook events you receive: * `payment_instrument.card`: Triggered for card-level updates (e.g., PAN changed, expiration updated) * `payment_instrument.network_token`: Triggered for network token updates (e.g., token provisioned, status changed) For API version `2025-12-01`+, clients must use the new specific subscription names. ### Accounts API **Collection Account Support** The [Account Sensitive](/reference/accounts/sensitive/overview) product now supports the `collection` account type. This enables you to retrieve sensitive account details (such as account numbers) for accounts that have been sent to collections, expanding coverage for debt management and recovery workflows. ### Attributes API **Support for Closed Accounts** You can now retrieve [Account Attributes](/reference/accounts/attributes/overview) for closed liability accounts. Previously, querying Attributes for a closed account would return an error. With this update, derived financial insights (such as payment history summaries and balance trends) remain accessible even after an account has been closed—useful for historical reporting and analytics. # Introducing API v2 Source: https://docs.methodfi.com/changelog/api-versions/2024-04-04 title We are excited to announce the launch of API v2 (release `2024-04-04`), the highly anticipated second version of Method's API. Over the past year, our team has been dedicated to gathering feedback and working closely with our clients to create an even more powerful and developer-friendly API. This release is packed with new features and enhancements that build upon Method's credential-less consumer permissioned financial network. Expanded integrations with Visa/Mastercard power new features such as real-time credit card transaction notifications, and enabling 1-click checkout experiences for merchants. This is in addition to our real-time financial institution liability updates, which have been significantly upgraded to provide better accuracy, expanded coverage, and reduced latency. ### Upgrading to 2024-04-04 The new API version is available to all existing teams. New teams are automatically pinned to the API version `2024-04-04`. During the transition phase, teams will be allowed to utilize any API version in tandem. Note that once upgraded manually, it’s not possible to revert to older versions. Contact your Method CSM for more information on upgrade rollbacks. * **Request Header**: Set `Method-Version` to `2024-04-04`. See [API Versioning](/reference/versioning#api-versioning) for more information. * **Client Libraries**: For Method Libraries, the version is locked to the dated version of the API. For example, method-node v0.x.x is locked to 2020-12-06, while method-node v1.x.x is locked to 2024-04-04 and onwards. #### Upgrade Support Our technical integration team is here to help! Contact your Method CSM for a 1:1 on best practices and support migrating to `2024-04-04` Personalized upgrade guides have been created for enterprise customers. Contact your Method CSM to receive your guide. **✨ Ask Method:** The search bar of our docs now includes a conversational LLM search powered by ChatGPT. Feel free to ask any questions and receive a personalized answer. *Sample questions:* > How are auth\_sessions different in the new version of the API? > What are the new products in 2024-04-04? ## Entities New endpoints have been introduced for verification sessions, identities, connect operations, credit scores, products, and subscriptions. Several endpoints, including auth session, credit scores, and sensitive information retrieval, have been deprecated. The connect endpoint now fetches all liability accounts across Method’s network of financial institutions, replacing auth\_session. The verification sessions endpoint manages methods for verifying an entity's phone and identity, while the identities endpoint retrieves the underlying identity (PII) of an entity. The products and subscriptions endpoints provide an overview of the products and continuous updates available for entities. ### New Features #### The Connect endpoint [Connect](/reference/entities/connect/overview) identifies and connects all the liability accounts (e.g., credit card, mortgage, auto loans, student loans, etc.) for an entity across Method’s network of 1500+ financial institutions/lenders. * **The Connect endpoint replaces:** * Auth Session: `POST /entities/{ent_id}/auth_session` See [Connect](/reference/entities/connect/overview) for more information. *** #### The Credit Scores endpoint [Credit Scores](/reference/entities/credit-scores/overview) returns the latest credit score and score factors for an entity. * **The Credit Scores endpoint replaces:** * Credit Score: `GET /entities/{ent_id}/credit_score` See [Credit Scores](/reference/entities/credit-scores/overview) for more information. *** #### The Verification Sessions Endpoint [Entity Verification Sessions](/reference/entities/verification-sessions/overview) manage the methods for verifying an entity's phone and identity. Entities need to verify their identity and/or phone to be used throughout the Method API. The status of an entity's verification is returned via the `verification` field in the Entity object. * **The Verification Sessions endpoint replaces:** * KBA questions via Auth Session: `POST /entities/{ent_id}/auth_session` is replaced by [kba](/reference/entities/verification-sessions/create-kba) entity verification session. * Non-KBA authentication via Auth Session: `POST /entities/{ent_id}/auth_session` is replaced by [byo\_kyc](/reference/entities/verification-sessions/create-byo-kyc) entity verification session. * `individual.phone_verification_type` and `individual.phone_verification_timestamp` via the create Entity request are replaced by [byo\_sms](/reference/entities/verification-sessions/create-byo-sms) phone verification requirements. * Utilizing `capabilities`, `available_capabilities`, and `pending_capabilities` in the Entity object to verify if an entity's identity has been matched or if more PII is required. * This flow is now replaced by `verification.identity.verified` and `verification.identity.matched` in the `verification` field in the Entity object. * **Upgrade notes:** * The `verification` field in the Entity object returns the status of Identity Verification (`verification.identity`) and Phone Verification (`verification.phone`). * The `method` key in the `entity.verification` object enumerates the phone and identity verifications available for your entity. * Available verification methods differ on a team-by-team basis and are further defined by the PII provided during entity creation. See [PII Requirements](/reference/entities/overview#pii-requirements) for more information. * Teams with pre-defined PII requirements can utilize `byo_kyc` to skip KBA, and `byo_sms` to skip phone verification. * Teams upgrading from a prior API version might have some verifications auto-generated. Contact your Method CSM for more info. * The `status` key in an entity will only transition to `active` when all verification requirements have been completed. See [Verification Sessions](/reference/entities/verification-sessions/overview) for more information. *** #### The Identities endpoint Entity [Identities](/reference/entities/identities/overview) endpoint is used to retrieve the underlying identity (PII) of an Entity. * **The Identities endpoint replaces:** * Entity Sensitive: `GET /entities/{ent_id}/sensitive` See [Identities](/reference/entities/identities/overview) for more information. *** #### The Products endpoint Entity [Products](/reference/entities/products/overview) endpoint outlines the products (*capabilities*) an entity has access to and provides an overview of the status of all the products. Products are Method endpoints available for an entity. Access to most products requires an entity to be active. However, some products have restricted access requiring team-by-team enablement. See [List all Products](/reference/entities/products/list) for more information. **Entity Products:** | Name | Use-Case | Resource Doc | | -------------- | -------------------------------------------------------------------- | ----------------------------------------------------------- | | `connect` | On-Demand comprehensive view of an Entity’s outstanding liabilities. | [Connect](/reference/entities/connect/overview) | | `credit_score` | On-Demand view of an Entity’s credit score. | [Credit Scores](/reference/entities/credit-scores/overview) | | `identity` | On-Demand retrieval of the full Identity (PII) for any Entity | [Identities](/reference/entities/identities/overview) | * **The Products endpoint replaces:** * Utilizing `capabilities`, `available_capabilities`, and `pending_capabilities` in the Entity object to determine the capabilities an entity has access to. These fields have been deprecated from the Entity object and removed in favor of: * `products` (products available for this entity) * `restricted_products` (products not currently available, but can be made available) See [Products](/reference/entities/products/overview) for more information. *** #### The Subscriptions endpoint Entity [Subscriptions](/reference/entities/subscriptions/overview) endpoint controls the state of all subscriptions for an entity. Subscriptions are products that can provide continuous updates via webhooks (e.g., *Credit Score Subscription provides updates on an entity’s credit score*). **Entity Subscriptions:** | Name | Use-Case | Resource Doc | | -------------- | ------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | | `connect` | Comprehensive view of an Entity’s outstanding liabilities and continuous near real-time updates on new liabilities. | [Connect](/reference/entities/connect/overview) | | `credit_score` | Continuous near real-time updates on an Entity’s credit score. | [Credit Scores](/reference/entities/credit-scores/overview) | * **The Subscriptions endpoint replaces:** * Custom configuration for continuous credit report pulls via your Method CSM. This has been deprecated and replaced by [Create a Subscription](/reference/entities/subscriptions/create) endpoint. See [Subscriptions](/reference/entities/subscriptions/overview) for more information. *** ### Breaking Changes #### Entity object changes * ✨ Corporation entity types have been simplified to `corporation` during [Create a Corporation](/reference/entities/create-corporation) entity. * `c_corporation`, `s_corporation`, `llc`, `partnership`, and `sole_proprietorship` have been deprecated and removed in favor of `corporation` * ✨ Providing SSN is now supported during [Create an Individual](/reference/entities/create-individual) entity. * `individual.ssn`, and `individual.ssn_4` * ✨ Entity verification status is now returned by the Entity object. See [Entity object](/reference/entities/overview) for more information. * `verification` * ✨ Products and subscription status are now returned by the Entity object. See [Entity object](/reference/entities/overview) for more information. * `products` * `restricted_products` * `subscriptions` * `available_subscriptions` * `restricted_subscriptions` * ⛔ Phone verification has been replaced and no longer returned by the Entity object. * `individual.phone_verification_type`, and `individual.phone_verification_timestamp` have been deprecated and removed in favor of [Entity Verification Sessions](/reference/entities/verification-sessions/overview) * ⛔ Entity capabilities have been deprecated and removed from the Entity object. * `capabilities`, `available_capabilities`, and `pending_capabilities` have been deprecated and removed in favor of [Products](/reference/entities/products/overview), [Subscriptions](/reference/entities/subscriptions/overview), and [Entity Verification Sessions](/reference/entities/verification-sessions/overview) * The `verification` field in the Entity object returns the status of Identity Verification (`verification.identity`) and Phone Verification (`verification.phone`). * The `products` array returns the products the entity has access to, replacing `capabilities`. * The `restricted_products` array returns the products the entity does not have access to, replacing `pending_capabilities`. * The [Entity Products](#) endpoint outlines the products (*capabilities*) an entity has access to and provides an overview of the status of all the products. * The following fields have been modified in the [Entity object](/reference/entities/overview): * `individual.phone_verification_type` * `individual.phone_verification_timestamp` * `capabilities` * `available_capabilities` * `pending_capabilities` * `individual.ssn` * `individual.ssn_4` * `verification` * `products` * `restricted_products` * `subscriptions` * `available_subscriptions` * `restricted_subscriptions` #### Deprecated endpoints The following endpoints have been deprecated and removed in `2024-04-04` * Auth Session: `/entities/{ent_id}/auth_session` removed in favor of [Connect](/reference/entities/connect/overview) * Credit Score: `/entities/{ent_id}/credit_score` removed in favor of [Credit Scores](/reference/entities/credit-scores/overview) * Entity Sensitive: `/entities/{ent_id}/sensitive` removed in favor of [Identities](/reference/entities/identities/overview) * Refresh Capabilities: `/entities/{ent_id}/refresh_capabilities` is no longer supported in `2024-04-04` * Manual Auth Session: `/entities/{ent_id}/manual_auth_session` is no longer supported in `2024-04-04` * Entity Vehicles: `/entities/{ent_id}/vehicles` is no longer supported in `2024-04-04` ## Accounts New endpoints have been introduced for updates, card brands, payoffs, transactions, balances, verification sessions, and sensitive information. Several endpoints, including account syncs, account verification, and sensitive information retrieval, have been deprecated. The updates endpoint now provides real-time account data directly from financial institutions, replacing syncs, and making liability account data available through the updates endpoint. The verification process for ACH and liability accounts has been streamlined with Account Verification Sessions. ### New Features #### The Updates endpoint [Updates](/reference/accounts/updates/overview) endpoint retrieves in real-time account data including balance, due dates, APRs, directly from the account’s financial institution. Updates is Method's flagship endpoint and replaces the `sync` endpoint by enabling push notifications directly from the financial institution. As part of the `2024-04-04` release the Account object has been modified, and most Account data is now returned by an Update object. See [Account object changes](/changelog/api-versions/2024-04-04#account-object-changes) for more information. * **The Updates endpoint replaces:** * Syncing an account using `/accounts/{acc_id}/syncs` has been deprecated and removed in favor of [Create an Update](/reference/accounts/updates/create) * Enrolling in auto syncs using `/accounts/{acc_id}/sync_enrollment` or via your Method CSM has been deprecated and removed in favor of [Updates](/reference/accounts/updates/overview) and [Subscriptions](/reference/accounts/subscriptions/overview) * Sync status fields in the Account response have been deprecated and removed in favor of [Updates](/reference/accounts/updates/overview). Removed fields include: * `data_status` * `data_sync_type` * `data_last_successful_sync` * `data_status_error` * `data_source` * `data_updated_at` * Enrollment into credit report-based updates via your Method CSM has been deprecated and removed in favor of the `update.snapshot` subscription type. See [Subscriptions](/reference/accounts/subscriptions/overview) for more information. * Liability data at the account level (`account.liability.`) has been deprecated and removed in favor of an Update object and an expansion. See [Account](/reference/accounts/overview) for more information. * Utilizing `data_status` to determine real-time financial institution coverage has been deprecated and removed in favor of the `products` array including `updates`. See [Updates](/reference/accounts/updates/overview) for more information. * **Upgrade notes:** * New updates sources: `direct` and monthly `snapshot` updates. * `direct`: Near real-time account update (balance, due dates, etc.) from the account’s financial institution (replaces a `sync`). * `snapshot`: Monthly snapshot update (balance, due dates, etc.) from the account’s financial institution (replaces credit report-based updates). * Receiving continuous updates requires a subscription to `update` or `update.snapshot`. See [Subscriptions](/reference/accounts/subscriptions/overview) for more information. * Liability data at the account level (`account.liability.`) has been deprecated and removed in favor of an Update object and an expansion. See [Account](/reference/accounts/overview) for more information. * Any account connected using Entity Connect will receive an initial `snapshot` update and a `direct` update (when available). * Legacy accounts connected via `auth_session` have been migrated with an Update object pre-populated. See [Updates](/reference/accounts/updates/overview) for more information. *** #### The Card Brand endpoint [Card Brand](/reference/accounts/card-brands/overview) endpoint retrieves the associated credit card metadata (Product / Brand Name, Art, etc.) directly from the card issuer. In the future, card brand webhooks will notify in real-time any card changes (e.g., card downgraded, card lost, etc.) * **The Card Brand endpoint replaces:** * Derived card names in the liability account field `name`. Migrating to card brand will provide accurate names across any Visa / Mastercard card regardless of issuing bank. See [Card Brand](/reference/accounts/card-brands/overview) for more information. *** #### The Payoffs endpoint [Payoffs](/reference/accounts/payoffs/overview) endpoint retrieves a payoff quote in real-time from the Account’s financial institution / lender. Payoffs are currently only available for Auto Loan and Mortgage accounts. * **The Payoffs endpoint replaces:** * `payoff_amount` and `payoff_amount_term` fields within the `auto_loan` Account type response. See [Updates](/reference/accounts/updates/overview) for more information on the Account object changes. See [Payoffs](/reference/accounts/payoffs/overview) for more information. *** #### The Transactions endpoint [Transactions](/reference/accounts/transactions/overview) endpoint retrieves real-time transaction (authorization, clearing, etc) notifications for Credit Card Accounts directly from the card networks (Visa, MC). Enrollment for transactions requires a subscription and additional consent using Method's `connect` element. * **The Transactions endpoint replaces:** * Enrollment for transactions using the `auth` element has been deprecated and removed in favor of the `connect` element. See [Connect Overview](/elements/connect/overview) for more information. * Global transactions endpoint `/transactions` has been deprecated and removed in favor of account-scoped transactions. See [Transactions](/reference/accounts/transactions/overview) for more information. * `transaction:stream` capability has been deprecated and removed in favor of the `transactions` product. See [Products](/reference/accounts/products/overview) for more information. See [Transactions](/reference/accounts/transactions/overview) for more information. *** #### The Balances endpoint [Balances](/reference/accounts/balances/overview) endpoint retrieves the real-time balance from the account’s financial institution. Balance is now available for non-liability accounts such as checking accounts. Contact your Method CSM for early access to expanded Balance coverage. * **The Balances endpoint replaces:** * The `balance` field in `liability..balance` has been deprecated and removed in favor of: * Retrieving `balance` using the [Balances](/reference/accounts/balances/overview) endpoint * Retrieving `balance` and additional liability information using the [Updates](/reference/accounts/updates/overview) endpoint See [Balances](/reference/accounts/balances/overview) for more information. *** #### The Verification Sessions endpoint [Account Verification Sessions](/reference/accounts/verification-sessions/overview) manage the methods for verifying an Account to enable specific products for ACH or Liability accounts. For example, ACH Accounts require a verified Account Verification Session before they can be used as a source for Payments. * **The Account Verification Sessions endpoint replaces:** * ACH Account verification via `/accounts/{acc_id}/verification` has been deprecated and removed in favor of: * An Account Verification Session of one of the available methods: `micro_deposits`, `plaid`, `mx`, or `teller`. * Teams with corporate disbursement ACH accounts can skip verification and a verification will be auto-provisioned with the type of `auto_verify`. * Teams with managed DDAs can whitelist a routing number to skip verification across all their DDAs (routing / account number pair). * See [Verification Types](/reference/accounts/verification-sessions/overview#verification-types) for more information. A verification of `trusted_provisioner` will be auto-provisioned. Contact your Method CSM for more information. * Liability account number verification for AMEX, Apple Card, etc. is now handled by a `standard` Account Verification Session. See [Update a Standard Verification](/reference/accounts/verification-sessions/update-standard) for more information. * Instant Link CVV verification is now handled by a `pre_auth` Account Verification Session. See [Update a Pre-auth Verification](/reference/accounts/verification-sessions/update-preauth) for more information. * **Upgrade notes:** * Teams upgrading from a prior API version might have some verifications auto-generated. Contact your Method CSM for more info. See [Account Verification Sessions](/reference/accounts/verification-sessions/overview) for more information. *** #### The Sensitive endpoint [Sensitive](/reference/accounts/sensitive/overview) endpoint returns underlying sensitive account information (e.g., PAN, CVV, account number). This product is only available for liabilities and requires verification on a team-by-team basis. * **The Sensitive endpoint replaces:** * `GET /accounts/{acc_id}/sensitive` is deprecated and removed in favor of [Create a Sensitive](/reference/accounts/sensitive/create). See [Sensitive](/reference/accounts/sensitive/overview) for more information. *** #### The Products endpoint Account [Products](/reference/accounts/products/overview) endpoint outlines the products (*capabilities*) an account has access to and provides an overview of the status of all the products. Products are Method endpoints available for an account. Most products are accessible by default. However, some products have restricted access requiring team-by-team enablement and elevated account verification. **Account Products:** | Name | Use-Case | Supported Types | Resource Doc | | ------------ | ----------------------------------------------------------------------------------------------------------- | --------------- | ------------------------------------------------------ | | `update` | On-Demand real-time account update (balance, due dates, etc.) from the account's financial institution | All liabilities | [Updates](/reference/accounts/updates/overview) | | `balance` | On-Demand real-time balance from the account's financial institution | All liabilities | [Balances](/reference/accounts/balances/overview) | | `card_brand` | On-Demand retrieval of credit card metadata (Product / Brand Name, Art, etc.) directly from the card issuer | Credit Cards | [Card Brand](/reference/accounts/card-brands/overview) | | `payoff` | On-Demand retrieval of auto loan payoff (amount, per diem, etc.) from the account's financial institution | Auto Loans | [Payoffs](/reference/accounts/payoffs/overview) | | `payment` | Next day electronic push payments to the account's financial institution | All liabilities | [Payments](/reference/payments/overview) | | `sensitive` | On-Demand retrieval of underlying sensitive account information (PAN, CVV, account number) | All liabilities | [Sensitive](/reference/accounts/sensitive/overview) | * **The Products endpoint replaces:** * Utilizing `capabilities`, `available_capabilities`, and `pending_capabilities` in the Account object to determine the capabilities an account has access to. These fields have been deprecated from the Account object and removed in favor of: * `products` (products available for this Entity) * `restricted_products` (products not currently available, but can be made available) See [Products](/reference/accounts/products/overview) for more information. *** #### The Subscriptions endpoint Account [Subscriptions](/reference/accounts/subscriptions/overview) endpoint controls the state of all subscriptions for an account. Subscriptions are products that can provide continuous updates via Webhooks. (*e.g., Transaction Subscription provides real-time updates on a Credit Card’s transactions*). **Account Subscriptions:** | Name | Use-Case | Supported Types | Resource Doc | | ----------------- | ------------------------------------------------------------------------------------------------- | --------------- | --------------------------------------------------------- | | `transactions` | Real-time transaction (authorization, purchases, etc.) notifications for credit card accounts | Credit Cards | [Transactions](/reference/accounts/transactions/overview) | | `update` | Near real-time account update (balance, due dates, etc.) from the account's financial institution | All liabilities | [Updates](/reference/accounts/updates/overview) | | `update.snapshot` | Monthly account snapshot update (balance, due dates, etc.) from the credit bureau | All liabilities | [Updates](/reference/accounts/updates/overview) | * **The Subscriptions endpoint replaces:** * Custom configuration for continuous syncs via your Method CSM. This has been deprecated and replaced by [Create a Subscription](/reference/accounts/subscriptions/create) endpoint. * Account Sync Enrollment `/accounts/{acc_id}/sync_enrollment` for enrollment in auto syncs. This has been deprecated and replaced with an Updates subscription. See [Updates](/reference/accounts/updates/overview) and [Create a Subscription](/reference/accounts/subscriptions/create) for more information. * `data_sync_type` has been removed from the Account endpoint. See [Updates](/reference/accounts/updates/overview) and [List all Subscriptions](/reference/accounts/subscriptions/list) for more information. See Account [Subscriptions](/reference/accounts/subscriptions/overview) for more information. *** ### Breaking Changes #### Account object changes * ✨ Product properties are now included in the Account object. By default, the ID of the latest product resource is returned and can be expanded in-line using the `expand` query param. See [Expanding Resources](/reference/expanding) for more information. * `latest_verification_session` * `update` * `balance` * `card_brand` * `payoff` * ✨ Products and Subscription status are now returned by the Account object. See [Account object](/reference/accounts/overview) for more information. * `products` * `restricted_products` * `subscriptions` * `available_subscriptions` * `restricted_subscriptions` * ✨ Liability name and fingerprint are now returned by the Account object. See [Account object](/reference/accounts/overview) for more information. * `liability.name` * `liability.fingerprint` * ✨ New account liability types are now supported and returned by the Account object. See [Account Liability Types](/reference/accounts/overview#account-liability-types) for more information. * ⛔ Liability data under the `account.liability.` property has been deprecated and removed in favor of [Updates](/reference/accounts/updates/overview) * The `updates` field returns the ID of the latest update and can be expanded to return liability account data in-line using the `expand` query param. See [Expanding Resources](/reference/expanding) for more information. * ⛔ Syncing liability data using `/accounts/{acc_id}/syncs` has been deprecated and removed in favor of [Updates](/reference/accounts/updates/overview) * Additionally, data sync status fields at the account liability object have been deprecated and removed in favor of status fields within an [Update](/reference/accounts/updates/overview) * `liability.data_status`, `liability.data_sync_type`, `liability.data_sync_type`, `liability.data_last_successful_sync`, `liability.data_source`, `liability.data_updated_at`, `liability.data_updated_at`, `liability.data_status_error` * ⛔ Account capabilities have been deprecated and removed from the Account object. * `capabilities`, `available_capabilities`, and `pending_capabilities` have been deprecated and removed in favor of [Products](/reference/accounts/products/overview), [Subscriptions](/reference/accounts/subscriptions/overview), and [Account Verification Sessions](/reference/accounts/verification-sessions/overview) * The `products` array returns the products the account has access to, replacing `capabilities`. * The `restricted_products` array returns the products the account does not have access to, replacing `pending_capabilities`. * The account [Products](/reference/accounts/products/overview) endpoint outlines the products (*capabilities*) an account has access to and provides an overview of the status of all the products. * ⛔ Account payment status (`liability.payment_status`) has been deprecated and removed in favor of [Products](/reference/accounts/products/overview) * ⛔ Account clearing (`clearing`) and liability hash (`liability.hash`) has been deprecated and removed in `2024-04-04` * The following fields have been modified in the [Account object](/reference/accounts/overview): * `liability.payment_status` * `liability.data_status` * `liability.data_sync_type` * `liability.data_last_successful_sync` * `liability.data_source` * `liability.data_updated_at` * `liability.data_status_error` * `liability._liability_type_` - where `liability_type` is any of the [Account Liability Types](/reference/accounts/overview#account-liability-types). * `liability.hash` * `clearing` * `capabilities` * `available_capabilities` * `pending_capabilities` * `liability.name` * `liability.fingerprint` * `latest_verification_session` * `update` * `balance` * `card_brand` * `payoff` * `products` * `restricted_products` * `subscriptions` * `available_subscriptions` * `restricted_subscriptions` #### Deprecated endpoints * Account Syncs: `/accounts/{acc_id}/syncs` removed in favor of [Updates](/reference/accounts/updates/overview) * Account Sync Enrollment: `/accounts/{acc_id}/sync_enrollment` removed in favor of [Updates](/reference/accounts/updates/overview) and [Subscriptions](/reference/accounts/subscriptions/overview) * Account Verification: `/accounts/{acc_id}/verification` removed in favor of [Account Verification Sessions](/reference/accounts/verification-sessions/overview) * Account Sensitive: `/accounts/{acc_id}/sensitive` removed in favor of [Sensitive](/reference/accounts/sensitive/overview) * Account Card: `/accounts/{acc_id}/card` removed in favor of [Card Brand](/reference/accounts/card-brands/overview), [Sensitive](/reference/accounts/sensitive/overview) and Credit Card [Account Verification Sessions](/reference/accounts/verification-sessions/overview) * Account Payment History: `/accounts/{acc_id}/payment_history` is no longer supported in `2024-04-04` * Account Details: `/accounts/{acc_id}/details` is no longer supported in `2024-04-04` * Bulk Sensitive: `/accounts/{acc_id}/bulk_sensitive` is no longer supported in `2024-04-04` * Bulk Sync: `/accounts/{acc_id}/bulk_sync` is no longer supported in `2024-04-04` * Account Vehicle: `/accounts/{acc_id}/match_vehicle` is no longer supported in `2024-04-04` * Routing Numbers: `/routing_numbers` is no longer supported in `2024-04-04` * BINs: `/bins` is no longer supported in `2024-04-04` ## Additional Changes ### Expand Parameter New `expand` query parameter for expanding certain properties from an ID to their respective objects in-line in the response body. Applicable to both Entities and Accounts, allowing expansion of fields such as `connect`, `credit_score`, `update`, `balance`, `payoff`, `sensitive`, `transactions`, `card_brand`, and `latest_verification_session`. See [Expanding Resources](/reference/expanding) for more information. ### Elements Introducing the [Connect element](/elements/connect/overview) as the primary way to connect user accounts and complete necessary verifications. The Auth element has been deprecated in favor of Connect. See [Connect guide](/elements/connect/overview) for step-by-step instructions on leveraging Connect. # Introducing API Version 2025-07-04 Source: https://docs.methodfi.com/changelog/api-versions/2025-07-04 We're excited to announce the release of **API version `2025-07-04`**, featuring key improvements to our **Card Brand** model and the introduction of the new **Card Products API**. This version enhances data consistency across card networks, issuers, and products — enabling more structured integrations and cleaner brand experiences for your users. *** ## What’s New ### Card Brand API Card Brands The [Card Brand API](/reference/accounts/card-brands/overview) has been expanded with a **richer, more structured object**. This change makes it easier to **identify, display, and integrate** specific card products while ensuring consistent metadata across networks and issuers. **Key improvements:** * Brand data is now **fully nested**, encapsulating `network`, `issuer`, and visual assets under each brand. * New fields such as `card_product_id`, `description`, and `type` provide more granular control when mapping and displaying cards. * Removed legacy fields (`last4`, `shared`) for a cleaner, product-centric response format. Available when passing `Method-Version: 2025-07-04` in the request header. ```json theme={null} { "id": "cbrd_eVMDNUPfrFk3e", "account_id": "acc_yVf3mkzbhz9tj", "network": "visa", "issuer": "Chase", "last4": "8623", "brands": [ { "id": "brand_AMxtjQzAfDCRP", "name": "Chase Sapphire Reserve", "url": "https://static.methodfi.com/card_brands/1b7ccaba6535cb837f802d968add4700.png" } ], "status": "completed", "shared": false, "source": "network", "error": null, "created_at": "2024-03-19T01:05:37.247Z", "updated_at": "2024-03-19T01:05:37.247Z" } ``` ```json theme={null} { "id": "cbrd_Accm7P6t6mYQP", "account_id": "acc_LxwEqNicr66yP", "brands": [ { "id": "pdt_15_brd_1", "card_product_id": "pdt_15", "description": "Chase Sapphire Reserve", "name": "Chase Sapphire Reserve", "issuer": "Chase", "network": "visa", "network_tier": "infinite", "type": "specific", "url": "https://static.methodfi.com/card_brands/1b7ccaba6535cb837f802d968add4700.png" } ], "status": "completed", "source": "method", "error": null, "created_at": "2025-08-12T00:56:50.139Z", "updated_at": "2025-08-12T00:56:50.139Z" } ``` *** ### Card Products API We’re introducing the new [Card Products API](/reference/card-products/overview) — a **directory of card products** that allows you to retrieve all associated `Card Brand` objects for a given product. This endpoint gives developers a unified way to reference and display card metadata (art, network, tier, and issuer) across all variants of a card family. Available when passing `Method-Version: 2025-07-04` in the request header. ```bash theme={null} curl https://production.methodfi.com/card_products/pdt_17 \ -H "Method-Version: 2025-07-04" \ -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" ``` ```json theme={null} { "id": "pdt_17", "name": "Chase Freedom", "issuer": "Chase", "type": "specific", "brands": [ { "id": "pdt_17_brd_1", "description": "Chase Freedom", "network": "visa", "network_tier": "signature", "default_image": "https://static.methodfi.com/card_brands/fb5fbd6a5d45b942752b9dc641b93d1f.png" }, { "id": "pdt_17_brd_2", "description": "Chase Freedom", "network": "visa", "network_tier": "standard", "default_image": "https://static.methodfi.com/card_brands/6cb697528b0771f982f7c0e8b8869de3.png" } ] } ``` *** ## Breaking Changes * **Card Brand response shape updated** * `network` and `issuer` are now nested under each `brand`. * New fields: `card_product_id`, `description`, `type`. * Removed fields: `last4`, `shared`. *** ## Why It Matters This release unifies how card data is modeled and consumed across the Method platform. By standardizing the `Card Brand` object and introducing a canonical `Card Products` directory, developers can now: * Reliably map and display card details across networks and issuers * Build consistent card selection and branding experiences in their apps * Reduce dependency on ad-hoc naming or inferred card data *** ## Upgrading to 2025-07-04 The new API version is available to all existing teams. New teams are automatically pinned to **`2025-07-04`**. * **Request Header:** Set `Method-Version` to `2025-07-04`. See [API Versioning](/reference/versioning#api-versioning) for more information. * **Client Libraries:** `method-node` and `method-python` **v2.0.0+** default to this version. > Once upgraded, rollbacks to prior API versions are not supported. Contact your Method CSM for upgrade assistance. *** ### Upgrade Support Our technical integration team is available to guide you through the migration. Contact your Method CSM to schedule a review of your current card integration or to receive a personalized upgrade checklist. # Introducing API Version 2025-12-01 Source: https://docs.methodfi.com/changelog/api-versions/2025-12-01 We're excited to announce the release of **API version `2025-12-01`**, featuring the new **Payment Instruments API** for inbound funding workflows. This version enables liability accounts to receive direct payments via ACH or wire transfer — allowing third parties to send funds directly to liability accounts without requiring explicit Payment creation. *** ## What's New ### Payment Instruments API Method now supports **inbound funding workflows** with the introduction of a new `PaymentInstrument` type: `inbound_achwire_payment`. This feature allows liability accounts (e.g., loans, credit cards) to receive direct payments via ACH or wire transfer. **Key features:** * Provisions a unique virtual account number and routing number linked to a specific Method Account, effectively making the underlying liability routable * Third parties can send funds directly to these credentials, and Method automatically applies the funds to the associated account, without requiring you to explicitly create a Payment * Supports use cases such as payroll, refinancing, and other direct payment scenarios **How it works:** 1. **Create Instrument**: Create a Payment Instrument of type `inbound_achwire_payment` for a specific Method Account 2. **Receive Banking Details**: Method returns unique `account_number` and `routing_number` 3. **Share with a Third Party**: Provide these banking details to a third party (e.g., payroll provider, refinance lender, or another bank) 4. **Inbound Transfer**: When funds are sent to these credentials, Method receives the inbound ACH or wire transfer 5. **Automatic Application**: Method automatically applies the received funds to the associated account Available when passing `Method-Version: 2025-12-01` in the request header. ```bash theme={null} curl https://production.methodfi.com/accounts/acc_4m9amk4KFiaQX/payment_instruments \ -X POST \ -H "Method-Version: 2025-12-01" \ -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" \ -H "Content-Type: application/json" \ -d '{ "type": "inbound_achwire_payment" }' ``` ```json theme={null} { "id": "pmt_inst_cLbaArHhfDBDf", "account_id": "acc_GAzrD99cUqGEN", "type": "inbound_achwire_payment", "card": null, "network_token": null, "inbound_achwire_payment": { "account_number": "2517228863", "routing_number": "026015244" }, "chargeable": true, "status": "completed", "error": null, "created_at": "2025-12-11T00:12:58.639Z", "updated_at": "2025-12-11T00:12:58.639Z" } ``` See [Payment Instruments](/reference/accounts/payment-instruments/overview) for more information. *** ### Simulate API The [Simulate API](/reference/simulations/overview) now supports simulating inbound ACH / wire payments for `inbound_achwire_payment` Payment Instruments — making it easier for developers to test inbound payment flows in the development environment. **[Simulate Inbound ACH/Wire Payments](/reference/simulations/payment_instruments/create)**\ This endpoint allows developers to simulate receiving an inbound payment and triggers the same automatic payment application logic used in production. Available when passing `Method-Version: 2025-12-01` in the request header. This API is available in the development environment only. For more information, visit the [Simulations API](/reference/simulations/overview) documentation. *** ## Breaking Changes * **Payment Instrument product names changed** * The `payment_instrument` product name has been split into three separate product names: * `payment_instrument.card` * `payment_instrument.network_token` * `payment_instrument.inbound_achwire_payment` * In previous versions (`2024-04-04`, `2025-07-04`), the Account object's `products`, `restricted_products`, `subscriptions`, `available_subscriptions`, and `restricted_subscriptions` arrays contained the single product name `payment_instrument`. * In `2025-12-01`, these arrays now contain the three separate product names instead of the single `payment_instrument` name. *** ## Why It Matters This release enables new inbound funding workflows that simplify payment collection for liability accounts. By introducing `inbound_achwire_payment` Payment Instruments, developers can now: * Enable third parties to send payments directly to liability accounts without explicit Payment creation * Streamline payroll, refinancing, and other direct payment scenarios * Automatically apply inbound transfers to the associated account * Test inbound payment flows more easily with enhanced Simulate API support *** ## Upgrading to 2025-12-01 The new API version is available to all existing teams. New teams are automatically pinned to **`2025-12-01`**. * **Request Header:** Set `Method-Version` to `2025-12-01`. See [API Versioning](/reference/versioning#api-versioning) for more information * **Client Libraries:** `method-node` and `method-python` **v2.1.0+** default to this version > Once upgraded, rollbacks to prior API versions are not supported. Contact your Method CSM for upgrade assistance. *** ### Upgrade Support Our technical integration team is available to guide you through the migration. Contact your Method CSM to schedule a review of your current payment integration or to receive a personalized upgrade checklist. # Create a Connect Element Token Source: https://docs.methodfi.com/elements/connect/create_connect_token Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. To start using Connect, you will first need to create a [Connect Element Token](/reference/elements/tokens). There are a few different use cases that will determine what you pass to the endpoint. ### New Entities If you do not have any identity information about your users, you will likely create a token using a payload similar to this: ```json theme={null} { "type": "connect", "connect": { "products": ["balance"], "entity": { "type": "individual", "individual": {} } } } ``` This will return a token that you can use to create a new entity and connect their accounts. Fill in the `products` array with a list of the different products you want to connect (for example `["balance", "card"]`). ### New Entities with Partial Information If you have some information already about a given user (such as their name), you can pass that information into the `individual` object: ```json theme={null} { "type": "connect", "connect": { "products": ["balance"], "entity": { "type": "individual", "individual": { "first_name": "Kevin", "last_name": "Doyle" } } } } ``` You can also pass in a user's phone number, address, DOB, or the last 4 digits of their SSN to make the identity verification process faster. ### Using with Existing Entities You can also pass in an existing entity\_id: ```json theme={null} { "type": "connect", "entity_id": "ent_au22b1fbFJbp8", "connect": { "products": ["balance"] } } ``` ### Using with Existing Accounts If you also have specific accounts you'd like to connect, you can pass the account ids: ```json theme={null} { "type": "connect", "entity_id": "ent_au22b1fbFJbp8", "connect": { "products": ["balance"], "accounts": ["acc_k8LAKDnED7kti", "acc_KUaFnxn7eUAeH"] } } ``` ```bash cURL theme={null} curl https://dev.methodfi.com/elements/token \ -X POST \ -H "Method-Version: 2025-07-04" \ -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" \ -H "Content-Type: application/json" \ -d '{ "type": "connect", "connect": { "products": ["balance"], "entity": { "type": "individual", "individual": { "first_name": "Kevin", "last_name": "Doyle" } } } }' ``` ```javascript Node.js theme={null} const token = await method.elements.token.create({ type: "connect", connect: { products: ["balance"], entity: { type: "individual", individual: { first_name: "Kevin", last_name: "Doyle" } } } }); ``` ```python Python theme={null} token = method.elements.token.create({ 'type': "connect", 'connect': { 'products': ["balance"], 'entity': { 'type': "individual", 'individual': { 'first_name': "Kevin", 'last_name': "Doyle" } } } }) ``` ```json theme={null} { "element_token": "pk_elem_qPmypE9wwphr3WL3yTj7JhxjrPzAmK8G" } ``` # Getting Connect Results Source: https://docs.methodfi.com/elements/connect/get_results Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. In addition to [listening for the success event](/elements/events/overview), the result of the Connect session can also be retrieved by calling the `results` endpoint with the element token for that session. ```bash theme={null} GET /elements/token/{element_token}/results ``` See [Retrieve Element Results](/reference/elements/results) for more information about this endpoint. ```bash cURL theme={null} curl https://production.methodfi.com/elements/token/pk_elem_dDe4r9M6X3Ad9zjpbgYpzLNtRCXfhPYR/results \ -X GET \ -H "Method-Version: 2025-07-04" \ -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" ``` ```javascript Node.js theme={null} const response = await method .elements .token .results('pk_elem_dDe4r9M6X3Ad9zjpbgYpzLNtRCXfhPYR'); ``` ```python Python theme={null} response = method .elements .token .results('pk_elem_dDe4r9M6X3Ad9zjpbgYpzLNtRCXfhPYR') ``` ```json theme={null} { "authenticated": true, "cxn_id": "cxn_xr86xHEcWmpmB", "accounts": [ "acc_jPXLFqd6KzH3N", "acc_DALLeLrj3TH8h" ], "entity_id": "ent_GWKYtnFyE79db", "events": [ { "type": "open", "metadata": { "element_type": "connect", "op": "open" }, "timestamp": "2024-04-25T02:35:28.097Z" }, { "type": "success", "metadata": { "entity_id": "ent_GWKYtnFyE79db", "accounts": [ "acc_jPXLFqd6KzH3N", "acc_DALLeLrj3TH8h" ], "element_type": "connect", "op": "success" }, "timestamp": "2024-04-25T02:35:57.120Z" }, { "type": "exit", "metadata": { "element_type": "connect", "op": "exit" }, "timestamp": "2024-04-25T02:35:57.138Z" } ] } ``` # Launching a Connect Session Source: https://docs.methodfi.com/elements/connect/launch_connect Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. After creating a Connect Element token, you can launch a Connect session in a webview. ## Initializing the Connect Element The Connect Element is optimized to work within Webviews, including on iOS and Android. Open a webview in your app to your desired environment using the `element_token` you generated. Example: Using the [Element SDK](/elements/libraries) (recommended): ```javascript theme={null} method.open('pk_elem_BtzySdrQGFmLdAPw5gXSQNCxQkhCkT3K'); ``` Without SDK: ```bash theme={null} https://elements.production.methodfi.com/ ?token=pk_elem_4PpMTPcchb49VBjwP3bREKhMN93hrQHR ``` # Connect Overview Source: https://docs.methodfi.com/elements/connect/overview Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. Connect is the primary way to leverage Method Elements to connect your users' liabilities. Connect allows you to verify a user's identity, gather their consent, and complete any needed verifications to ensure their accounts are connected to the desired Method [Products](/reference/accounts/products/overview). The Connect element itself consists of two main steps: Verify the user's identity and connect their accounts. If no entity information is provided when creating the Connect element token, the user will be asked to provide identity information such as name, phone, last 4 digits of SSN, DOB, or address. Request any additional information needed from the user to connect their accounts and leverage specific products. # Environments Source: https://docs.methodfi.com/elements/environments Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. Elements are available in each of our three [Environments](/reference/environments): ``` https://elements.dev.methodfi.com (Development) https://elements.sandbox.methodfi.com (Sandbox) https://elements.production.methodfi.com (Production) ``` ## Considerations for Connect When using the [Connect Element](/elements/connect/overview), there are a few things to keep in mind related to the different environments. ### Development Environment In dev, you can use the following phone numbers to ensure your entity gets verified: ```bash theme={null} Phone | Required Fields ------------------------------ +15121231111 | Name, Phone +15121231112 | Name, Phone, DOB (Date of Birth) +15121231113 | Name, Phone, DOB (Date of Birth), Address ``` You can either pass in the required fields on token creation or during the Connect session. **Note**: If you do not use one of the above phone numbers, your dev entities will not be verified. # General Events Source: https://docs.methodfi.com/elements/events/general_events Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. ## Open The open event is triggered when an element has successfully launched. No additional data is passed at this time. ```bash theme={null} methodelements://general ?op=open &element_type=connect ``` The event payload will have the following form: ## Error The error event is sent for any element that encounters any error while it's active. ```bash theme={null} methodelements://general ?op=error &element_type=unknown &type=INVALID_REQUEST &sub_type=EXPIRED_TOKEN &message=The public element token is no longer valid. Element tokens are short lived and can only be used once. Request a new element token and try your request again. &code=400 ``` The event payload will have the following form: ## Exit The exit event is the last event in the element flow, at this point your app should no longer present the Method Element. Exit is triggered after an error, a user requested exit or a successful element event. ```bash theme={null} methodelements://general ?op=exit &element_type=connect ``` The event payload will have the following form: # Events Overview Source: https://docs.methodfi.com/elements/events/overview Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. Communication between the Element and your app can be handled either by PostMessage communication or via HTTP redirects. ## Listening to Events We strongly recommend using one of the [Element SDKs](/elements/libraries) to make listening to events easy. They provide you with callback functions that are invoked every time a specific type of event occurs (such as `open`, `success`, `exit`, etc). Each type of Element will emit its own events. See [General Events](/elements/events/general_events) and [Element Specific Events](/elements/events/specific_events) for more information about the events that are emitted. ### PostMessage without SDK To receive events via PostMessage, pass the query parameter `event_channel=message` to the Elements url. For example: ```bash theme={null} https://elements.production.methodfi.com ?token=pk_elem_4PpMTPcchb49VBjwP3bREKhMN93hrQHR &event_channel=message ``` To listen to the emitted events, add an event listener onto the window object: ```javascript theme={null} window.addEventListener('message', function(event) { const { payload, type } = event.data; console.log('Received event!', type, payload); }); ``` ### Redirects Redirects are the default way of listening to element events if you are not using one of the SDKs. Your webview / app should intercept the redirects in order to react accordingly to state changes. All redirect URLs will have the scheme ("prefix") `methodelements`. The event source will be the URL host and the payload will be query strings. HTTP redirects from Method Elements are in the following format: ```bash theme={null} methodelements://{event_source}?{event_data} ``` # Element Specific Events Source: https://docs.methodfi.com/elements/events/specific_events Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. ## Connect Connect will emit a `success` event when the user has successfully completed all required authentication and verification: ```bash theme={null} methodelements://connect ?op=success &element_type=connect &entity_id=ent_WyDmJnQgaxVRH &accounts=["acc_PFUNazUbpUpfm","acc_gjWr4Cb8H7TLz"] ``` When parsed, will result in the following JSON ```json theme={null} { "op": "success", "element_type": "connect", "entity_id": "ent_WyDmJnQgaxVRH", "accounts": ["acc_PFUNazUbpUpfm","acc_gjWr4Cb8H7TLz"] } ``` This will list all of the accounts that were consented and connected to at least one of the products passed into the Element token creation (Note: Some accounts are ineligible for some products). ## Other Events For more granular information about specific actions a user is taking, `auth` and `account_verification` will emit the following events. ### Auth Auth will emit a variety of events that describe how the user is progressing through the authentication process. Most events are of the following form: ```bash theme={null} AUTH_{STEP}_{ACTION} ``` STEP will reference a step during the auth process: `INTRO`, `NAME`, `PHONE`, `PHONE_VERIFY`, `DOB`, `ADDRESS`, `SSN4`, `SECQ`, and `CONSENT`. ACTION will refer to the action the user took: `OPEN`, `CONTINUE`, `SUBMIT`, and `CLOSE`. **Note**: Not all steps will have all actions, and that there are a few actions that do not follow this pattern For example, if the user was prompted for the last 4 of their SSN, then submitted their info and was directed to the DOB page, you would see the following events: ```bash theme={null} AUTH_SSN4_OPEN AUTH_SSN4_CONTINUE AUTH_DOB_OPEN ``` ### Account Verification Account Verification will emit a variety of events using a similar structure to auth: ```bash theme={null} AVF_{STEP}_{ACTION} ``` STEP will reference a step during the account verification process: `ACCOUNT_LIST`, `LEARN_MORE`, and `ACCOUNT_VERIFY`. ACTION will refer to the action the user took: `OPEN`, `CONTINUE`, `SUBMIT`, `SKIP`, and `CLOSE`. For example, if the user was prompted to verify their credit card, then submitted their info and was directed to the success screen, you would see the following events: ```bash theme={null} AVF_ACCOUNT_VERIFY_OPEN AVF_ACCOUNT_VERIFY_SUBMIT AVF_SUCCESS_OPEN ``` # Element SDKs Source: https://docs.methodfi.com/elements/libraries Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. Method offers a variety of libraries for your frontend application to make integrating with Elements easy and simple. We also offer [backend libraries](TODO:Where_is_link) to help manage token creation and using the API more broadly. ## Frontend Libraries Depending on your application, Method offers three different frontend libraries to help you integrate with Element: 1. [method-js](https://docs.methodfi.com/libraries/js-sdk), for vanilla JavaScript applications 2. [react-method-elements](https://github.com/MethodFi/react-method-elements), for React applications 3. [react-native-method-elements](https://github.com/MethodFi/react-native-method-elements), for React Native applications # Overview Source: https://docs.methodfi.com/elements/overview Method Elements will no longer be supported or maintained beginning December 31st, 2025. We recommend using [Method Opal](/opal/overview) for all new integrations. If you are currently using Elements, please reach out to your CSM to discuss your migration options. Method Elements is a collection of embeddable UI components that make it easy to integrate Method's API into your experience. Using Method Elements, you can securely identify your users, connect their liabilities, and move money across accounts. ## Using Method Elements Your app's backend will generate an `element_token` by hitting the [/elements/token](/reference/elements/tokens) endpoint. Using the `element_token`, Method Elements will be [initialized](/elements/libraries) with the intended Element for your user. While your user interacts with an Element, [events](/elements/events/overview) will be triggered for your app to handle. ### Authentication Ensure you have an [API key created](/reference/authentication) for your organization in order to request an Element token. # Overview Source: https://docs.methodfi.com/libraries/overview Method offers a list of official libraries that help developers easily interact and build on top of the Method services. ## API client Libraries Below is a list of libraries for each supported programming language. These libraries are updated frequently to provide the best developer experience when interacting with the Method API. } href="https://github.com/MethodFi/method-node" /> } href="https://github.com/MethodFi/method-python" /> ## Element client libraries Method supports a list of frontend libraries to make integrating Element into your applications more seamless. } href="/https/docs.methodfi.com/libraries/js-sdk" /> } href="https://github.com/MethodFi/react-method-elements" /> } href="https://github.com/MethodFi/react-native-method-elements" /> ## Quickstart and examples We've built a couple of quickstart applications to help you get started with seamlessly building on top of Method. } href="https://www.postman.com/methodfi/method-api/collection/8d5j00b/method-api-v2" /> # Account Verification Source: https://docs.methodfi.com/opal/account_verification/overview Mode: `account_verification` Opal Account Verification is a pre-built flow for verifying a specific account. It provides a secure, compliant way to verify a single, known account (for example, a specific credit card). account-verification-hero ## What this mode does Account Verification drives a focused verification flow for a single, known account (for example, a specific credit card). You must pass the target account\_id. Account Verification will automatically be invoked when needed (for example, during card\_connect), or can be used as a standalone module. ## Parameters ## Create a token You can create an account verification session token using one of the supported patterns: * Existing entity: provide `entity_id` + `mode` + `account_verification` * Create new entity: provide `entity` + `mode` + `account_verification` * Resume session: provide `session_id` only (omit `mode` and `account_verification`) ### Existing Entity ```json theme={null} { "entity_id": "ent_...", "mode": "account_verification", "account_verification": { "account_id": "acc_..." } } ``` ### Create New Entity ```json theme={null} { "entity": { "type": "individual", "individual": { "first_name": "Kevin", "last_name": "Doyle", "phone": "+15125551234" } }, "mode": "account_verification", "account_verification": { "account_id": "acc_..." } } ``` ### Response ```json theme={null} { "token": "otkn_...", "valid_until": "2025-06-10T22:50:53.024Z", "session_id": "osess_..." } ``` ## Launch Opal ```tsx theme={null} import { OpalProvider, useOpal } from "@methodfi/opal-react"; function Screen() { const { open } = useOpal({ env: "dev", onEvent: (e) => {} }); const start = async () => { const { token } = await getTokenFromBackend(); open({ token }); }; return ; } ``` ```tsx theme={null} import { OpalProvider, useOpal } from "@methodfi/opal-react-native"; function Screen() { const { open } = useOpal({ env: "dev", onEvent: (e) => {} }); const start = async () => { const { token } = await getTokenFromBackend(); open({ token }); }; return ; } ``` ```tsx theme={null} import { OpalProvider, useOpal } from "@methodfi/opal-react-native"; function Screen() { const { open } = useOpal({ env: "dev", onEvent: (e) => {} }); const start = async () => { const { token } = await getTokenFromBackend(); open({ token }); }; return ; } ``` ```tsx theme={null} import { OpalProvider, useOpal } from "@methodfi/opal-react-native"; function Screen() { const { open } = useOpal({ env: "dev", onEvent: (e) => {} }); const start = async () => { const { token } = await getTokenFromBackend(); open({ token }); }; return