9 January 2026

Changes between 5 December 2025 and 9 January 2026

Core platform - Flex controls

New

Flexible transaction controls now support attribute groups, which allow you to define sets of values, such as merchant IDs or Merchant Category Codes (MCCs), that can be shared across multiple controls within the same organization. This feature simplifies control configuration and significantly improves maintainability.

The following new endpoints are available:

For more information, refer to the Attribute groups guide.

Core platform - Payments

New

The payment scheduler functionality is now available in general release and with additional endpoints and features. In addition to the creating and executing a pre-schedule, which was previously supported in beta release, you can now also create bulk pre-schedules. In addition, the following endpoints are now available and support schedules of single and transfer type.

For more information, refer to the Payment scheduler guide.

Core platform - Security

New

New security guides are now available: Pismo platform security guide and two sub-guides Security audit, testing, and incident response and Compliance, certifications, and security teams. These guides offer a high-level understanding of the security Pismo provides for the Pismo platform. This includes topics such as access management, data and information management, backup and recovery, and much more.

Data and reporting

New

Regulatory scheduled reports are now available for the United States. A new guide, Reports for the United States, lists and describes them.

Card issuing - Card tokenization

New

There is a new MDES Token Connect API and guide to support Mastercard’s Token Connect service. Pismo acts as a pass-through proxy for this service and Pismo’s API endpoints mirror Mastercard’s endpoints. Token Connect is a framework within Mastercards’s Digital Enablement Service that allows issuers (card-issuing banks) to directly push a tokenized version of a customer's card (for example, their debit or credit card) to digital wallets and merchant platforms.

Card issuing - Statements

New

The new installment advancement functionality is now available in beta release, giving you early access to explore its capabilities and share feedback. This functionality supports two new modes:

ALL_CONTRACTS: Advances all future installments for all installment agreements in the account.
MULTIPLE_CONTRACTS: Advances installments for specific contracts with individual configurations.

The following endpoints are available in beta:

New

The new “Revolving credit - Statement refinancing” section with subsection “Payment agreement simulation” is now available. It contains the following endpoints:

New

The new Close account cycle endpoint is now available in beta release.

Control Center

New

The Control Center homepage was redesigned to keep the essentials front and center.

What’s changed?

What’s new section—gives you quick insight into upcoming features, key changes, and any pending actions (like requests and approvals).
Refined design—makes scanning simpler and helps you stay focused on what matters most.
Direct access to the Pismo Developers Portal— provides deeper technical resources.

What hasn’t changed?

The key features you rely on remain the same:

Your program data
Your favorites
Navigation: the main menu, organization menu, and header

Read more about these changes in Navigating Control Center.

New

There is now a quick and easy way to unblock cards without waiting for timeouts directly from the Pismo Control Center. When a cardholder enters the wrong PIN too many times, their card gets temporarily blocked. With this new feature, you can reset the PIN try count and instantly unblock the card—right from the Accounts -> cards section in Control Center. This feature supports dual approval: one person initiates the request, and another reviews and approves it. With dual approval, the change only takes effect after approval, ensuring full control and compliance. Learn more about this feature in the Card information guide and the Dual approval guide.

Core banking

Docs

The Bank statements guide is now available. This guide explains how the Pismo platform generates and manages bank statements through cycle closing—its continuous, configurable process for capturing daily account balances, producing balance history, and supporting accurate reporting across business and non‑business days.

Seller management

New

The Seller management, Marketplace API has three new endpoints. These new endpoints allows you to create a new marketplace, retrieve marketplace information by its ID, and update marketplace information.

Accounts

Updated

A currency_numeric_code field was added to the account object in the Create account application endpoint. This is the ISO 4217 code for the account's currency. If not defined, the Pismo platform uses the program currency code. If not defined at the program level, the platform uses the currency code defined at the organization level.

An allowed_operations enum field was added to the Create status reason endpoint. It is now also now returned from the List status reasons endpoint. This field is used to determine what operations an account is allowed to do given its status.

Flexible transaction controls

Docs

The description of the entry_mode field description on the flex controls endpoints was updated to provide details about the Visa and Mastercard field and code specifications.

General

Docs

The Welcome to Pismo page was updated to include Control Center and link to more developer guides.

Docs

BIN descriptions were updated throughout documentation to indicate that it refers to the first six to eight numbers on a payment card.

Migrations

Docs

The Accruals and Balance sections in the Migrations guide were removed.

Payments

Docs

The Authorization validation rules for platform operations guide was updated to correct a typographical error and display in tables.

Security

Docs

The link to Generating a JWT in the token field of the Get OpenID access token endpoint was fixed.

Setup

Updated

A new program parameter Allow overriding the minimum amount due for the current statement was added to the table in the Program parameters guide.

Docs

A line was added to the description for the Interest rate period program parameter in the Program parameters table.

Support

Docs

The Incident lifecycle guide was updated to include a diagram of the incident lifecycle workflow.

Docs

The Pismo operations status guide was updated to include the timelines for sending out scheduled and emergency status messages.

Transactions

Docs

The description of the card object in the response of the Get transaction and List transactions endpoints was updated with clarifications how the field is populated for different types of transactions.

Docs

In the Transaction types guide, the descriptions of the 604 and 512 transaction types and 0001 processing code were standardized.

Events

Updated

Two new values were added to the trigger_reason field of the Account balance history generated event:

INTEREST_POSTED: Triggered when interest is posted to the account
INTEREST_ACCRUED: Emitted when interest is accrued on the account

Docs

A note was added to the description of the Delinquent account closed event.

Docs

The Setting up an additional event subscriber section within Data and Reporting was revised to align with the GRC policy. External systems or organizations outside Pismo are not allowed as additional subscribers. This avoids misconfigurations and non-compliant solution designs.

