Changelog
Sub-processorsAbout PismoContact us
Back to All

5 June 2026

about 1 month ago by [email protected]

Changes between 1 May and 5 June 2026

General

New

An llms.txt file was added to the Pismo Developers Portal to help large language models (LLMs) parse and understand Pismo documentation. The file provides a machine‑readable, Markdown‑based index of all portal content, stays in sync with documentation updates, and offers direct access to Markdown versions of all site pages. For more information, refer to Using LLMs with the Pismo Developers Portal.

Docs

The Pismo API reference overview guide was moved to the new Get started section on the APIs tab, and was renamed to Get started with Pismo APIs.

Control Center

Docs

The Holidays guide is now available with instructions for managing bank holiday calendars in Control Center, including calendar creation, hierarchy, import/export, and holiday configuration.

Core banking

Docs

The new Bankers Automated Clearing System (BACS) guide is now available to accompany the new BACS API endpoints.

Instant payments

New

The new Return FPS payment [beta] endpoint is now available in beta release.

Accounting

Docs

In the Create accounting entry endpoint, the example for the event_date field was updated to be in the correct YYYY-MM-DD format and the description of the tracking_id field was updated to clarify its format as UUID and to include a generator link.

Accounts

Docs

In the Account status table, the CANCELLED row was updated to explicitly state that you can change the status in Control Center.

Docs

In the Get account endpoint, the show_children field description was updated to indicate that the response lists up to 3 levels of descendant account numbers (children, grandchildren, and great-grandchildren) in the children array.

Authentication

Docs

The description for Get OpenID access token endpoint was updated to clearly explain the role of the JSON Web Token (JWT) and to include a link to the Authentication with OpenID Connect guide.

Client webhooks

Docs

The Zero balance validations webhook section of the Client webhooks guide was updated to address the following.

  • The requirement descriptions for request fields authorization_code and incoming_authorization_code were updated for clarification.
  • The partial_approval_info object and its fields local_amount, settlement_amount, and cardholder_amount, were added to the response fields list to address insufficient fund declines at point-of-sale when the available Visa card or account balance is not sufficient to approve a transaction in full.
  • The original_network_data object is now properly marked as required for both Zero balance and Full balance.

Flex controls

Updated

In the Flex controls API, the currency_code value was removed from the list of options in the conditions.attributes field.

General

Docs

The Get started with Ask AI guide was moved to the Resources section.

Docs

The following note was added to the description of the metadata field in the Transaction banking, Overdraft, Lending, and Statements APIs.

