Changelog
Sub-processorsAbout PismoContact us
Back to All

6 March 2026

28 days ago by [email protected]

Changes between 6 February and 6 March 2026

General

Docs

The new Get started with the Pismo Developers Portal guide is now available. It replaces the previous Welcome to Pismo guide and introduces the following improvements.

  • Improved introductory content to better orient new users to the Pismo Developers Portal
  • Restructured content to highlight the four main areas of the Developers Portal and their use cases
  • Additional visual aids to support written content

On the landing page, the Get started with card issuing feature card was replaced with a New to the Developers Portal? feature card to highlight the new guide.

Core platform - Account parameters

New

The new guide Account parameters is now available to list available account parameters, which are configurable properties that manage how an account is set up and how it behaves. All account parameters have corresponding program parameters. Account parameters give you the option of configuring the same properties differently for specific accounts. The link to the new guide was added to the account parameters endpoints.

Core platform - Program limits

New

The Pismo platform now allows you to control the total granted limit distributed across all accounts within a program. This feature ensures that the program-level global limit is enforced during operations that increase or decrease limit values, such as account creation, limit updates, or program transfers.

The following new endpoints support this functionality.

Refer to the Program limits guide for details.

Core banking - Transaction banking

Docs

The following new guides are now available.

Card issuing - Reconciliation

New

The new endpoint Perform clearing reconciliation is now available. If a problem is encountered during the clearing process for Clearing/Base II authorization events, you can use this endpoint to reconcile the clearing, taking over the reprocessing of messages in the Dead Letter Queue (DLQ), assuming the responsibility to reconcile unprocessed clearing messages. All messages that have been sent to the DLQ can be reconciled through this endpoint. Clearing reconciliation is available for Visa and Mastercard only. Clearing reconciliation details were added to the updated Clearing / Base II and the Authorization events guides.

Card issuing - Statements

New

The new endpoint List calendars is now available. Use this endpoint to list the calendars for a program, optionally filtering on due date, program calendar strategy ID, or division ID.

Updated

The overridden_amount_due body parameter is now available in the Create payment agreement simulation endpoint.

Updated

In the List transaction balances endpoint, the following updates were made.

  • The minimum attribute of 1 was added to the accountID path parameter.
  • The transactionTypeId path parameter was changed to an array of int64s. It was incorrectly listed as just an int64 previously.

Updated

A new program parameter, Ignore grace days on pending accruals reversal for revolving accounts, was added to the Program parameters guide.

Docs

The description of the status body parameter in the Get delinquent account closure process information endpoint was updated in the following ways.

  • A description was added for every possible value of the enum.
  • CREDIT_SEPARATED_TRANSACTION_REQUESTED, which was missing from the enum list, was added.

Docs

A row for Ignore grace days on pending accruals reversal for revolving accounts was added to the table in the Calculating interest accruals guide.

Docs

The description of the period_to_calculate body parameter was updated in the Configure program accrual rates and Configure account accrual rates endpoints.

Docs

The List transaction types endpoint was incorrectly marked as deprecated and was updated to remove the DEPRECATED tag. It is scheduled to be deprecated, but it hasn’t been deprecated yet. The note in the endpoint description was updated to explain that it will be deprecated. The first line of the description was also rewritten to better conform to documentation standards.

Docs

The Credit liquidation and Managing due date, cycle closing date, and additional grace periods guides were rewritten to clarify the grace days logic.

Docs

The capitalization of a body parameter in the List statements v3 was corrected from presenttoPast to presentToPast.

Control Center

Updated

Processing codes and transaction types were updated in Control Center to align with the updated Processing code API. With this change, you can now do more with processing codes and transaction types with Control Center, including:

  • Link authorization, reversal, and partial reversal processing codes
  • Replace assigned reversal processing codes
  • Edit processing code and transaction type names
  • Adjust transaction flows
  • Filter processing codes by any field

The Create processing codes and transaction types guide and the Add a transaction type to an existing processing code guide were updated to reflect the new functionality.

Lending

Docs

The new guide Loan product setup is now available. It provides information on setting up loan products on the Pismo platform, covering required product attributes and configuration needed to support loan simulation, booking, disbursement, and lifecycle management via the lending APIs.

