---
title: "Create reversal processing code"
method: POST
path: "/orgs-operation/v1/reversal-processing-codes"
tags: ["Reversal processing codes"]
---

# Create reversal processing code

`POST /orgs-operation/v1/reversal-processing-codes`

## Request

- Base URL: `https://sandbox.pismolabs.io`
- URL: `https://sandbox.pismolabs.io/orgs-operation/v1/reversal-processing-codes`
- Auth: HTTP bearer

Create a reversal processing code for an existing processing code.

This endpoint creates a `REVERSAL` type processing code and a [Orgs operation created](https://developers.pismo.io/events/docs/orgs-operation-create-1) event.

## Request body

- ReversalProcessingCodeCreateRequest
  - `processing_code` string, required: Processing code ID
  - `balance_impact` 1 | 0 | -1: Balance impact associated with processing code: * `1` - Credit * `0` - No impact. Zero balance operations have no impact. Zero balance customers are responsible for settling accounts and generating transactions. * `-1` - Debit
  - `description` string, required: Processing code description
  - `translations` object[]: Processing code descriptions translation in different languages
    - `language` string: Translation language. For example, the code for English (United States) is `en-US`. The prefix, `en`, is a language code following the ISO 639-1 standard. The suffix, `US`, is a country code following the ISO 3166-1 Alpha-2 standard.
    - `description` string: Translated description

## Response `201`

Created

- ReversalOrgsOperationCreateResponse
  - `processing_code` string: A processing code identifies a financial operation on the Pismo platform. Processing codes need to be mapped to transaction type codes to create a transaction flow. A custom processing code is created with a `PENDING` status . Initially, its use is not allowed in authorizations. Once the transaction flow for a custom processing code is completely configured, its status changes to `SUCCESS` and it is ready for use. For more information, refer to [Processing codes](doc:processing-codes-and-transaction-types)
  - `status` 'SUCCESS' | 'PENDING': Processing code status: * `PENDING` - Missing required configurations. A custom processing code is initially created with a `PENDING` status and its use is not allowed in authorizations. Once the transaction flow for a custom processing code is completely configured, its status changes to `SUCCESS` and it is ready for use. All standard processing codes have a `SUCCESS` status. * `SUCCESS` - Required configurations done

## Other responses

- `400`: Bad request error.

---

[API](https://skmtc.dev/pismo/apis/platform-setup-orgs-operation.md) - [All operations](https://skmtc.dev/pismo/apis/platform-setup-orgs-operation/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/platform-setup-orgs-operation/revisions/086ad02a703d?raw)