Changelog
Sub-processorsAbout PismoContact us
Back to All

1 May 2026

3 days ago by [email protected]

Changes between 3 April and 1 May 2026

General

Docs

We’re pleased to announce the new Pismo platform onboarding guide. It walks new Pismo customers through the onboarding process, including organization creation, required tool and system access, and authentication setup.

All onboarding information is now consolidated in one place. As part of this update, onboarding content was removed from the following guides, which now link to the new onboarding guide instead:

  • Get started with core banking
  • Get started with transaction banking
  • Getting started with demand deposit accounts (DDAs)
  • Get started with card issuing
  • Get started with lending
  • Seller management onboarding

Docs

An introductory explainer video was added to the Get started with the Pismo Developers Portal guide. The video introduces the Developers Portal and provides an overview, including:

  • The purpose of the portal and who it’s for
  • An outline of the key sections and features
  • Guidance on where to start and what to explore based on your role

Docs

A feature overview video, “Understanding fee models in the Pismo platform,” was added to the Fee models guide. The video introduces the basic concepts and benefits of fee models, including:

  • Business benefits
  • Calculation rules and triggers
  • Hierarchy of control

Disputes

New

The new Mastercard dispute lifecycle management for Control Center is available in test environment (EXT)

The new experience helps you manage Mastercard disputes more easily, with a clearer interface and better tools. This feature is available from the main menu under Customer operations -> Disputes.

With this feature, you can:

  • Open disputes for transactions with or without installments using automated control
  • Select reason codes aligned with Mastercard standards
  • Create partial disputes
  • Update dispute statuses
  • Create fraud reports
  • Create Expedited Billing Dispute Forms (EBDF)
  • Upload supporting evidence files
  • Track dispute status and progress

To use this feature, you must have one of these roles assigned to your user account:

  • To view disputes: backoffice-viewer
  • To open and update disputes: backoffice-operator

What else can you expect? Look for Disputes in Control Center production soon.

How can you learn more? Explore how disputes management works in Disputes.

Transaction banking

New

Bank statements API v2 is now available. The new version allows you to create or update account balance history configurations at the division, organization, and program levels using a configuration ID. Previously, this was supported only at the division level. Bank statements API v2 includes the following endpoints:

New

The following endpoints were created that work specifically with Pismo account IDs. Their original counterparts remain active.

Earmarking

Payment

Docs

The new Channel Control for back-business-date and cutoff exceptions guide explains how channel-based access and execution controls work, including configuration of channel-based exceptions for back business dates and cutoff processing.

Docs

The new guide Penalties for CD accounts is now available, This guide explains how you can define and combine rules that apply specific charges when certain withdrawal events occur, with the Pismo platform evaluating these conditions at withdrawal time based on the product’s configuration.

Accounts

New

The new field is_centralizer was added to the Create account application request. This boolean field indicates if the account is a centralizer account. A centralizer account, within the account hierarchy, is the account responsible for invoice billing.

Accounting

Docs

The accounting API documentation was enhanced in the following ways.

  • The Accounting scripts V2 endpoints were moved into a separate section, the majority of their field descriptions were added or enhanced, and the unused cosif field was removed.
  • In the Create accounting script V1 endpoint, the cost_center field was marked as optional instead of required and the entry_name field was updated with the list of enum values and their descriptions.
  • In the Create accounting entry endpoint, the tracking_id field description was updated to indicate that it's a UUID field and with the link to the random UUID generator.

Docs

In the Accounting events report files guide, the descriptions for the CreatedAt, EventDate, and RefDate date fields were updated to include formats and the data type for the AuthorizationDate field was corrected to be date instead of string.

Fee management

Docs

The Fee management guide and Fee models guide were rewritten for clarification and to provide more in-depth details about fee models in the Pismo platform. In addition, three new guides related to fee models are now available.

Migration

Docs

The Migrate authorizations and Migrate merchant transactions property fields were revised for general editorial updates to better adhere to Pismo documentation standards.

Payments

New

