> ## Documentation Index
> Fetch the complete documentation index at: https://docs.methodfi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Funding Accounts

> Set up and verify the Account used to fund Method Payments.

## 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](/guides/payments/flow-of-funds) to understand the standard funding flows, including Per-Payment funding.

Create the disbursement Account with [`POST /accounts`](/reference/accounts/create):

```bash theme={null}
curl https://production.methodfi.com/accounts \
  -X POST \
  -H "Method-Version: 2026-03-30" \
  -H "Authorization: Bearer sk_WyZEWVfTcH7GqmPzUPk65Vjc" \
  -H "Content-Type: application/json" \
  -d '{
    "holder_id": "ent_y1a9e1fbnJ1f3",
    "ach": {
      "routing": "021000021",
      "number": "1234567890",
      "type": "checking"
    }
  }'
```

Verify the Account before using it as a Payment source.

<Note>
  Your team configures funding Accounts. End users do not. End users connect liability Accounts; your verified disbursement Account funds the Payments.
</Note>

Method supports several verification approaches for funding accounts:

<CardGroup cols={2}>
  <Card title="Micro-Deposits" icon="coins">
    Method sends two small deposits. Confirm both amounts after they settle, typically in 1–2 business days.
  </Card>

  <Card title="Plaid" icon="bolt">
    Verify instantly with a Plaid processor token.
  </Card>

  <Card title="MX" icon="bolt">
    Verify instantly with an MX processor token.
  </Card>

  <Card title="Teller" icon="bolt">
    Verify instantly with a Teller processor token.
  </Card>
</CardGroup>

<Note>
  If your team does not use an existing bank data aggregator, Plaid is the recommended default for instant verification.
</Note>

## Verification Flow

1. Create the funding Account with [`POST /accounts`](/reference/accounts/create).
2. Create a Verification Session with [`POST /accounts/{id}/verification_sessions`](/reference/accounts/verification-sessions/create).
3. Complete the verification:
   * **Micro-deposits:** Wait 1–2 business days, then [submit both amounts](/reference/accounts/verification-sessions/update-microdeposits).
   * **Plaid, MX, or Teller:** Submit the processor token with the [Plaid](/reference/accounts/verification-sessions/update-plaid), [MX](/reference/accounts/verification-sessions/update-mx), or [Teller](/reference/accounts/verification-sessions/update-teller) endpoint.
4. Listen for the `account.update` [webhook](/reference/webhooks/overview). Retrieve the Account and confirm that its `status` is `active` before you use it.

See the [Account Verification Sessions reference](/reference/accounts/verification-sessions/overview) for full API details.

<Warning>
  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.
</Warning>

<Note>
  You can create multiple verified disbursement Accounts and select the source in each [`POST /payments`](/reference/payments/create) request.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.