3 April 2026

Changes between 6 March and 3 April 2026

General

Docs

The new Pismo API reference overview guide is now available. The guide orients new users to Pismo’s API reference documentation and serves as a reference guide for existing users looking for specific information. The guide:

Outlines the standard elements present on a typical endpoint page in the Pismo Developers Portal
Summarizes key REST API and Pismo-specific standards and attributes
Describes how to build and test API requests using the interactive console

Docs

The AI-powered search feature was updated in the Pismo Developers Portal. The Developers Portal now features a standalone AI assistant called Ask AI.

The Get started with Ask AI and Get started with the Pismo Developers Portal guides were updated to reflect this new functionality.

Core banking - Transaction banking

New

The new Fund coverage API is now available and includes the following endpoints.

The new Funds coverage guide explains this functionality.

New

The following v2 account balance history configuration endpoints are now available to configure account balance history settings using division, organization, and program IDs.

New

The new Register banking accounts with transaction banking endpoint allows you to register existing Pismo banking accounts for transaction banking, which gives you access to transaction banking APIs and features.

Control Center

New

You can now create and manage Buy Now, Pay Later (BNPL) loan products in Control Center. The new Loan products guide explains this functionality. This feature is currently available in the PROD-US environment.

Updated

The dual approval feature was updated in Control Center. You can now request Pismo to enable dual approval for holding, releasing, or transferring funds.

Client webhooks

Updated

The client webhook for tokenization was updated with a network_call_method field. Possible values: VTS_DEVICE_BINDING | TA | VTS_APPROVE_PROVISIONING | VTS_APPROVE_PROVISIONING_ISO. The Visa example for the original_network_data field was updated. The following new custom codes were added.

Custom code	Description	VTS action code	MDES action code
ELFR2	CVV2 retry limit exceeded	05	05
MATPC	Exceeded maximum active tokens per card	05	05
FRE	Cryptogram data validation failed	05	05

Flex controls

New

The new List program flex controls endpoint is now available.

Migrations

Updated

The following fields were added to the Migrate tokens endpoint.

expiry_date
network
status
tc_date_time
token
token_unique_ref
wallet_identifier
device_id
correlation_id

Docs

The field descriptions in the following endpoints were updated for editorial enhancements to align with Pismo documentation standards and best practices.

Payments

Docs

The denial codes list in the Authorization validation rules for platform operations guide was updated to correctly list and define CBD (card broken) and CDB (card blocked).

Deprecated

The deprecated currency field was removed throughout the payment scheduler API.

Transactions

Updated

In the Create transaction type and Create transaction flow endpoints, the following new response is now available.

Status code 409 - Error WTRC08001 - The provided transaction_type_id is reserved by the platform and cannot be used.

Security

Updated

Due to security issues, you can no longer generate your own certificate and sign it with your own Certificate Authority when configuring identity connectivity with mTLS. In addition, certificates will now expire after two years instead of three. Both of these changes are reflected in the Identity connectivity with mTLS guide.

Docs

The following changes were made to the JWT claims list in the Verifying webhook requests guide.

The JWT claim aud (audience/host name) was removed from the table because it is not a valid claim in the JWT token that Pismo provides.
The JWT claim body-hash was corrected to replace the incorrect format of “body_hash”.
The JWT claim kid is no longer marked “not always provided” as it is always part of the JWT.

Docs

The JSON request sample code in the Authentication with OAuth2 guide was updated to indicate the recommended use of “data-urlencode” instead of “data”. Although the request works with “data”, “data-urlencode” is needed for some specific credentials when generated with special characters (such as ( )).

Setup

Docs

In the Create balance configuration endpoint, the global_config parameter was added to documentation.

Docs

The Update account limits (outdated) endpoint was marked as outdated. Use the Update account limits endpoint instead, which also validates the account limit against the configured program global limit. The Account limits guide was updated accordingly.

Events

New

The new Cycle closing configuration created event is now available. The platform generates this event when a new account balance history configuration is created using organization, division, or program IDs.

New

The new Account inactive_since status updated event is now available to provide information how long a bank account has been inactive.

New

The External payout processed event is now available. The platform generates this event when payouts are successfully processed and an external payout account was configured during product attachment.

Integrated payments

Updated

The new transaction_id field is now available in the following endpoints. This is the ID that links the bank slip to the specific transaction performed in the payments API. It can be used for tracking, reconciliation, and reference purposes when managing bank slips and their associated transactions.

Interest-bearing accounts

Updated

The subsequent_withdrawals field was added to the penalties object in the following endpoints. This field allows you to define a withdrawal window that applies a penalty to subsequent withdrawal events.

Updated

The corresponding fee IDs and penalty transaction flow were added to the following penalty types in the Create deposit product endpoint.

early_withdrawal_after_opening
grace_period
tiered_interest_forfeiture
withdrawal_fee
subsequent_withdrawals

Docs

The new Penalties for deposit products section in the Interest-bearing accounts guide provides details on penalties, their corresponding fee IDs, and transaction flows.

Docs

The new min_amount field allows you to specify the minimum amount required for yield calculation. This field was added to the following endpoints.

Docs

The "savings account" was renamed to "savings account product" in the documentation for the following endpoints.

Transaction banking

Updated

The Create earmark endpoint now includes the following error codes.

WEAM0016: Invalid header account. Informs clients that the x-account-id header is invalid or malformed.
WEAM0024: The account cannot be credited. Credit function is not active. Returned when the account cannot receive credits, whether because it is inactive or for another related reason.

Updated

The Post payment endpoint now includes the following error codes.

