Changelog
Sub-processorsAbout PismoContact us
Back to All

6 November 2026

about 1 month ago by [email protected]

Changes between 2 October and 6 November 2026

Core platform - Transactions

Docs

The following new guides are now available.

Data and reporting

Docs

A new guide, Events fanout service, is now available. The guide explains how the Fanout service supports reliable event delivery. It also covers delivery guarantees, retry and recovery behavior, connector-specific behavior, timeout handling, and circuit breaker and failure recovery mechanisms.

Core banking - Payment rails

New

There are 3 new Bankers Automated Clearing System (BACS) endpoints for Direct Debit indemnity claims that allow a customer's bank to immediately refund them for an erroneous, unauthorized, or non-compliant Direct Debit payment, and then automatically recover that money from the collecting business (the Service User). These new endpoints are available in beta release.

Card issuing - Cards

New

The Pismo platform now supports card renewal functionality. Card renewal enables an issuer to update an existing card's expiration date, keeping the same card while assigning a new expiration date. Renewal behavior differs depending on the card type.

The new Renew card expiration date endpoint is now available to renew a card. To go with this, there is a new “Cards issing - Cards > Card renewal” API section.

A new Card renewal guide describes how card renewal works for virtual and physical cards.

Card issuing - Disputes

New

The following new disputes setup endpoints are now available. The Create setup endpoint replaces requesting dispute access through the service desk.

Lending

Docs

A new guide, Cancel loans, is now available. The guide provides detailed instructions on canceling single loans, canceling multiple loans in bulk, and how to configure automatic loan cancellation when an account defaults on a loan and optionally when an account is non-performant for their credit card payments.

Seller management

Docs

A new guide, Creditor Operations, is now available. The guide provides guidance for understanding, configuring, and managing creditor operations.

Resources

Docs

A new guide, Access Pismo event schemas on GitHub, is now available. The guide gives pointers to the public GitHub repository where a new folder contains the event JSON schema files for reference.

Accounting

Updated

Credit transaction flow is now supported by accounting scripts v2. Previously, it was available only in accounting scripts v1. Refer to Supported flows for details.

Docs

In the List accounting entry types endpoint, the response now correctly lists the responsible field.

Docs

Multiple string fields throughout the Accounting API were updated to use maxLength instead of maximum to specify maximum length. These include account, credit_cost, credit_org, debit_cost, debit_org, description, processing_code, properties, tracking_id, type, reason, and responsible fields.

In addition, minLength was added to the accounting entry type description, reason, and responsible fields.

Client webhooks

Docs

The Visa example of the original_network_data field was corrected in the Client webhooks guide.

General

Updated

The search functionality on the Developers Portal was updated to search through all URLs and fields.

Migrations

Updated

The Migrate tokens endpoint was updated to add the devices_binding field. This update enhances token-related event data by explicitly identifying whether a token is device-bound, enabling you to distinguish between device-bound and non-device-bound token implementations.

Docs

The Migrate transactions endpoint was updated to increase the maximum length of the soft_descriptor field from 25 to 100 characters. The increased field length provides greater flexibility for transaction descriptors, allowing more detailed merchant and installment information to be represented without truncation.

Deprecated

The Create reversal transaction endpoint (deprecated) was replaced by the Cancel merchant transaction endpoint. Use the Cancel merchant transaction endpoint to cancel a previously created merchant transaction.

Payments

Update

In the Platform authorization created event, the new anti_fraud_metadata field is now available.

Programs

Docs

The API documentation for the synchronous Copy program endpoint was corrected. Previously, it erroneously stated that a successful operation returned "200 OK". It now states that a successful copy returns "201 Created", which is what the service has always returned.

Rates and fees

Updated

In the Platform setup - Rates and fees API, the calculation_method, interest_rate, and fees fields were properly relocated to the top level of the schema and the previously missing precedence field was added.

Setup

Update

The List holiday calendars endpoint was updated to return 400 Bad request for any invalid values passed to sort_by and sort_order, and the List holidays endpoint was updated to return 400 Bad request for any invalid values passed to orderBy.

Update

The Create holiday calendar was updated to always include working_days in the response. If you create a calendar without working_days, or pass an empty array ([]), the response returns the default working days ([1, 2, 3, 4, 5]). Previously, the response left the field out or returned [], even though the calendar was saved with Monday to Friday as working days.

Docs

