7 July 2025

Changes between 6 June and 7 July 2025

Control Center

New

We’re excited to announce that our redesigned menu is now live in EXT—making it easier than ever to find exactly what you need.

What’s new?

All configurations, organized clearly. Find all configurations in one place, grouped by platform-wide settings, card issuing, and banking.
User and permission management, simplified. Manage users and permissions from a single location.
Organization details, now easier to find. We’ve moved them out of the menu and into the top organization selector, where they belong.

Why the change?

We’ve redesigned the menu to make navigation clearer and more intuitive now, while also making room for future features as Control Center grows.

What do you need to do?

Just one thing: reset your favorites in EXT. Your current favorites won’t carry over, so you’ll need to add them again.

Security guide

Docs

A new Security guide for Control Center is available to help you understand the security options and protections available to you. The Control Center has a number of systems and policies in place to ensure and enforce security and privacy. This includes requirements and processes related to the creation, authentication, and authorization of users and defined practices for data retention and handling of personal identifiable information (PII). It also includes account and organization access.

Seller management

Docs

If you are getting started with seller management, now you can read about onboarding with Pismo as well as how to get started including planning, governing, processing codes, testing, and monitoring seller marketplaces.

Accounts

Updated

The number field in the address object for the Create account application and Create address endpoints is no longer required.

Client webhooks

Updated

Two new response address fields, street and number, were added to the Zero balance validations webhook. The response fields table and the sample response were updated with these new fields.

Flex controls

Updated

The following new attributes are now available to evaluate a flex control condition:

acquirer_country_code
authentication_method
is_cavv_present
is_tra_exemption_requested
is_token_present
initiation_mode

These attributes are available as options inside the conditions.attribute field in the following endpoints:

These attributes are also available as options inside the conditions.attribute field in the following events:

General

Docs

The new API endpoints removed guide lists when API endpoints were removed from Pismo’s public documentation.

Payments

Updated

The following new processing codes and their reversal processing codes are now available:

PSM039 (cashback) and PSM04 (cashback reversal)
PSM018 (installment withdrawal TECBAN) and PSM019 (installment withdrawal TECBAN reversal)

Programs

Deprecated

The deprecated endpoint List due dates for all statements was removed from public documentation.

Security

Docs

The steps for Server authentication in the Authentication with OpenID Connect guide were updated to reflect that you no longer need to send a public key to Pismo and instead you upload the public key directly to Control Center.

Docs

The JWT key descriptions in the Authentication with OpenID Connect guide were updated for clarification.

Events

Deprecated

The events in the rules domain that were previously listed on the Events tab under Core platform > Flex controls were removed as no longer applicable. Refer to the full list of flex controls events in the audit domain.

Banking operations

Updated

The new field change_available_datetime is now available on the Account balance changed and Account balance history generated events. This field records the exact date and time of impact to a balance in a ledger.

Banking reports

Deprecated

The following endpoints were deprecated and decommissioned on 30 June 2025. Refer to API endpoint deprecation and removal schedule for a list of deprecated endpoints.

Create transaction types
Get account income report
Get account annual fees report
List transaction types

Instant payments

New

A new enum value - PIX_AUTOMATICO - was added to the refund_reason enum field for Pix refunds. It indicates that a Pix refund was requested due to a failed Automatic Pix operation.

New

A new section was added to the QR Code API - Recurring payment. In this section, the following endpoints were added to generate QR Codes for recurring payments such as gym membership:

Transaction banking

Updated

division_id in the Division cycle closing completed event is now a required field.

Updated

The fields future_dated_credits_balance and future_dated_debits_balance were added to the 200 response payloads of the following endpoints. These fields add information about future-dated credit and debit balances in the response.

Updated

The new field check_timezone_origin was added to the following endpoints and events. This field allows you to specify whether the dormancy check should use the timezone of the account’s program or division.

Endpoints:

Events:

In addition, the following "Invalid timezone origin" error message was added to the Create dormancy configuration and Update dormancy configuration endpoints.

code: "WDOR0002"  
message: check_timezone_origin must be one of [DIVISION PROGRAM]

Updated

The change_available_datetime field is no longer a required field in the following events:

Updated

