APIs
Sub-processorsAbout PismoContact us

Create processing code

post
https://sandbox.pismolabs.io/orgs-operation/v1/processing-codes

Create a processing code for an organization.

Processing codes identify financial operations on the Pismo platform. For example, 00 is a purchase, 01 is a withdrawal, and so on.

Processing codes need to be mapped to transaction types to create a transaction flow.

This endpoint creates an AUTHORIZATION type processing code and generates a Orgs operation created event.

Notes:

  • The prefix PSM is reserved at Pismo platform, customers are not allowed to use this prefix when creating custom processing codes . Not all standard processing codes have the PSMprefix. There are codes created before this standard and are kept for backward compatibility. New ones, however, will always have this prefix.
  • On the Pismo platform, 2-digit processing codes are reserved and used only for network processing. Because of this, customers are not allowed to have 2-digit custom processing codes.
  • When a new standard processing code is created, it is replicated and configured to all platform organizations, no action is required on your part.
  • This endpoint generates a Orgs operation created event.

For more information, refer to Processing codes.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
length between 3 and 6

Processing code ID

The following applies to this field:

  • It must have between 3 and 6 characters.
  • Only letters and numbers are allowed.
  • Must be unique and not already exist in the org's database
  • Cannot start with the prefix “PSM”, this is reserved for Pismo platform processing codes.
integer
enum
required

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
Allowed:
string
required
length ≤ 50

Processing code description

string
required
length between 2 and 6

Reversal processing code. Processing code for cancellation. Used in transactions and accounting flow to post the correct entries related to cancellation.

Every 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.

The 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.

For more information, refer to default reversal processing codes.

string
length ≤ 50

Reversal description. If not passed, it is automatically set to "REV " plus the description field. For example, if description is "Purchase", the reversal description will be "REV Purchase".

string

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.

Every 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.

For more information, refer to default reversal processing codes.

string
length ≤ 50

Partial reversal description. REQUIRED if partial_reversal_processing_code does not exist.

tags
array of strings

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.

tags
translations
array of objects
translations
Responses

Updated 21 days ago

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json

Updated 21 days ago