Docs

The new guide Loan simulation is now available. It explains how to create draft loan simulations on the Pismo platform, enabling lenders to model loan terms and repayment schedules before finalizing a loan. The guide shows how draft simulations support customer review and iteration prior to booking and disbursement.

Accounts

Docs

In the accounts endpoints, person object, the document_issued_date’s format was incorrectly listed as being “yyyy-mm-dd” when it should have been “dd/mm/yyyy”.

Docs

In the Get account endpoint response, the misnamed collection_status field has been corrected to collections_status.

Client webhooks

Docs

The descriptions for the request fields for Zero balance validations webhook were updated to provide clarifying details.

Docs

The Client webhooks for VCAS guide was updated to include an overview flow diagram and updated overview text to help clarify the Visa Consumer Authentication Service (VCAS) as used within the Pismo platform.

General

Docs

The abbreviation format for Not Applicable (N/A) was standardized and explicitly defined in the following guides to improve accessibility.

Migrations

Docs

The Migrate transactions field descriptions have been updated for clarity and order.

Payments

Updated

In the Authorization validation rules for platform operations guide, the new RATES_LOGICAL_ERROR reason was added to the Operation amount calculation rule.

Rates and fees

Docs

The new section Use Merchant Category Codes to allow or disallow over-limits was added to the Over-limit fees guide.

Security

Docs

A new section, PGP encryption for card embossing, was added to the Pismo platform security guide to define and describe the use of Pretty Good Privacy (PGP) encryption for card embossing.

Setup

Docs

The Program parameters guide was updated for documentation standards. One note was updated to better explain account parameters and a link was added to the new Account parameters guide.

Docs

The value in the Category column of the Fine amount for late payment program parameter was updated in Program parameters. It was incorrectly listed as "Rate". It is now correctly listed as "Parameter".

Transactions

Updated

In the Update transaction flow endpoint, the following responses are now available.

  • Status code 400 - Error WTRC05003 - Transaction type doesn't exist.
  • Status code 409 - Error ETRC04004 - The provided transaction type is already configured for the processing code.
  • Status code 409 - Error ETRC04005 - The provided amount type conflicts with an existing configured amount type for the processing code. Please select either Principal or Contract.

Docs

In the List transactions endpoint, the following 400 response examples for error WTRC00001 were added:

  • Number of latest transactions should not have another filter
  • Number of latest transactions should be an integer
  • Invalid range for number of latest transactions
  • Invalid authorization type
  • Account is required when querying by card ID
  • Event date start not provided
  • Invalid event date start format
  • Invalid event date end format
  • Invalid time range

Events

New

The following events were added to simplify notifications for processing interest-bearing accounts credit accruals.

For deposit products:

For savings account products:

Instant payments

New

The following new Faster Payment System (UK) endpoints are now available in beta release.

Updated

The following instant payment API/sections and their endpoints that were previously in beta release are now available in regular release.

New

The following new Pix Dict API funds recovery endpoints are now available.

Docs

The new Suspense transaction flow section was added to the Faster Payment System (UK) guide that details the flow for a transaction that fails an anti-fraud check and is put on hold.

Updated

Interactive flow for Pix DICT funds recovery endpoints is no longer supported. Only the Automatic flow, where the Diretório de Identificadores de Contas Transacionais (DICT)—a national Pix key registry and database—automatically manages tracking and blocking using a standard algorithm is now supported. The flow_type parameter, which specified interactive or automatic, was removed from the Create funds recovery endpoint. The Create tracking graph and Block funds recovery endpoints were removed.

For the Get tracking graph endpoint, the following changes were made.

  • Query parameter graphId has been removed
  • The fundsRecoveryId query parameter was renamed to funds_recovery_id
  • A new created_at field was added to the response
  • The graph_id parameter was removed from the response
  • Fields created_at in the person and account objects are now optional
  • The hop field was removed from the transaction object

Transaction banking

Updated

As part of the migration to transaction banking with a single balance, the PAY maturity instruction was removed so that deposit products accept only ROLLOVER or NULL to support rollover behavior or no action at maturity. All PAY‑related functionality was fully removed. This effort impacts the maturity_instructions object of the following endpoints.

Updated

The following endpoints are now available in general release and the [beta] tag was removed from them.