AWS-Jakarta was added to the Pismo platform sub-processors guide.

Docs

The working_days field description was updated to correctly include Sunday (0) as an allowed value. It now shows the full range the API has always accepted. If you don't pass working_days when you create a calendar, it defaults to [1, 2, 3, 4, 5] (Monday to Friday). The following endpoints are affected.

Docs

Documentation for the Get program V2 endpoint was updated as follows to correctly describe and align with the API behavior (no changes were made to the API functionality).

  • The base_program_id field now allows null in the response.
  • The description field in the brand object was renamed to name in the response.

Docs

Documentation for the List programs endpoint was updated as follows to correctly describe and align with the API behavior (no changes were made to the API functionality).

  • The base_program_id field now allows null in the response.
  • The cycle_closing and holiday_calendar_id fields were added to the response.

Docs

The reversal_description field description for the Create processing code endpoint was updated. It now describes the truncation behavior in cases where the description field’s description is used.

Docs

The endpoint descriptions for the Holidays (deprecated) and Holidays v2 - Transaction banking (deprecated) endpoints were updated to remove details about specific deprecation dates to adhere to Pismo documentation standards. For more information about endpoint deprecation, refer to the API endpoint deprecation and removal schedule.

Docs

The endpoint descriptions for the Administrative divisions (deprecated) and Administrative divisions V2 (deprecated) endpoints were updated to remove details about specific deprecation dates to adhere to Pismo documentation standards. For more information about endpoint deprecation, refer to the API endpoint deprecation and removal schedule.

Support

Docs

The Incident Operational Level Agreement (OLA) in the Request types and common fields guide was updated to reduce the mitigation time for critical incidents from 4 hours to 2 hours.

Transactions

Docs

Field descriptions for the eventDateStart and eventDateEnd fields on the following endpoints were updated to specify correct date formats.

Docs

Maximum length for the custom_code and processing_code fields in the transaction flows endpoints are now correctly specified by maxLength instead of maximum since these are string fields.

Docs

In the following endpoints, the items field is now correctly defined as an array of objects.

Docs

In the List transaction types endpoint, the description of the orderBy field was enhanced to specify the default value and all accepted values.

Events

Updated

In the Account migrations started v2 event, the max_limit field was added to the account_incoming event schema to document the maximum limit provided when migrating an account.

Updated

In the Account go-live completed event, the account_go_live_outgoing event schema was updated to no longer accept CREATE as a valid operation. The event now supports only ACTIVATION and UPDATE operations, as expected.

Docs

The following lending events are not generating the authorizations_postings object so the documentation was updated to reflect the actual output.

Reports

Updated

Two new fields, DischargeOrder and PaymentHierarchy_ID, were added to the table in Discharge tracking report files.

Docs

"Format: Parquet" was added to the bullet point list in the first paragraph of each guide under Base scheduled reports.

Banking operations

Updated

The title of the Penalties for CD accounts guide was renamed to Penalties and taxes for CD accounts. In addition, a new Taxes section in this guide now explains how to configure tax withholding.

Updated

The field descriptions and calculation formula in the Simulate penalty endpoint were expanded to provide additional context and calculation details. The following information was added.

  • gross_amount—When a capitalization total record is available, this value equals the sum of the principal balance and the total interest accrued. Formula = withdrawal_amount + interest_earned_amount.
  • interest_earned_amount—Represents the total interest earned through interest payments or capitalization. Always returned and set to 0 when no interest has been paid or capitalized.
  • net_amount—Represents the amount remaining after deducting penalties from the gross amount. Formula = gross_amount - penalty_amount.
  • penalty_amount—Indicates the total penalty applied to the withdrawal. Always equals the sum of the penalty_breakdown. Formula = penalty_breakdown.fixed_amount + penalty_breakdown.percentage_amount.
  • percentage_amount—Specifies the sum of all percentage-based penalties. Formula = rule % × withdrawal_amount.
  • net_amount—Represents the remaining amount after penalties are deducted from the gross amount. Formula = gross_amount − penalty_amount.
  • penalty_rule_applied—Lists penalty rules applied to the withdrawal, omitted when no penalty applies. Added: Every non-zero penalty_breakdown component has at least one matching rule.

Updated

Two query parameters were added to the List products endpoint to support more targeted filtering of results. These parameters are.

  • name—Filter results by product name
  • productId—Filter results by product ID

