---
title: "Create transaction banking account"
method: POST
path: "/corporate/v1/corporate-accounts"
tags: ["Accounts"]
---

# Create transaction banking account

`POST /corporate/v1/corporate-accounts`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/corporate/v1/corporate-accounts`
- Auth: HTTP bearer

Creates a transaction banking account. For details, refer to [Transaction banking accounts](doc:corporate-accounts).

This endpoint generates the following events:
 - [Corporate account created](https://developers.pismo.io/events/docs/corporate-corporate-account-creation-1).
 - [Account application created](https://developers.pismo.io/events/docs/onboarding-succeeded-1)

 For more information about events and setting up event notifications, refer to the [Data and reporting overview](doc:data-reporting-overview) guide.

## Request body

- CreateAccountRequest: Create corporate account request object
  - `division_code` string, required: Code used to identify your division within the organization. Division code should only contain letters, numbers, and hyphens. This is a client-provided ID and can be changed.
  - `program_id` integer, required: Program ID. The program must belong to the organization. Use [List programs](https://developers.pismo.io/pismo-docs/reference/programs-1) to view a list of the program IDs for the organization. This program must be bound to the division. You can attach the program with either of the following endpoints: [Create division](ref:post-division-v2) [Patch division](ref:patch-division-v2)
  - `applicant` object, required
    - `document_number` string, required: Applicant's government document number. Once set, this value is immutable, which means that `document_number` can't be updated. This field only accepts alphanumeric characters.<br> <b>Note</b>: `document_number` does not allow special characters.
    - `name` string, required: Applicant name
    - `external_id` string: Custom entity ID that uniquely identifies the entity within your organization. By default, `document_number` is used as the primary identifier. To set `external_id` as the primary identifier, contact a Pismo representative to enable the parameter `EXTERNAL ID AS MAIN KEY`.
    - `custom_fields` CustomFields: Name-value fields for any account-related data your organization needs to store at Pismo. This field can have its values validated against the JSON schema stored at the division (referenced by the `division_code`) field `schema`.
  - `external_account_id` string, required: Custom account ID. Used as the key for all operations (manage accounts, transactions, etc.) on the corporate layer. This field is: - Unique within the Organization - Immutable: The field cannot be updated. - Not recyclable: You can't reuse an external account ID, even if the account that was using it has been canceled.
  - `parent_account_id` integer: Parent account ID. If provided, the account is the child of the account referenced by `parent_account_id`. The account referenced by `parent_account_id` can be in another program or division.
  - `account_creation_datetime` string, date-time: The datetime the account was created (in UTC). The datetime format follows the ISO 8601 standard: `yyyy-mm-ddThh:mm:ss.sssZ`.<br> `minLength: 24` `maxLength: 24`
  - `overdraft` Overdraft
    - `limit` number, float, required: Account overdraft limit
  - `currency_code` string: Alphabetic or numeric code (ISO 4217) for the currency used by the program. (Use the same currency as the program, but this is only a temporary situation).

## Response `201`

Account created

- CreateAccountResponse: Create account response body
  - `account_id` integer, required: Account ID
  - `program_id` integer, required: Program ID. This is a client-provided ID.
  - `external_account_id` string: Custom account ID. Used as the key for all operations (manage accounts, transactions, etc.) on the corporate layer. This field is: - Unique within the Organization - Immutable: The field cannot be updated. - Not recyclable: You can't reuse an external account ID, even if the account that was using it has been canceled.
  - `division_code` string: Code used to identify your division within the organization. Division code should only contain letters, numbers, and hyphens. This is a client-provided ID and can be changed.
  - `account_creation_datetime` string, date-time: Datetime the account was created in the Pismo system (in UTC). The datetime format follows the ISO 8601 standard: `yyyy-mm-ddThh:mm:ss.sssZ`.<br> Note that milliseconds are represented as `000`, for example: `2024-02-22T16:51:49.000Z`.<br> This field accepts datetime values from the present or past. Future dates are not allowed.<br> `minLength: 24` `maxLength: 24`

## Other responses

- `400`: A Bad Request validation error. Static Validations (mandatory field, max value, max length, etc) have the code `WCAC0005`.
- `401`: Access token is missing or invalid
- `403`: The request has been lost
- `404`: Not Found
- `409`: Conflict.
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/banking-transaction-banking.md) - [All operations](https://skmtc.dev/pismo/apis/banking-transaction-banking/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/banking-transaction-banking/revisions/1334306c9303?raw)