WPMT0008: Invalid processing code. Returned when the processing code is invalid.
WPMT0014: Account is closed. Returned when the account is closed.
WPMT0019: Cannot use same account for credit and debit. Returned when clients attempt to use the same account for both credit and debit in a transfer.
WPMT0032: Validation rules conflict with internal accounts program. Returned when validation rules conflict with the internal accounts program.
WCAC0002: Invalid header account. Indicates that the x-account-id header is invalid or malformed.
WCAC0012: Account not found. Returned when the account cannot be found.

Updated

The Settle float payment endpoint now includes the following error codes.

WCFC0022: Transaction using this tracking_id is in progress, please try again later. Returned when a transaction with the same tracking ID is already in progress.
WCFC0023: Operations blocked for account. Returned when an operations block is in place on the account.

Updated

The Create check posting endpoint now includes the following error code.

WCPT0014: Invalid account currency code: 999. Returned when the client provides an invalid currency code.

Updated

The Create fund restriction endpoint now includes the following error codes.

WRFO0014: Invalid restricted funds processing code. Returned when the client provides an invalid processing code for a restricted funds operation.
WRFO0003: Account is locked, please try again later. Returned when the account is locked because of concurrent operations.

Updated

The Post payment endpoint now includes the following error code about division IDs being set with an invalid timezone.

WPMT0002: invalid timezone (invalid)

Updated

The Upload bulk file endpoint now includes the following bulk header-related 400 error codes.

WBUP0004: Invalid request header
WBUP0005: Invalid JSON data in bulk header
WBUP0006: Authentication OrgID does not match Bulk Header
WBUP0007: BulkID in URL does not match Bulk Header
WBUP0008: Invalid operation_type in Bulk Header

Authorizations

Docs

The Authorization configurations guide was updated to correctly indicate that the always_call_ledger_rules field is only required for Full balance and is not required for Zero balance.

Card network integration

Docs

A new guide, PAN encryption for 3DS authentication, was published to describe the PAN encryption process for use with the Send pre-authentication info endpoint.

Cards

Updated

The activation_date field was removed from the Card updated event.

Embossing

Docs

A new section was added to the Physical embossing guide—Embossing flows—that describes the endpoint/event flows for embossing nominal and noname cards.

Statements

Updated

The following changes were made in the Create installment advancement and Create installment advancement (outdated) endpoints.

The new option REMOVE_ALL_INTEREST was added to the calculator field and the field description was updated.
The endpoint descriptions were modified to clarify how to handle the interest on advanced installments.

Updated

The x-program-id header field was removed from the following endpoints.

Updated

The following change occurs in the Payment agreement API.

Starting March 30th, 2026, payment agreement transactions will be created using Payment methods. This change provides greater flexibility and includes the following enhancements:

Support for processing codes.
Use of the same authorization ID for payment agreement cancellation transactions.
Support for creating additional transactions, such as insurance, when the agreement is created.

Rollout schedule:

April 6 to 17: EXT
April 20: Other Prod environment (except Prod-MT and Itaú)
May 18: Prod-MT environment
June 1: Itaú environment

This change does not affect current customer processes.

Docs

The Delinquency buckets guide no longer applies only to India, because at least one other country is using delinquency buckets. So, “(India only)” was removed from the beginning of the guide. The second paragraph was also modified to remove the reference to India.

Docs

The Credit card refinancing guide was divided and some information was moved into the following new guides.

These 3 guides replace the following guides, which have been deleted.

Create an installment agreement
Create a statement agreement
Create a compulsory agreement

The remaining text in the Credit card refinancing guide was updated to improve clarity.

Docs

The description of the Change due date endpoint was updated to emphasize that the due date must be updated no later than two days before the cycle closes.

Docs

The text of the Managing the charge order for debit transactions guide was updated to improve clarity.

Docs

The following sections were added to the end of the Full balance credit program guide.

These features are not new but they haven’t been documented before.

Docs

The [Accrual type rate structure](doc:configuring-accrual-rates#accrual-type-rate-structure section was updated for clarity. The callout in the Validation for configuring accruals section was updated for the same reason.

Docs

The Installment management guide was replaced with the Installment advancements, since the original guide primarily covered installment advancements. Most of the material in the Installment advancements section was moved into the new guide.

Docs

The Accruals section was updated to clarify how the MAD determines whether the Pismo platform considers the debits as paid, refinanced, or overdue.

Docs

The header names of the first two columns in the table in the Update account collection status endpoint documentation were switched because they were labeled in the wrong order. That is, the first column was incorrectly labeled “Account status”. It is now “Collection status”. The second column was incorrectly labeled “Collection status”. It is now “Account status”.

Deprecated

The Accrual rate discount program parameter was removed from the table in the Program parameters guide. This program parameter has been deprecated for some time and has now been decommissioned.

Lending

Updated

The List account loans page was updated to include the following new loan status options and their descriptions: SCHEDULED, PROCESSING, PAID, PARTIALLY_PAID, PAST_DUE, CANCELED, NOT_PAID.

Marketplace

New

The new List marketplaces is now available. This endpoint returns a paginated list of marketplaces with optional filtering and sorting capabilities.

Control Center

Updated

The Interest plans guide was updated to reflect the enhanced Control Center experience, which makes it easier to configure how interest is calculated and applied across products, including:

Interest thresholds—Set minimum and maximum limits for interest rates
Interest by tiers—Apply different rates to different portions of a balance

This feature is currently available in the PROD-US environment.

Docs

The Edit programs guide was updated to clarify that you cannot remove transaction types from existing transaction categories for programs.