Updated

A 503 Service unavailable error EIBA0045: Accounts API temporarily unavailable is introduced to the following endpoints when there is a service outage.

Updated

A new trigger_balance body parameter was added to the Create balance endpoint.

Updated

The following event pages were deleted from the Events section of the portal. These are all under “Interest engine”. Note that there are some events with the same names under “Interest management”. These were not deleted.

  • Interest accrual succeeded (interest_accrual_success)
  • Interest post-balance operation (interest_post_balance_banking)
  • Asset status changed (asset_status_change)
  • Quota status changed (status_change_quota)

Updated

The maxItems attribute of the values array of the reactivation_exceptions_config field of the following endpoints were increased from 30 to 75.

Docs

The description and example for the balance_id field of the Create balance endpoint was updated and [beta] tag was added to the endpoint title.

Docs

The list of examples of 400 error responses for the Get account interest endpoint was corrected to include only responses that can really be returned by the endpoint. Originally, it listed some responses that were not applicable for a GET endpoint.

Instant payments

New

A new Pix DICT Statistics Reader feature is now available. The Central Bank of Brazil (BCB) requires Pix participants to maintain a database containing security information about their clients and to refresh that information at least once every six months through consultation of the security information stored in DICT. The Pismo DICT Statistic Reader retrieves and stores DICT security statistics, refreshes them periodically, and makes them available for Pix anti-fraud decisions and optional automatic transaction rejection. For more information, refer to the new Pix Dict Statistics Reader guide.

New

A new List Pix participants endpoint is now available. This endpoint returns the list of all Pix participants institutions registered in the BCB DICT, including each participant's ISPB, institution name, and type. This endpoint is listed under a new API section header "Participants".

Updated

Enhancements were made to the Automatic Pix Cancel recurrence endpoint. It now supports recurrence cancellation for journeys 2, 3, and 4. New supported QR Code recurrences also have their QR Code location disabled. 

Updated

The Pix Scheduled transfer(s) v2 endpoint now supports scheduling up to 60 transfers in advance. There is a new PRESET scheduling type and an executions array to support this. These executions can all be correlated to an original Open Finance consent. Open Finance in Brazil is a regulatory framework led by the Central Bank of Brazil that allows consumers and businesses to safely share their financial data and history across different banks, fintechs, insurers, and investment platforms using standardized APIs. To accompany this, there is a new Pix Batch scheduled transfers (Open Finance) guide.

Updated

Enhancements were made to the Cancel recurrent compound QR Code endpoint. It now disables an eligible legacy QR Code recurrence location.

Updated

A city_code (IBGE) parameter was added to the Accept/reject recurrence authorization endpoint. An IBGE municipal code is a 7-digit numerical ID that the Brazilian Institute of Geography and Statistics (IBGE) assigns to uniquely ID each municipality and federal district in Brazil.

Updated

A taxes object is now returned from the Pix Get transaction from provider endpoint. This object contains tax information related to the transaction.

Updated

An initiator_document_number optional field was added to the Schedule transfers V2 endpoint. This field is the Brazilian tax CNPJ identifier, validated as a CNPJ. This field’s presence indicates an Open Finance transaction.

Payment rails

Docs

A new BACS Direct Debit indemity claims guide is now available. A BACS Direct Debit Indemity Claim (DDIC) is a mechanism under the UK Direct Debit Guarantee that allows a customer's bank to immediately refund them for an erroneous, unauthorized, or non-compliant Direct Debit payment, and then automatically recover that money from the collecting business (the Service User).

Updated

There is a new status for BACS Direct Debit indemity claims - DORMANT. This status indicates that no Direct Debit has been received for the dormancy period (default = 24 months). Later collections generate a return_code of 6 (no instruction). This is a terminal state - collections only resume with a new mandate.

Transaction banking

Updated

A new 409 error message WEAM0049: Earmark was concurrently modified was added to the following endpoints to indicate an earmark is being modified by a concurrent operation.

Updated

A 409 error message, WRFO0019: Restricted funds was concurrently modified, was introduced to the following endpoints to show a payment being modified by a concurrent operation.

Updated

Removes the maximum: 4294967295 (int32) constraint from four ID schemas in the Transaction banking API and clears the matching text from their description blocks plus AccountID3 and AccountID4. The cap conflicts with format: int64 and caused valid 19‑digit identifiers to fail validation. The limit is a leftover 32‑bit value, so the schemas now use minimum: 1 with format int64 and no maximum. This change affects the following endpoints.