Banking operations

Updated

Two new body parameters were added to the Update account interest endpoint: taxes_exemption and fee_processing_code.

Integrated payments

Fixed

The Perform cash-in endpoint is removed from the Integrated payments API reference, as it was intended for internal use only.

Instant payments

New

Pix payments has a new endpoint - Update infraction report - that allows the caller to update some fields in an infraction report.

New

There is a new event - Pix internal transaction reported - generated when a Pix internal transaction occurs and is reported. You can use this event to track internal Pix transaction progress, completion, or failure.

Transaction banking

Updated

A new error code, WEAM0046 (Invalid account currency code), is now available. This error is returned when a client provides a literal currency code instead of a numeric one—for example, entering USD instead of 840. This code was added to the following endpoints:

Updated

A second error code, WPMT0056 (Invalid account currency code: 999), was added for the same validation in the Post payment endpoint.

Updated

For the Post multi-leg payment endpoint, two additional error codes were introduced to handle credit and debit legs separately:

WMLP1043 for credit legs
WMLP0005 for debit legs

Updated

The Create fund restriction endpoint now includes the error code WRFO0013 to enforce the same rule.

Updated

The new optional business_date field was added to the Confirm payment endpoint, consistent with the field of the same name in the payments API.

Key behavior:

Defaults to the current business date.
Allows the client to submit a business date to confirm a future‑dated payment pre‑authorization.
Accepts dates within the range D‑1 to D+1.

Updated

The Confirm payment and Cancel payment endpoints now include the same business‑date validation errors used in the payments API, with one exception:

WPMT0057 : Cannot instantly cancel when original business date is after the current date

This is a new error specific to Cancel payment. It occurs when you attempt to cancel a future‑dated payment using cancellation_method=INSTANT.

Updated

The new optional cancellation_method field was added to the Cancel payment endpoint. It supports the following values:

instant (default): Reverts the payment and updates balances using the current business date.
original_dates: Reverts the payment and updates balances using the payment’s original dates (business_date and payment_datetime).

Updated

For the Revoke operation block endpoint, the following error was introduced to indicated that the operation block you are attempting to deactivate is already inactive:

WOBK0009: Operation block is not active

Authorizations

Updated

The List account authorizations endpoint has two new fields, merchant_category_id and processing_code, returned with network authorization query results.

Card network integration

Docs

The Full balance versus Zero balance integration guide was updated in the following ways.

Included support for flexible transaction controls in Zero balance integration.
Corrected link to and added clarifying details in the Accounting management section.

Docs

The Simulate authorizations guide was updated to include entry mode information with a link to the Validation code definitions guide with full details of the possible entry mode codes.

Docs

The FRH-POS (point-of-sale) entry mode validation description in the Validation code definitions guide was updated to correctly reflect that the entry mode field for Visa is field 22.

Docs

The Authorization events guide was updated to correctly reflect that the Network authorization ISO8583 message event and the Network authorization received event are sent to both Full and Zero balance issuers. The same correction was made to the Authorization/Base I workflow in the Full and Zero balance transaction workflows guide.

Disputes

Updated

For the Get dispute endpoint, the form field in the response is a string but was incorrectly listed as an object. This string contains many objects and properties though. In the Create dispute form endpoint, the form field is an object and you can view its objects and properties to see what is returned as a string in Get dispute.

Embossing

New

The “Cards issuing - Cards > Embossing” section is now 3 sections - Embossing, Embossing data, and Embossing encrypted.

Three new endpoints were added to the Embossing encrypted section:

The Embossing encrypted endpoints are for issuers who want to do their own embossing and need a card’s encrypted data as per regulations. For the V2 endpoints, the initial vector (iv) field is not passed but is Pismo-generated and returned in the response.

Docs

A section about IPK certificates has been added to the Physical card embossing guide. An Issuer Public Key (IPK) Certificate is a digital certificate used in financial transactions, especially with Visa contactless cards, containing an issuer's public key. Pismo does not provide the IPK; the issuer or network, likely the issuer, is responsible for it. Providing this certificate falls outside Pismo's scope.

Instant payments

Docs

There is a new Faster Payments System (FPS) guide. FPS is an instant payments service in the United Kingdom. This guide documents Pismo services for FPS integration in the UK, their architectural approach, its major transaction flows, and the end-to-end process for connecting to FPS using the Pismo platform.

Statements

Updated

The new ranges property was added to the body parameters and 200 responses in the following endpoints.

Updated

The new query parameters beginDueDate, endDueDate, and maxClosedCycles were added to the List statements v3 endpoint.

Docs

Description of the Update account collection status endpoint was updated.

Docs

The first two paragraphs of the Credit liquidation guide were updated to remove duplicated information.

Docs

The description for the Create program calendar strategy endpoint was updated.

Docs

The first bullet point in How the program discharges transactions was updated to clarify information.

Docs

A note was added to the descriptions of default_rate and rate_if_overdue in the body parameters and 200 response of the Configure account accrual rates endpoint and in the 200 response of the List account accrual rates endpoint.

Docs

The items field in the 200 response for the Get interest accrual summary endpoint was incorrectly documented as an object. It should be an array of objects. The documentation was updated accordingly.

Lending

New

The following new v2 endpoints are now available in beta release. They will eventually replace the v1 endpoints.

Migrations

Updated

The new fees field was added to the Get creditor operation endpoint.

Control Center

New

The Export user list functionality was added to Control Center. If you have the Admin or User manager role, you can export the list of an organization’s users as a CSV file. The exported user list contains information useful for auditing and reporting purposes.

Docs

The Card network tokenization guide for Control Center was updated to note that a Service Desk request is necessary to configure anti-fraud webhooks within Control Center.