The following error messages were added to the Create account balance history configuration and Get account balance history configuration endpoints in relation to the limit defined for cycle_event_delay. The limit is now set for 1439 minutes after cycle_closing_time.

WCFG0002: cycle_event_delay must be 1,439 or less
WCFG0002: divisionCode is a required parameter
WCFG0002: cycle_closing_time must be a maximum of 8 characters in length
WCFG0002: cycle_closing_time has an invalid time format: {cycle_closing_time}
WCFG0002: cycle_event_delay must be 5 or greater
WCFG0002: cycle_closing_time or cycle_event_delay must be provided

Docs

Two account balance definitions were added to the account balance definitions table in the Account balance definitions for transaction banking guide:

Future-dated credits balance
Future-dated debits balance

In addition, this guide now includes a note that uncleared_funds is calculated as future_dated_credits_balance - future_dated_debits_balance.

Card network integration

Updated

A new REJECTED reason, HSM_UNKNOWN_ERROR_RESPONSE, was added to the CVM validation.

Docs

A note was added to the definition for the validation code DCM (original authorization not found at refund) to clarify some differences in event responses for MTI 0420 and 0400 refunds.

Card tokenization

Deprecated

The public documentation for the deprecated endpoints Get encrypted card data for wallet token and Get encrypted card data for Apple Pay were removed.

Cards management

Docs

Two new sections were added to the Cards API reference - Card reissue (2 endpoints) and Card status (3 endpoints). The endpoints aren’t new, this was done to improve API organization and readability.

Docs

A new Card reissuing guide is now available. The content for this guide was previously contained in the Cards lifecycle and statuses guide.

Disputes

Updated

The following fields were removed from the Visa Collaboration Process Errors form under dispute_due_to = D (Duplicate) or P (Paid by other means):

arn
transactionID
rolTransactionId
duplicateTranAmount
duplicateTranId
duplicateTranDate

Statements

Updated

The Post interest accruals endpoint now includes two new fields: start_date and end_date.

Updated

The following updates were made to the List statements v3 endpoint.

The showAmounts query parameter was removed. Before this update, setting this parameter to true would cause some additional fields to be displayed in the 200 response. These fields are now displayed automatically if a statement is closed and if it was closed after 17 April 2025. This is because the behavior of these fields has changed, and if they were shown for statements that do not fit these criteria, they would not contain the expected information. The following fields were affected and their descriptions were modified.
- amount_due
- amount_paid_until_due_date
- amount_paid_after_due_date
- other_credits_until_due_date
- other_credits_after_due_date
A new enum field called status was added. It represents the status of the statement, and it has the following values: CLOSED, CLOSED_NOT_DUE, OPEN, FUTURE.

Updated

A new section Configuring features based on account status was added to the Full balance credit program guide. It explains the use of three new endpoints that have been added to the API.

Docs

A new guide Limiting the number of days accruals can be charged is now available.

Docs

The Managing due date, cycle closing date, and additional grace periods guide was updated to correct and clarify information about grace periods. Renamed the section “Defining a grace period” to Defining an additional grace period and updated its contents.

Docs

A note was added to the description of the Create recurring charge plan endpoint explaining that the 504 - RECURRING_CHARGE_FINAL_ACCOUNT_STATUS program parameter must be set in order for the endpoint to work properly.

Docs

The new section Configuring features based on account status was added to the Full balance credit program guide.

Docs

The description and example for the reason field of Close delinquent account was corrected.

Docs

The Create installment advancement endpoint description and the descriptions of the response body fields old_amount, new_amount, and new_interest_amount were updated.

Docs

The bullet point 3 in Installment advancements was updated.

Docs

A new callout at the end of the “Payment hierarchy” section of How the program discharges transactions explains an exception to the rules about how transactions are discharged.

Docs

The section How to automate closing delinquent accounts was updated.

Docs

The Multivalue parameters guide was updated with additional columns and information and some corrected entries.

Merchants

New

Now you can link multiple merchants to a marketplace rather than one merchant to one marketplace. These newly released endpoints enable this feature:

Pismo Control Center

Fixed

An issue was fixed where network acceptance information was not being displayed for credit program exports.

Docs

The new Cloned and exported program properties guide helps explain what program information is exported or copied, addressing issues with program status and manual configuration steps.