---
title: "Get Funding Account"
method: GET
path: "/v2/fundingAccounts/{fundingAccountId}"
tags: ["Funding"]
---

# Get Funding Account

`GET /v2/fundingAccounts/{fundingAccountId}`

Get Funding Account by ID

## Path parameters

- `fundingAccountId` string, uuid, required

## Query parameters

- `sensitive` boolean

## Response `200`

Funding Account Response

- FundingAccountResponseV2
  - `id` string, uuid — Funding Account Id
  - `payorId` string, uuid
  - `accountName` string — name on the bank account
  - `accountNumber` string — bank account number
  - `routingNumber` string — bank account routing number
  - `name` string — name of funding account
  - `currency` string — Valid ISO 4217 3 letter currency code. See the <a href="https://www.iso.org/iso-4217-currency-codes.html" target="_blank" a>ISO specification</a> for details.
  - `countryCode` string — ISO 3166-1 2 letter country code (upper case)
  - `type` string — Funding account type. One of the following values: FBO, PRIVATE
  - `archived` boolean — A flag for whether the funding account has been archived. Only present in the response if true.

## Other responses

- `400` — Bad Request
- `401` — Invalid access token. May be expired or invalid
- `403` — The authentication does not have permissions to access the resource This usually occurs when there is a valid authentication instance (client or user) but they do not have the required permissions
- `404` — The resource was not found or is no longer available

---

[API](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis.md) · [All operations](https://skmtc.net/velopaymentsapi/apis/velo-payments-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/velopaymentsapi/velo-payments-apis/revisions/05c3f09fc50a/schema)