2022-10-03 changelog

AccountsAccountingConsoleDocumentationExchange ratesMigrationsFlex controlsProcessing codesSecurity

Highlights

πŸ“ New payments configuration API

A new Payments configurations API allows you to configure how the Pismo platform processes operations in the payments flows. To support new processing codes configurations, the following new endpoints are now available also:

For details, see the Payments configurations guide.

πŸ“ New parameter to enable/disable account creation per program

A new program parameter ALLOW_ACCOUNTS_CREATION is now available in the Pismo Console. It allows you to enable or disable the accounts creation per program.

πŸ“ Changed customClaims field name

In Creating a JWT, changed claims field name to customClaims.

Documentation updates

πŸ“ New processing codes documentation

A new Processing codes and transaction types guide explains how the Pismo platform handles the processing codes for transaction types and lists standard processing codes by program types.

πŸ“ New accounting events guide

A new Accounting events guide lists the accounting events that can be generated by financial operations of the corresponding transaction type.

πŸ“ Updated API reference for standards

The following API reference sections were updated to improve the descriptions and to bring them in line with the new standards:

πŸ“ Added endpoints to migrations API

The following migration endpoints were added to the API Reference:

πŸ“ Endpoints that require an account-specific token

The PUT /accounts/v2/customers/{customerId} endpoint was added to the list of endpoints that require an account-specific token.

πŸ“ Marked deprecated exchange rates endpoints

The following old exchange rates endpoints are now marked as deprecated:

πŸ“ Updates to clearing documentation

In the Clearing/base II workflow, updated information how the platform processes the settlement files for Mastercard and Visa.

πŸ“ Updates to core objects

Updated the Basic component structure table to reorganize object hierarchy and clarify account and customer descriptions.

πŸ“ Requirement updates to personal object

Updated requirement specifications for the name, printed_name, and social_name fields in the personal object on the following endpoints:

πŸ“Added required accounting amount field

In Create accounting entry, added the required amount field.

πŸ“Removed deprecated spending limits API

The deprecated spending limits endpoints are now removed from the API reference. For any new development of flexible transaction controls, refer to the flex controls API instead.