---
title: "Request bulk settlement"
method: POST
path: "/corporate/v1/bulk-settlement"
tags: ["Bulk settlement"]
---

# Request bulk settlement

`POST /corporate/v1/bulk-settlement`

This endpoint triggers the clearing of future value-dated payments and check-release operations in bulk.<br>
A future value dated payment is a banking transaction that is scheduled to occur on a future date, such as a prepayment or normal payment. The bank is instructed to send the payment on a specific date, which can be the next day or later. When a payment is scheduled for a future date, the funds remain in the payer's account, continuing to accrue interest until the payment is settled on the scheduled date.

A check release is the process that moves funds from an uncleared or held state into the customer’s available balance. After a check is deposited, some or all of its amount remains pending until a scheduled release. When the check is released, the pending funds are applied, and the account balances are updated so that the amount becomes fully available for use.

<b>NOTE</b>: You can call this endpoint once with the same parameters, per division, settlement date, and operation type. If the process fails, you can retry up to 9 times per division, per business day.

## Request body

- BulkSettlementRequest — Bulk settlement request
  - `operation_type` 'DELETE' | 'SUSPEND' | 'RESUME' | 'CALL_CENTER_ACTIVATION' | 'CARDHOLDER_STEPUP_APP_TO_APP' | 'TOKEN_DEVICE_BIDING_APPROVE' | 'TOKEN_DEVICE_BINDING_APPROVE_BANK_APP', required — Operation type: * `DELETE` - Delete token * `SUSPEND` - Suspend token * `RESUME` - Resume suspended token * `CALL_CENTER_ACTIVATION` - Call center verification * `CARDHOLDER_STEPUP_APP_TO_APP` - App2App verification * `TOKEN_DEVICE_BIDING_APPROVE` - Device verification, approve and activate the most recently inactive device (only Visa) * `TOKEN_DEVICE_BINDING_APPROVE_CALL_CENTER` - Device verification with call center activation, approve and activate the most recently inactive device (only Visa) * `TOKEN_DEVICE_BINDING_APPROVE_BANK_APP` - Device verification with bank app approval, approve and activate the most recently inactive device (only Visa) **Note**: For App2App token activation, set this field to `CARDHOLDER_STEPUP_APP_TO_APP` (Mastercard) and `CALL_CENTER_ACTIVATION` (Visa).
  - `settlement_date` string, date, required — Future date on which the `float_amount` is settled. Corresponds to the cycle closing date relative to the payment date.<br> <b>Notes</b>: - The settlement date is in ISO 8601 format. - It's similar to the `business_date` attribute for regular payment operations.
  - `division_code` string, required — Division code registered in the [Create division](https://developers.pismo.io/pismo-docs/reference/post-division-v2) endpoint.
  - `bulk_id` string, required — Bulk settlement request ID provided by the requester.

## Response `202`

Accepted

## Other responses

- `400` — A Bad Request validation error
- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `409` — Conflict
- `429` — Too many requests
- `500` — Internal Errors

---

[API](https://skmtc.dev/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.dev/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)