Accounts

Create transaction banking account

Creates a transaction banking account. For details, refer to Transaction banking accounts.

This endpoint generates the following events:

For more information about events and setting up event notifications, refer to the Data and reporting overview guide.

post/corporate/v1/corporate-accounts

Request

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

Request body

division_codestring 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_idinteger required

Program ID. The program must belong to the organization. Use List programs 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 Patch division

external_account_idstring 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_idinteger

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

currency_codestring

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).

Example request

{
  "division_code": "US",
  "program_id": 8674,
  "applicant": {
    "document_number": "812045147",
    "name": "Chester Fields",
    "external_id": "83bcde27-e049-4244-9dab-cfb4c88d70f8"
  },
  "external_account_id": "b993ba96-b3e8-4ef7-9cf7-7eee5ddafdab",
  "parent_account_id": 232,
  "account_creation_datetime": "2025-02-01T22:07:58.000Z",
  "overdraft": {
    "limit": 15680.45
  },
  "currency_code": "986"
}

Response

Account created

account_idinteger required

Account ID

program_idinteger required

Program ID. This is a client-provided ID.

external_account_idstring

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_codestring

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

Example response

{
  "account_id": 1234,
  "program_id": 2222,
  "external_account_id": "b993ba96-b3e8-4ef7-9cf7-7eee5ddafdab",
  "division_code": "US",
  "account_creation_datetime": "2024-01-04T10:25:30.123Z"
}

Changes

No recorded changes to this operation across all 1 revision of this API.