Accounts

 Earmarking (external accounts)

Earmarking (Pismo account ID)

Payments (Pismo account ID):

Dormancy:

Updated

Added release_datetime filed to the following endpoints. This field indicates the timestamp when the remaining held funds are released to the client account.

Updated

The division_id field was added to the 200 response payload of the Get transaction banking account information endpoint. This field contains the division ID generated and assigned to clients by Pismo.

Updated

The Update restriction endpoint introduces the following 422 Unprocessable Entity errors. These errors occur when you attempt to increase a recurrent restriction after the allowed increase window has expired or when the increase would exceed the requested amount.

  • WRFO0021: Cannot increase a restriction after increase_datetime_limit has passed, when the increase window has expired.
  • WRFO0022: Increase would make the held amount exceed the requested amount, when an increase would cause held_amount to exceed requested_amount.

Updated

The following new error codes were introduced to distinguish scenarios where currency_code is omitted and the currency cannot be determined because the program, organization, or both cannot be identified. The following error codes were added to the Create transaction banking account endpoint.

  • WCAC0048: currency_code was not provided and could not be resolved from the program or the org
  • WCAC0049: currency_code was not provided and the program was not found
  • WCAC0050: currency_code was not provided and the org was not found

Updated

A note was added to the credit and debit request objects of the Post multi-leg payment endpoint clarifying that using force_post or validation_rules.ACCOUNT_STATUS.override posts the leg as a forced authorization, which can affect dormancy handling because forced transactions may not reactivate dormant accounts.

Updated

Account closure requirements in the Close transaction banking account were clarified to specify that an account can be closed only when book_balance, ledger_balance, uncleared_checks_balance, and earmarked_balance are all zero and there are no active scheduled payments. Also clarified that balance updates after payment operations are asynchronous, recommending a balance check before closure and retrying the request if WCAC0019 is returned.

Deprecated

The following endpoints were decommissioned and removed from the Developers Portal and added to the API endpoints removed list.

  • Post multi-leg payment v2
  • Get multi-leg payment status v2

Cards

Updated

The following new error codes and messages were added to the Update card embossing address endpoint.

  • 400 Not found—No embossing record for this tenant + card + account
  • 400 Not found/Bad request—Database failure while looking up that record
  • 500 Internal server error—Unable to process your request

Disputes

New

Two new fields were added to the Visa collaboration questionnaire (Create dispute form endpoint) supporting form for disputes.

  • facilitiesWithdrawnDate—Date the merchant's facilities were withdrawn. Format: YYYY-MM-DD. Valid in the Visa Consumer Disputes Flux (Reason Code 13).
  • dateCardholderCheckedOut—Date the cardholder checked out of the hotel. Format: YYYY-MM-DD. Valid in the Visa Consumer Disputes Flux (Reason Code 13).

These fields were also added to the Visa collaboration questionnaire guide.

Network transactions

Updated

Due to a recent security enhancement, Balance Inquiry operations are now recognized and processed as complete transactions, following the same standard security validation flow applied to other authorization transactions, including event generation and record persistence within the Pismo platform.

Docs

A note that incorrectly stated the incremental authorization feature is available only for Full balance was removed from the Incremental authorizations guide. Pismo supports incremental authorization for both Full balance and Zero balance.

Statements

Updated

The fields discharge_order and payment_hierarchy_id were added to the 200 response of the List discharges endpoint.

Updated

A new parameter, MAD_PAYMENT_TRANSACTIONS_TYPES (ID 4), was added to the table in the Multivalue program parameters guide. Also, a note was added to the description of the PAYMENTS_TTS (ID 2) parameter.

Docs

The descriptions for the Change due date and Close account cycle endpoints were updated.

Docs

A new section, How to cancel specific transactions separately, was added to the Credit liquidation guide. It’s not a new feature, but it wasn't properly documented before.

Deprecated

The following endpoints were decommissioned and removed from the Developers Portal and added to the API endpoints removed list.

  • Get account total due (GET /statements-v2/v2/accounts/{accountId}/total-due)
  • List transaction types (GET /statements-v2/v1/transaction-types)

Control Center

Updated

The dual approval feature in Control Center was updated. You can now request Pismo to enable dual approval for the following actions.