Note: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to Get started with Pismo APIs.`

Migrations

Docs

Balance control and Accruals sections were added to the Migrations guide. These sections detail how to ensure account balances are established correctly, as well as ensure interest and other accrued charges are transferred correctly on to the Pismo platform during the migration process.

Docs

In the Migrate PCI cards endpoint, pin_type and pin_validation_data field descriptions were updated to reflect accepted enum values. The encrypted_pin field was also revised for clarity and adherence to Pismo platform standards.

Docs

The summary for the Migrate balances endpoint was updated to explicitly state the configuration requirements when migrating balances.

Payments

Updated

In the Request authorization endpoint, the validation_rules field is now available. You can set validation_rules to control the rules in this flow, such as disabling a rule, changing the response code and denial code, and forcing a rule. The Define validation rules of the Configure payment methods guide was updated accordingly also.

Programs

Docs

The unused and incorrect field, currency_numeric_code, was removed from the Update program endpoint. The currency defined for a program was never intended to be modifiable, as it could cause problems with the program.

Rates and fees

Docs

The Exchange rates guide was updated to better explain exchange rate configuration and retention behavior and to include a description of rates behavior in a multi-currency setup (MCS).

Docs

The sample for Bulk upload of exchange rates in the Exchange rates in Control Center guide was updated to clarify that both periods and commas work for exchange rates and fees, regardless of the specified currency codes.

Security

Docs

The Authentication with OpenID Connect guide was updated with the following clarifying edits.

  • A reference and link to the Get OpenID access token endpoint was added to the initial guide summary.
  • The definition for the claim tenant_id was updated to clarify that the tenant_id claim is different than the Org ID.
  • The definition and example for the claim pismo was updated to indicate that you can add more than one permission group at a time.

Docs

The Important security details section of the Identity connectivity with mTLS guide was rewritten for clarification of security for API communications.

Docs

The Request parameter list for Grant type in the Authentication with OAuth2 guide was updated to list the parameter client_secret (it was previously incorrectly listed as client_secret_string).

Setup

New

New sections and endpoints were added to Platform setup - Holidays: Holiday calendar and Holiday calendar data. The endpoints in these sections are a replacement for endpoints in two sections in the same API: Holidays and Holidays V2 - transaction banking. These two sections and their endpoints are now deprecated. Endpoints under Holidays (found under Platform setup – Organizations) were also deprecated and replaced with endpoints in the two new sections.

Docs

A new section for Holidays and admin divisions was added to the API endpoint deprecation and removal schedule to detail deprecated endpoints and their replacements.

Docs

The table in Program parameters was updated to use an advanced format. Some of the new features and changes include:

  • The table can now be sorted by any column.
  • The filter textbox enables you to search for a text value anywhere in the table.
  • Pagination is enabled with page size set to 30 rows.
  • You can export the table to a CSV file.
  • The column header “Required?” has been changed to “Constraints”. This is meant to better reflect the purpose of the column, which is to indicate how the program type constrains the use of the parameters.
  • Other minor changes have been made to the table and the rest of the page.

Docs

The table in Account parameters was updated to use an advanced format. Some of the new features and changes include:

  • The table can now be sorted by any column.
  • The filter textbox enables you to search for a text value anywhere in the table.
  • You can export the table to a CSV file.
  • The column header “Required?” has been changed to “Constraints”. This is meant to better reflect the purpose of the column, which is to indicate how the program type constrains the use of the parameters.
  • Other minor changes have been made to the table and the rest of the page.

Support

Docs

The Comments column of the Request types and common fields guide was updated to remove the reference that did not link to any additional content and caused confusion. The column now presents the information without unnecessary or misleading text.

Docs

The "Sandbox" request type was updated to "Non-production environment" across the following guides.

Events

Updated

The new maturity_period and detach_datetime fields were added to the following events to provide additional details about account and product attachments.

Updated

The description of the Installment advanced event was updated to list the endpoints that generate it.

Updated

References to the cycle field were removed from the Statement migration started and Statement migration completed events. These events are only a receipt/acknowledgement and do not define the invoice cycle, and therefore were removed to avoid misinterpretation of the event.

Updated

The status field was added as a required field to the Account migration started and Account migration completed events. This update was to address the mandatory field missing from the payload.

Banking operations

New

Two new endpoints are introduced to enable clients to update payout accounts for deposit and savings accounts.

Updated

In the deposit_configs field of the Attach deposit to account endpoint request payload and Get account attachment response payload, the following fields were replaced by maturity_period.

  • maturity_date_days
  • calendar_maturity_date

Updated

The end_date field is introduced to the deposit product and is used as a validation point for rollover rules. The deposit product creation endpoint currently supports configuring maturity and rollover behavior but does not enforce any boundary tied to an end date. This new field is added to the following endpoints.

Updated

The new legal_holds field was added to the response payload of the following endpoints to indicate the portion of an account balance under legal holds and unavailable for transactions.

Updated

In the maturity_instructions object of the Create deposit product and Get deposit product endpoints, the NO_ACTION attribute of the principal object in the 200 response payloads is now replaced by PAY, which indicates the principal amount paid to the payout account.

Instant payments

New

The new Confirmation of payee (CoP) endpoint was added to the Faster Payments API. CoP allows payers to check that the name they have for the intended recipient matches the actual name on the recipient's account, reducing the risk of fraud and misdirected payments. This endpoint must be called before calling Send Faster Payment. The new Confirmation of payee section was also added to the Faster Payments guide. The two CoP events were edited for clarity and standards.

New

The new Resend payment order endpoint is now available in the Automatic Pix API. You can use this endpoint when:

  • The payer's PSP did not accept the payment order and the status is REJECTED or EXPIRED,
  • When the payment order was accepted, but the Pix transaction was not found by the due date, with status CANCELLING.

In these cases, the payment order can be resent to trigger a new attempt to process the payment.

Updated

In the Automatic Pix API, the reason_code has a new cancellation reason code: OTHS. This reason indicates that the cancellation was requested by either the payer’s participant or the receiver’s participant for other reasons not specified in the previous categories.

Docs

The “Instant payments - Automatic Pix” API has been divided into two sections - Automatic Pix and Automatic Pix data. In the CRUD (Create, Read, Update, Delete) scheme of things, the first section contains all the CUD (POST, PUT, PATCH, DELETE) endpoints and the data section contains all the R (GET) endpoints.

Payment rails

New

The new Reverse BACS direct credit outbound payment endpoint is now available in the Bankers' Automated Clearing System (BACS) API. This endpoint can be called to reverse a BACS direct credit outbound payment that is on hold.

Updated

The URL path was updated in the Release BACS inbound transaction [beta] and Cancel BACS inbound transaction [beta] endpoints.

Transaction banking

New

The new Simulate penalty endpoint is now available. This endpoint lets clients simulate the penalty applied to a specified withdrawal on a given date.

Docs

The Account balance definitions for transaction banking previously listed the book balance formula as credit_balance - debit_balance + earmark_balance. This was now corrected to credit_balance - debit_balance.

Card network integration

Updated

The Visa denial code for custom code RED (operation_not_allowed_by_rules) was changed from 78to 9G. This change is reflected in the Validation codes for authorization events guide.

Docs

The Consolidated file and events section of the Clearing/Base II guide was updated to better explain that all settlement-related information is delivered through clearing events and there are no actual settlement events.

Cards

New

The following new card reissue endpoints are now available.

Cards on file

Updated

The unused Get card validation amount endpoint was removed.

Disputes

Updated

The names of version 1 of the Create fraud report and Update fraud report endpoints were changed to Create dispute fraud report and Update dispute fraud report, respectively. These name changes resolve duplicate endpoint names within the Disputes API.

Statements

Updated

The 423 - Account Locked HTTP status code response was added to the Create payment agreement simulation endpoint.

Docs

The description for the Update scheduled charge endpoint was updated.

Docs

The Configuring accrual rates guide was broken up into:

The Using configurable entities section of the Full balance credit program guide was rewritten and shortened using links to the new guides.

Docs

The following endpoints were renamed and their descriptions were updated. The original names were confusing and did not clearly differentiate the endpoints from other endpoints with similar functionality.

Docs

The path parameter PaymentAgreementId was changed to advancementId for the following endpoints. The original parameter was incorrect.

Docs

The table in the Multivalue program parameters guide was updated to use an advanced format.

  • The table can now be sorted by any column.
  • The filter textbox enables you to search for a text value anywhere in the table.
  • You can export the table to a CSV file.
  • The “Applies to” column has been moved to the right of the “Name” column.

Docs

The 423 - Account Locked HTTP status code response was added to the Create payment agreement simulation endpoint.

Deprecated

The deprecated endpoint Get program future calendars (GET /statements-v2/v1/calendars) was decommissioned and removed from the API reference. An entry for it was added to API endpoints removed.

Tokenization

New

The new tokenization endpoint Bind Visa device and token is now available. Device binding establishes that a specific device belongs to a specific cardholder. Once bound, the device can be trusted more in future transactions. An issuer can use this endpoint to update the status of a specific device linked to a token.

Lending

New

The following endpoints are now available in beta release for lending to enable prepayment simulation and prepayment records.

Updated

The following endpoints were updated to remove program_id from any loan adjustment information to avoid confusion and mismatched program configuration IDs.

Updated

The following endpoints were updated to enable you to set or get a grace period with the grace_period_days field. When set, the loan installment status goes to IN_GRACE_PERIOD instead of PAST_DUE when the deadline has passed for repayment.

Updated

You can now set, update, or remove a minimum total payment with minimum_total_payment on the following endpoints.

Updated

You can now indicate the minimum total payment difference with minimum_total_payment_delta on the Register repayment [beta] endpoint.

Merchants

Updated

The following new fields were added to the Get merchant transaction endpoint. These new fields allow you to see total discount and itemized discount breakdowns within the Seller management - Merchants API.

  • discount_amount
  • discount_details

Control Center

Docs

In the Change account status section:

  • An info notice was added, stating that you can reactivate a canceled account by changing its status back to Active.
  • The link at the bottom of the section was updated to point to the Accounts guide.

Docs

The OpenId Connect authentication guide for Control Center was updated to clearly indicate that Admin access is needed to view and edit OpenID authentication configurations.

Docs

Documentation was clarified that Pismo does not create and manage Control Center users. Rather, the customer’s Control Center administrators are responsible for these tasks. The following guides were updated:

Docs

The Exchange rates for Control Center guide was updated to include a note in the Bulk upload exchange rates section that it essential to include identity pairs when your setup is multi-currency.