--- updatedAt: 2026-03-25T12:23:57.000Z --- Fetch the complete documentation index at: https://developers.pismo.io/pismo-docs/llms.txt. Use this file to discover all available pages before exploring further. # List processing codes Get an organization's processing codes with filtering options. # OpenAPI definition ```json { "openapi": "3.1.0", "info": { "title": "Platform setup - Orgs operation", "description": "Orgs operations management endpoints.", "version": "v1.0", "contact": { "name": "Pismo Support", "url": "https://developers.pismo.io/support/" }, "license": { "name": "Copyright Pismo." } }, "servers": [ { "url": "https://sandbox.pismolabs.io", "description": "Sandbox API server for testing" } ], "security": [ { "S2SAuthentication": [] } ], "tags": [ { "name": "Processing codes", "description": "Manage processing codes" } ], "components": { "parameters": { "GetProcessingCodesListCursorQuery": { "name": "nextCursor", "in": "query", "required": false, "description": "Cursor to get next results. This is the `next_cursor` field in the response.", "schema": { "type": "string" } }, "GetProcessingCodesListLimit": { "name": "limit", "in": "query", "required": false, "description": "Maximum items to return. 100 maximum.", "schema": { "type": "string" } } }, "schemas": { "BalanceImpact": { "type": "integer", "description": "Balance impact associated with processing code:\n * `1` - Credit \n * `0` - No impact. Zero balance operations have no impact. Zero balance customers are responsible for settling accounts and generating transactions.\n * `-1` - Debit\n", "enum": [ 1, 0, -1 ], "example": 1 }, "GetProcessingCodeItem": { "type": "object", "properties": { "processing_codes": { "type": "string", "description": "Processing code ID", "example": "01" }, "org_operation_id": { "type": "integer", "description": "Org operation ID" }, "balance_impact": { "$ref": "#/components/schemas/BalanceImpact" }, "description": { "type": "string", "description": "Processing code description", "example": "International purchase" }, "standard": { "$ref": "#/components/schemas/Standard" }, "reversal_processing_code": { "$ref": "#/components/schemas/ReversalProcessingCode" }, "partial_reversal_processing_code": { "$ref": "#/components/schemas/PartialReversalProcessingCode" }, "status": { "$ref": "#/components/schemas/Status" }, "tags": { "$ref": "#/components/schemas/Tags" }, "translations": { "$ref": "#/components/schemas/Translations" } } }, "GetProcessingCodesResponse": { "type": "object", "properties": { "has_next": { "type": "boolean", "description": "Are there more results?" }, "next_cursor": { "type": "string", "description": "Cursor to get next results" }, "count": { "type": "integer", "description": "Number of processing codes returned" }, "items": { "type": "array", "description": "Processing code items list", "items": { "$ref": "#/components/schemas/GetProcessingCodeItem" } } } }, "PartialReversalProcessingCode": { "type": "string", "description": "Partial reversal processing code. Processing code for partial reversal cancellation. Used in transactions and accounting flow to post the correct entries related to partial cancellation. \n\nEvery `AUTHORIZATION` processing code is **REQUIRED** to have a reversal and a partial reversal processing code. If a partial code isn't provided, a default one is assigned based on `balance_impact`. \n\nFor more information, refer to [default reversal processing codes](https://developers.pismo.io/pismo-docs/docs/processing-codes-and-transaction-types#default-reversal-processing-codes).\n", "example": "578739" }, "ReversalProcessingCode": { "type": "string", "minLength": 2, "maxLength": 6, "description": "Reversal processing code. Processing code for cancellation. Used in transactions and accounting flow to post the correct entries related to cancellation. \n\nEvery `AUTHORIZATION` processing code is **REQUIRED** to have a reversal and a partial reversal processing code. If a partial code isn't provided, a default one is assigned based on `balance_impact`. \n\nThe reversal processing code can either currently exist or not. If it exists, its `balance_impact` must be the opposite of the main processing code and its type must be `REVERSAL`.\n\nFor more information, refer to [default reversal processing codes](https://developers.pismo.io/pismo-docs/docs/processing-codes-and-transaction-types#default-reversal-processing-codes).\n", "example": "578739" }, "Standard": { "type": "boolean", "description": "Is this a standard processing code? A standard processing code, as opposed to a custom one, is one that is pre-defined for every organization on the Pismo platform. \n\nFor more information, refer to [Standard processing codes](https://developers.pismo.io/pismo-docs/docs/processing-codes-and-transaction-types#standard-processing-codes). \n", "example": true }, "Status": { "type": "string", "description": "Processing code status:\n * `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.\n\n * `SUCCESS` - Required configurations done\n", "enum": [ "SUCCESS", "PENDING" ], "example": "SUCCESS" }, "Tags": { "type": "array", "description": "Processing code tags. These tags apply **ONLY** to `AUTHORIZATION` type processing codes. You cannot add tags to reverse processing codes as they may be associated with more than one authorization processing code.\n", "items": { "type": "string", "description": "Processing code tag.", "enum": [ "GLOBAL", "BRAZIL", "ARGENTINA", "INDIA", "NETWORK", "VISA", "MASTERCARD", "ELO", "RUPAY", "TECBAN", "UPI", "PIX", "FPS", "TRANSACTION_BANKING", "BNPL", "LENDING", "DEPRECATED" ], "example": "INDIA" } }, "TranslatedLanguage": { "type": "string", "description": "Translation language. \n\nFor 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.\n", "example": "en-US" }, "Translations": { "type": "array", "description": "Processing code descriptions translation in different languages", "items": { "type": "object", "properties": { "language": { "$ref": "#/components/schemas/TranslatedLanguage" }, "description": { "type": "string", "maxLength": 50, "description": "Translated description" } } } }, "HTTPError": { "type": "object", "description": "Code and error message.", "properties": { "code": { "type": "string", "description": "HTTP error code" }, "message": { "type": "string", "description": "HTTP error message" } } } }, "securitySchemes": { "S2SAuthentication": { "type": "http", "scheme": "bearer", "description": "All requests must be previously authenticated with an account token" } } }, "paths": { "/orgs-operation/v1/processing-codes": { "get": { "summary": "List processing codes", "description": "Get an organization's processing codes with filtering options.\n", "operationId": "ProcessingCodeList", "tags": [ "Processing codes" ], "parameters": [ { "$ref": "#/components/parameters/GetProcessingCodesListCursorQuery" }, { "$ref": "#/components/parameters/GetProcessingCodesListLimit" } ], "responses": { "200": { "description": "Sucessful response with list of processing codes", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/GetProcessingCodesResponse" } } } }, "400": { "description": "Bad request error.", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/HTTPError" } } } } } } } } } ```