The new API with 4 endpoints is now available in beta release- Payment rails - BACS payments. BACS stands for Banking Automated Clearing System. BACS is a UK service that facilitates electronic money transfers between banks within a 3-day settlement cycle— Day 1 (submission), Day 2 (processing), and Day 3 (clearing/credit).

Docs

The Payment methods guide was enhanced with the diagram that illustrates transaction categories.

Docs

In the Payment configurations API documentation, the titles were updated to avoid duplication and descriptions of boolean fields were updated according to standards.

Security

Docs

The Verifying webhook requests guide was updated in the following sections.

  • The public key request sample in the Retrieving a list of public keys section was updated to reflect the correct URLs.
  • The cache-control sample in the Renewing your public keys section was updated to reflect a correct max-age example.

Docs

The Get an account-specific token guide is now available.

Setup

Docs

In the Environments guide, the following were added to the list of PCI services.

  • /payment-methods/
  • /payment-methods-configs/

Docs

In the Balance configurations API documentation, the global_configs field name was corrected throughout. Some instances previously incorrectly listed this field as global_config.

Support

Docs

The description of the Occurrence field in the Request types and common fields guide for the Pismo Service Desk was updated for clarification.

Transactions

Fixed

The createdAt field was standardized in how it's handled and delivered across transaction events and endpoints. This change ensures that all createdAt date values sent in the events and returned by the transaction search endpoints are consistently expressed in Coordinated Universal Time (UTC), as denoted by the suffix Z.

At the time the Transaction created and Transaction updated events are sent, createdAt is now converted to UTC and correctly suffixed with Z. For example, in database timezone UTC−3, if the recorded time is 2025-01-01 12:00:00, createdAt is now correctly converted and sent as 2025-01-01T15:00:00Z.

Previously, these events were sent with createdAt in the database’s configured timezone but erroneously suffixed with Z. For example, in database timezone UTC−3, if recorded time was 2025-01-01 12:00:00, createdAt was sent as 2025-01-01T12:00:00Z.

In the Get transaction and List transactions endpoints, the response now converts from the actual database-configured timezone to UTC. For example, in database timezone UTC−5, if the recorded time is 2025-01-01 12:00:00, createdAt is now correctly returned as 2025-01-01T17:00:00Z.

Previously, the responses always converted as if the timezone was UTC−3, which could have impacted organizations configured with other timezones. For example, in database timezone UTC−5, if the recorded time was 2025-01-01 12:00:00, createdAt was incorrectly recorded as 2025-01-01T15:00:00Z (the platform should have added 5 hours instead of 3).

Docs

In the List transaction types endpoint, in the 200 response example, the description field was corrected. One instance of it was previously incorrectly listed as processing_code.

Reports

Docs

The description for Form 1042-S in the table in Reports for the United States was updated.

Banking operations

Docs

The following banking endpoints were renamed to avoid title duplication.

All endpoints in the Banking - Assets > Assets section.

All endpoints in the Banking - Overdraft > Account and Program sections.

The following endpoints in the Transactions banking API.

Transaction banking

Updated

The following fields are now required in the body parameters section of the Create earmark endpoint.

  • account_id
  • external_account_id
  • internal_operation

Updated

The following 400 error message are now available in the following endpoints.

WEAM0047: The payment date cannot be earlier than the account migration date.

WEAM0047: The payment date cannot be earlier than the account migration date WPMT0001: The payment date cannot be earlier than the account creation date

Updated

Two new parameters for back‑value and future‑value dated transactions were added. You can now include these parameters in the metadata of Create administrative division and Create holiday to reject specific back‑value or future‑value dated transactions.

  • reject_back_value_dating
  • reject_future_value_dating

Docs

The table of contents in the core banking guides was reorganized, and each guide is now grouped under its appropriate category.

Authorization

Docs

In the Simulate autnorization endpoint documentation, the following updates were made.

  • The local_currency body parameter was modified so that any currency code can be entered. Previously, it was incorrectly limited to two specific codes.
  • The description for the clearing_s3_path body parameter was updated to clarify the required format.
  • Links were added to the descriptions of the atc and processing_code body parameters.

