Skip to main content

​
Funding Accounts — Setting Up Payment Sources

Before Payments can flow through Method, your program needs a verified disbursement Account. This is typically your company’s corporate checking Account, not an Account belonging to an end user. In the Prefunded (push) Model, you send funds from the disbursement Account to a Method-managed FBO Account by ACH or wire. In the Method Debit (pull) Model, Method debits the disbursement Account by ACH. See Flow of Funds Setup to understand the standard funding flows, including Per-Payment funding. Create the disbursement Account with POST /accounts:
Verify the Account before using it as a Payment source.
Your team configures funding Accounts. End users do not. End users connect liability Accounts; your verified disbursement Account funds the Payments.
Method supports several verification approaches for funding accounts:

Micro-Deposits

Method sends two small deposits. Confirm both amounts after they settle, typically in 1–2 business days.

Plaid

Verify instantly with a Plaid processor token.

MX

Verify instantly with an MX processor token.

Teller

Verify instantly with a Teller processor token.
If your team does not use an existing bank data aggregator, Plaid is the recommended default for instant verification.

​
Verification Flow

  1. Create the funding Account with POST /accounts.
  2. Create a Verification Session with POST /accounts/{id}/verification_sessions.
  3. Complete the verification:
  4. Listen for the account.update webhook. Retrieve the Account and confirm that its status is active before you use it.
See the Account Verification Sessions reference for full API details.
If verification fails, the Verification Session moves to failed. Create a new Verification Session to retry. A micro-deposit session permits five amount-submission attempts before it fails.
You can create multiple verified disbursement Accounts and select the source in each POST /payments request.