> ## 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

> Setting up and verifying your corporate payment source.

## Funding Accounts — Setting Up Payment Sources

Before payments can flow through Method, your platform needs a verified funding source — an ACH account that serves as the origin for all outbound payments. This is typically your company's corporate checking account, not an account belonging to your end users.

Your platform creates the funding account by [calling the Accounts API](/reference/accounts/create) with the routing number and account number for your corporate bank account:

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

The account must then be verified to confirm your organization controls it. Once verified, this single funding account can serve as the payment source across all of your users' liability payments.

<Note>
  Funding accounts are set up by your team (the platform integrating with Method), not by your end users. End users interact with liability accounts discovered through Connect — your corporate funding account is the source that powers payments to those liabilities.
</Note>

Method supports several verification approaches for funding accounts:

<CardGroup cols={2}>
  <Card title="Micro-Deposits" icon="coins">
    The traditional verification method. Method sends two small deposits (typically a few cents each) to your corporate bank account. Your team confirms the deposit amounts, proving control of the account. This is universally supported but introduces a 1–2 business day delay while deposits settle.
  </Card>

  <Card title="Plaid" icon="bolt">
    Instant verification through Plaid's bank linking flow. If your platform already uses Plaid, this is a natural fit — authenticate with your bank through Plaid, and the verified account details are passed to Method. No waiting for micro-deposits.
  </Card>

  <Card title="MX" icon="bolt">
    Similar instant verification through MX's bank connectivity platform. Choose this if your platform uses MX for bank account linking.
  </Card>

  <Card title="Teller" icon="bolt">
    Another instant verification path through Teller's banking API. Like Plaid and MX, this eliminates the micro-deposit delay by verifying the account through direct bank authentication.
  </Card>
</CardGroup>

<Note>
  For most teams, instant verification (via Plaid, MX, or Teller) is strongly preferred because it eliminates the multi-day delay of micro-deposits and simplifies initial setup. If you don't have an existing relationship with any of these providers, Plaid is the most widely adopted option.
</Note>

## Verification Flow

1. Create the funding account ([`POST /accounts`](/reference/accounts/create))
2. Create a verification session ([`POST /accounts/{id}/verification_sessions`](/reference/accounts/verification-sessions/create)) specifying your preferred method
3. Complete the verification:
   * **Micro-deposits**: Wait 1–2 business days, then [update the session](/reference/accounts/verification-sessions/update-microdeposits) with the deposit amounts
   * **Plaid / MX / Teller**: Pass the processor token from your aggregator to the update endpoint ([Plaid](/reference/accounts/verification-sessions/update-plaid), [MX](/reference/accounts/verification-sessions/update-mx), [Teller](/reference/accounts/verification-sessions/update-teller))
4. Listen for the `account.active` [webhook](/reference/webhooks/overview) — the account is now ready for payments

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

<Warning>
  If verification fails (wrong micro-deposit amounts, invalid aggregator token), the verification session moves to a `failed` status. You can create a new verification session to retry. After 3 failed micro-deposit attempts, the account may require a fresh set of deposits.
</Warning>

<Note>
  Your team can have multiple verified funding accounts. When [creating a payment](/reference/payments/create), you specify which funding account to use as the source. Most teams use a single corporate checking account, but you can set up additional funding accounts if your business requires separate payment sources.
</Note>