---
title: "Create split request"
method: POST
path: "/v1/transactions/{merchantTransactionId}/split"
tags: ["Split requests"]
---

# Create split request

`POST /v1/transactions/{merchantTransactionId}/split`

## Request

- Base URL: `https://sandbox.pismolabs.io/sellers`
- URL: `https://sandbox.pismolabs.io/sellers/v1/transactions/{merchantTransactionId}/split`
- Auth: HTTP bearer

Create a new split request for a merchant transaction.<br>
Managing financial transactions often requires dividing a single transaction into multiple parts for accurate record-keeping and reporting. The split transaction feature addresses this need by allowing you to split a transaction into different categories or assign portions to various accounts. This functionality is particularly useful for handling shared expenses, allocating costs across different budget categories, or separating business and personal expenses.
When a split request is created, it's created with a `PENDING` status. Before you request a split, make sure the merchant transaction is already in the `WAITING_SPLIT` status.<br>
This endpoint generates a [Merchant transaction created](https://developers.pismo.io/events/docs/merchants-merchant-transaction-created-1) event.

## Path parameters

- `merchantTransactionId` integer, required

## Headers

- `Authorization` string, required

## Request body

- SplitRequestPostSaleRequest
  - `event_date` string, datetime, required: Event datetime. The datetime format follows the ISO 8601 format (UTC).
  - `installments` integer, required: Number of installments
  - `processing_code` string, required: Processing code.<br> For more information, refer to [Processing codes](doc:processing-codes-and-transaction-types).
  - `definitions` SplitRequestPostSaleDefinitionsRequest[], required: Determines how the transaction amount is split among merchants and specifies the applicable taxes and discounts. `definitions` defines the number of merchants involved in the transaction, amount of tax or discount to apply, and the percentage or amount allocated to each merchant.
    - `merchant_id` integer, required: Merchant ID
    - `amount` number, float: Merchant's requested amount If the sum of all defined amounts is less than the authorized amount, the difference is applied to the first merchant in the list. Either `amount` or `amount_percentage` is **REQUIRED**. Example: - Amount: 100.00 - Amounts: [ 10.00, 20.00, 30.00 ] - Adjusted Amounts: [ 50.00, 20.00, 30.00 ]
    - `amount_percentage` number, float: Percentage of the gross amount of the merchant transactions. 10% is 0.10, 100% is 1.00 Either `amount` or `amount_percentage` is **REQUIRED**.
    - `processing_code` string, nullable: Merchant transaction processing code
    - `transaction_status` 'PENDING' | 'SCHEDULED' | 'SETTLED' | 'CANCELED', nullable: Merchant transaction status

## Response `202`

Successfully create split requests

- SplitRequestPostResponse: Split request ID
  - `id` integer: Marketplace ID

## Other responses

- `400`: Bad request
- `500`: Internal server error

---

[API](https://skmtc.dev/pismo/apis/seller-management-transactions.md) - [All operations](https://skmtc.dev/pismo/apis/seller-management-transactions/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/seller-management-transactions/revisions/95ba885d7f40?raw)