Create a new subaccount

Creates a new subaccount for fund segregation within your root entity’s main account.

Request Body

Field	Type	Required	Description	Validation Rules
`name`	String	Yes	Name of the subaccount	Must be between 1 and 100 characters

Response Body

Field	Type	Description
`id`	UUID	Unique identifier of the subaccount
`name`	String	Name of the subaccount
`account_number`	String	Account number for deposits
`routing_number`	String	Deprecated: use `routing_numbers.ach`. Kept for backward compatibility
`routing_numbers`	Object	Routing numbers per rail (see below)
`routing_numbers.ach`	String	ACH routing number for ACH transfers
`routing_numbers.wire`	String	Wire routing number for wire transfers. For JPM VRNs with separate wire config, differs from ach. For other banks, same as ach.
`total_incoming_in_minor_units`	Integer	Total incoming funds in the smallest unit of the account’s currency (settled payins + incoming moves) - initially 0
`total_outgoing_in_minor_units`	Integer	Total outgoing funds in the smallest unit of the account’s currency (settled/debited payouts + outgoing moves) - initially 0
`created_at`	DateTime	ISO 8601 timestamp when the subaccount was created
`updated_at`	DateTime	ISO 8601 timestamp when the subaccount was last updated

Virtual Banking Details

Upon creation, each subaccount is assigned virtual banking details that can be shared with payers for direct deposits:

Account Number: Unique account number for receiving deposits
Routing Numbers: Use routing_numbers.ach for ACH transfers. For JPM VRNs, use routing_numbers.wire for wire transfers (same account number, different routing number per rail).

Use these details to configure payment processors to route funds to specific subaccounts.

Error Responses

Status	error_code	When
400	VALIDATION_ERROR	Request body failed validation (e.g. invalid or missing `name`)
400	VALIDATION_ERROR	Subaccounts are not supported for your operating account currency (e.g. non-USD main account while that capability is unavailable)

Creates a new subaccount for fund segregation within your root entity's main account. **Request Body** | Field | Type | Required | Description | Validation Rules | |-------|------|----------|-------------|-----------------| | `name` | String | Yes | Name of the subaccount | Must be between 1 and 100 characters | **Response Body** | Field | Type | Description | |-------|------|-------------| | `id` | UUID | Unique identifier of the subaccount | | `name` | String | Name of the subaccount | | `account_number` | String | Account number for deposits | | `routing_number` | String | Deprecated: use `routing_numbers.ach`. Kept for backward compatibility | | `routing_numbers` | Object | Routing numbers per rail (see below) | | `routing_numbers.ach` | String | ACH routing number for ACH transfers | | `routing_numbers.wire` | String | Wire routing number for wire transfers. For JPM VRNs with separate wire config, differs from ach. For other banks, same as ach. | | `total_incoming_in_minor_units` | Integer | Total incoming funds in the smallest unit of the account's currency (settled payins + incoming moves) - initially 0 | | `total_outgoing_in_minor_units` | Integer | Total outgoing funds in the smallest unit of the account's currency (settled/debited payouts + outgoing moves) - initially 0 | | `created_at` | DateTime | ISO 8601 timestamp when the subaccount was created | | `updated_at` | DateTime | ISO 8601 timestamp when the subaccount was last updated | **Virtual Banking Details** Upon creation, each subaccount is assigned virtual banking details that can be shared with payers for direct deposits: - **Account Number**: Unique account number for receiving deposits - **Routing Numbers**: Use `routing_numbers.ach` for ACH transfers. For JPM VRNs, use `routing_numbers.wire` for wire transfers (same account number, different routing number per rail). Use these details to configure payment processors to route funds to specific subaccounts. **Error Responses** | Status | error_code | When | |--------|------------|------| | 400 | VALIDATION_ERROR | Request body failed validation (e.g. invalid or missing `name`) | | 400 | VALIDATION_ERROR | Subaccounts are not supported for your operating account currency (e.g. non-USD main account while that capability is unavailable) |

Authentication

x-api-keystring

RootPay API key sent in the x-api-key header. Keys are environment-scoped: live_* for production, test_* for sandbox.

Request

This endpoint expects an object.

namestringRequired1-100 characters

Name of the subaccount

Response

Subaccount created successfully