Cards

New

The new template_id field was added to the Create noname card bulk request. Templates are used to implement the BIN override feature. For more information, refer to the BIN override guide.

New

The following new sections and endpoints are now available.

  • Card issuing - Cards > Mastercard benefits. You can use this section’s endpoints to manage Mastercard card benefits.
  • Card issuing - Cards > CVV rotation. You can use this section’s endpoints to manage CVV rotation intervals.

Cards management

Docs

A new scenario (#6) for reissuing a physical card was added to the Card reissuing guide.

Card network integration

Updated

For transactions declined with Custom Code Z22 (Token suspended), the Merchant Denial Code was changed to 02 (the code was previously 03). This change is reflected in the Validation codes for authorization events guide.

Disputes

New

New fields were added to Visa’s questionnaires and objects for creating a dispute form:

  • oneAuthForMultipleSalesInd was added to the allocation questionnaire. This field takes a Y or N value and indicates whether one authorization was used for multiple sales.
  • merchantAcceptInd was added to the collaboration questionnaire under dispute_due_to = CS (Cancelled merchandise/services). This field takes a Y or N value and indicates whether the merchant has accepted a cancellation.
  • explainCreditIssuedLateDetailsOfNegotiations was added to the collaboration questionnaire under dispute_due_to = CN (Credit not processed). This field is used to explain the credit issued late details of negotiation.
  • merchantRefuseAdvise was updated for the collaboration questionnaire. It no longer supports the MRRA reason.
  • issuerCertifiesCardholderContactedInd was added to the preArbitration object for the Create dispute form endpoint. It takes a Y or N value and indicates whether the issuer has certified the cardholder contact.

New

Three new fields were added to the pre_arbitration object that is returned in the Get dispute and Get dispute installment endpoint responses.

  • acquirer_memo - A string containing a memo from the acquirer included in the Mastercard pre-arbitration rejection response.
  • action - An enum string indicating the network pre-arbitration action,
  • response_date - Date of the network's pre-arbitration response.

Instant payments

Updated

The following endpoints are now outdated:

Protection Bulletin

Updated

The x-customer-id header was removed from the Get Protection Bulletin card and Delete card from Protection Bulletin endpoints.

Reconciliation

Docs

The adjustments parameter is no longer incorrectly flagged as a required field in the Perform clearing reconciliation endpoint.

Statements

Updated

The body parameters accrual_type and processing_code were added to the Post interest accruals endpoint.

Docs

A note was added to the endpoint description for the following endpoints.

Docs

The endpoint description for Update account calendar strategy was updated.

Docs

The [How payments are applied to accruals](doc:how-payments-are-applied-to-accruals was updated in the following ways.

  • The explanation of the Real Due Date was updated to include adjustments for holidays, weekends, and an additional buffer as defined by the program parameter.
  • A sentence in parentheses was added to Scenario 1 of Example 2, Step 3 to cover a complicating factor.

Docs

The title and the text of the last section of Account collection status were updated.

Tokenization

New

The product_type field was added to the Create encrypted card data for Apple Pay endpoint. This field is a product type identifier from the Apple SDK.

Updated

The Visa Click to Pay endpoints are no longer in beta release.

Control Center

Docs

Several guides were updated with information related to setting account limits.

In the Edit programs guide:

  • Added information about setting limits, now located on a dedicated Limits tab on the Program details screen in Control Center.
  • Consolidated program parameter information into this guide, removing the separate parameters guide.

In the Program limits guide, added references to Control Center to clarify when program limits can be managed in Control Center in addition to the related APIs.

Docs

A new list item was added at the beginning of the Get started with Control Center guide - “Create, view, and manage cardholder transaction disputes“.

Docs

In Navigating Control Center, the first paragraph and figure in the Customer operations section were updated to mention disputes.

Docs

The layout and content of the Customer operations guide were updated for consistency with other similar Control Center guides.