Skip to main content

​
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 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
  • 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
  • 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 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 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 documentation.