---
title: "Create check posting"
method: POST
path: "/corporate/v1/checks"
tags: ["Check posting"]
---

# Create check posting

`POST /corporate/v1/checks`

## Request

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

Allow clients to post a check for a specified external account, with the option to settle the amount either immediately or in the future.

**NOTES**:
  * This endpoint requires an account token - an access token encoded with an external account ID. Tokens can expire quickly, which can result in a `401 Unauthorized` message.
  * This endpoint generates the following events:
    - [Platform authorization created](https://developers.pismo.io/events/docs/platform-authorization-platform-authorization-1)
    - [Check posting status change](https://developers.pismo.io/events/docs/cash-management-check-status-change-1)

See [Data and reporting](doc:data-reporting-overview) for more information about events and setting up event notifications.

## Request body

- CheckPostingRequest: Request body for posting a check transaction.
  - `check_id` string, required: Check ID.
  - `check_amount` CheckAmount, required: Total check amount.
    - `value` number, float, required: Amount value
    - `currency` string: 3-letter code in ISO 4217-compliant format for the currency used in the transaction.
  - `settlement_type` 'BEGINNING' | 'END', required: Indicates when funds become available to the bank: `BEGINNING` or `END`.
  - `business_date` string, date: Specifying a `business_date` value impacts the account balance history.<br> <b>Notes</b>: - The business date is in ISO 8601 format. - The business date allows users to designate the balance history cycle in which a payment is posted. - You can specify a `business_date` within the current working day or up to one working day before or after.
  - `description` string: A brief description about a check posting transaction.
  - `settlements` CheckSettlementRequestItem[], required: List of check settlements. Each settlement represents a portion of the check amount to be settled on a specific date, with an associated type and tracking identifier.
    - `type` 'DEPOSIT' | 'PENDING' | 'HOLD', required: Settlement type. Indicates the nature of the settlement.
    - `tracking_id` string, required: A unique payment tracking number provided by the client. If an existing `tracking_id` is found on the Pismo platform, the API returns a `409` error. This field is: * Unique within the organization * Immutable: It can't be updated * Not recyclable: You can't reuse a `tracking_id`
    - `settlement_date` string, date, required: Settlement date in ISO 8601 format (yyyy-mm-dd).
    - `amount` number, required: Amount to be settled in the specified operation.

## Response `202`

Accepted. Returns the created check posting.

- CheckPostingResponse: Check posting response object.
  - `check_id` string, required: Check ID.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: The request has been lost
- `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)