Deprecated

The endpoint Get AES key (GET /corporate/v1/bulk-payments/encryption-keys/{bulkId}) was decommissioned.

3DS authentication

Docs

The path for the Send pre-authentication info endpoint was updated to remove a duplicated section. It now correctly displays the path: https://api-sandbox.pismolabs.io/3ds-acs/v1/preauthenticate.

Card network integration

Docs

The Authorization validation rules for card network operations guide and the Rule list guide were updated to correctly reflect that flex controls validation is available for both Full balance and Zero balance integrations.

Docs

The Visa Consumer Authentication Service (VCAS) guide was updated to include additional overview information and flow diagrams for each of the use cases for VCAS as used within the Pismo platform.

Docs

The Simulate authorization endpoint was updated to mention the ability to cancel a simulation in the test environment and examples for Create authorization and Cancel authorization were updated for clarification. The processing_julian_date field was corrected to properly show the format as YYDDD.

Docs

The List of rules table in the Authorization validation rules for card network operations guide now correctly reflects that Flex controls are valid for Zero balance, with limitations. A note was added to the Flex controls validation section of the Rule list guide to explain how Flex controls work with Zero balance.

Cards

New

A new Cards API section (Migration) and two new endpoints are now available in beta release.

  • Migrate card to different program - You can use this endpoint to transfer a card to a different program. Prior to this, you could only migrate between programs at the account level. In other words, the issuer can migrate an account from program A to program B, but cards cannot. Reissues are required to ensure the new card has the same program as the account.
  • Migrate card mode - Migrate a card's secondary mode (debit or credit) to a new program. If a combination card is initially created with a credit account (has a CREDIT mode), it gets migrated when the Migrate card to different program endpoint is called. However, if you wish to migrate the debit (secondary) mode, you need to call this endpoint.

Updated

The template_id field was added to the 200 and 201 responses for the Create card endpoint. Templates are used to implement the BIN override feature.

Updated

The Synchronize offline pin endpoint no longer requires creating a Jira ticket to use.

Cards management

Docs

A new section was added to the Embossing rules in the Physical card embossing guide to describe the use of Pretty Good Privacy (PGP) encryption for card embossing.

Full balance credit program

Docs

The Program transaction types section of the Full balance credit program guide was updated to add clarity on how program transaction types are mapped to program transaction categories.

Statements

Updated

The omitId query parameter was added to the Get interest accrual summary endpoint.

Updated

A deprecated endpoint for the Statements API was added to the API endpoint deprecation and removal schedule.

  • Deprecated endpoint: GET /statements/v1/accounts/{accountId}/total-due
  • Replacement endpoint: Get account total due

Docs

The list of enums for the status field in the 202 response for the Create installment advancement endpoint was updated. The original list was incorrect.

Docs

All the guides under Understanding statements were reorganized to improve the ordering. Fixed due date calendars and Fixed cycle closing calendar management strategy were moved underneath Calendar management strategies.

Docs

(V2) was removed from the names of the following endpoints.

The names of the following endpoints were updated with the word (outdated) and notes were added in the endpoint descriptions explaining recommendation that the above endpoints be used instead.

Marketplace

Updated

An additional fees field was added to the following creditor operations endpoints.

Docs

The following outdated and unused endpoints relating to head branch configurations were removed.

  • Delete merchant branches
  • Delete merchant branch relationships

The following corresponding events relating to head branch configurations were also removed.

  • Merchant head branch relationship disabled
  • Merchant head branch relationship created

Transactions

Updated

The new currency_code field was added to the Create merchant transaction and Cancel merchant transaction endpoints. This field represents the currency of a transaction with an alphabetic or numeric string.

Updated

Corrected description for a successful call response in Create merchant transaction and Cancel merchant transaction endpoints.

Docs

The definitions field description was revised for clarity and accuracy within the Create split request endpoint.

Control Center

New

A new user role, API keys approver (controlc-api-approver), was added to Control Center. This new role is listed and defined in the User permissions and roles guide and the Get started with SSO for Control Center guide.

Docs

The Access keys for basic authentication guide was updated to correctly identify the basic server-to-server key pair as server_key and server_secret, with updated descriptions of each key for clarification.