Changelog
Sub-processorsAbout PismoContact us
Back to All

3 October 2025

24 days ago by [email protected]

Changes between 5 September and 3 October 2025

Control Center - Exchange rates

New

You can now manage exchange rates in Pismo Control Center. Refer to Exchange rates for more information.

Control Center - Card network tokenization

New

You can now configure card network tokenization in Pismo Control Center. Refer to Card network tokenization for more information.

Control Center - Multi-factor authentication

New

Control Center now gives you more ways to protect your account. In addition to email verification, you can now use authenticator apps and passkeys for a more secure sign-on. Details for setting up additional authentication methods are provided in the Add additional methods for multi-factor authentication (MFA) guide.

Additionally, the Multi-factor Authentication in Control Center (MFA) section of the Security guide for Control Center was rewritten to reflect that MFA is required for all environments and to mention the new authentication options for users.

Control Center - Seller management

New

You can now configure and manage marketplaces, merchants, creditor operations, MDR fees, and settlement schedules within Control Center when you and your org have been granted access to Seller management. The new Seller management in Control Center guide provides an overview of each feature and how to work on those within Control Center.

Restrict funds

New

The restrict funds feature is now live. This feature enables financial institutions to instantly block or restore account fund access—individually or in bulk—based on regulatory, fraud, or client-driven requirements. You can block full or partial amounts in your clients’ accounts either due to request or judicial/regulatory events such as liquidation or receivership. This feature includes four endpoints:

Accounting

Docs

The accounting API documentation was updated for standards.

Migrations

Updated

Now you can pass a zero “0” value for the cvv_rotation_interval if a virtual card does not have CVV rotation requirements when using the Migrate cards endpoint. Note that passing a blank value indicates a 24 hour rotation interval.

Docs

The open_due_date field description in the Migrate accounts (v2) endpoint was updated to provide clarification.

Payments

Updated

The Create cash-in or cash-out endpoint now includes the new original_authorization request field.

Updated

The Platform authorization created event now includes the new merchant object field.

Processing codes

The following standard processing codes were added. In addition, a new TRANSACTION_BANKING tag was added.

  • 219258 HELD FUNDS CASHOUT TRANSFER
  • 219259 UNDO HELD FUNDS CASHOUT TRANSFER
  • 220054 CHECK CASHIN TRANSFER
  • 220055 UNDO CHECK CASHIN TRANSFER
  • 220056 CHECK HOLD FUNDS
  • 220057 UNDO CHECK HOLD FUNDS
  • 220058 CHECK RELEASE FUNDS
  • 220059 UNDO CHECK RELEASE FUNDS
  • 220060 CHECK CASHIN FUTURE FUNDS
  • 220061 UNDO CHECK CASHIN FUTURE FUNDS
  • 220062 CHECK RELEASE FUTURE FUNDS
  • 220063 UNDO CHECK RELEASE FUTURE FUNDS
  • PSM039 CASHBACK
  • PSM041 FUTURE DATED CASHIN TRANSFER
  • PSM042 UNDO FUTURE DATED CASHIN TRANSFER
  • PSM043 FUTURE DATED CASHOUT TRANSFER
  • PSM044 UNDO FUTURE DATED CASHOUT TRANSFER
  • PSM045 RESTRICT FUNDS
  • PSM046 RESTRICT FUNDS CANCEL
  • PSM047 RELEASE RESTRICTION
  • PSM048 RELEASE RESTRICTION CANCEL
  • PSM049 RESTRICTED FUNDS CASHOUT TRANSFER
  • PSM050 RESTRICTED FUNDS CASHOUT TRANSFER CANCEL
  • PSM051 FPS Payment
  • PSM052 FPS Payment Rev
  • PSM053 FPS Payment Rev Canc
  • PSM054 FPS Receipt
  • PSM055 FPS Receipt Rev
  • PSM056 FPS Receipt Rev Canc
  • PSM057 FPS Transfer In
  • PSM058 FPS Transfer In Rev
  • PSM059 FPS Transfer In Rev Canc
  • PSM060 FPS Transfer Out
  • PSM061 FPS Transfer Out Rev
  • PSM062 FPS Transfer Out Rev Canc

Setup

Docs

The following updates were made on the Program parameters guide.

  • A “Category” column was added to the table.
  • The missing program parameter "Overlimit fee amount" was added.
  • The text was updated to explain what it means for a program parameter to be “required”.
  • A note defining “Display name” was added.

Banking operations

New

The following new endpoints are now available:

Docs

Body parameters division_id, interest_by_tiers, and interest_thresholds were incorrectly listed in the Configure benchmark rate endpoint documentation. They were moved to the Create interest plan endpoint documentation where they belong.

Docs

The required header field x-program-id was added to the Create interest plan endpoint documentation.

Docs

The benchmark body parameter of the Create interest plan endpoint has a new possible value:

TO: Overnight Interbank Target Rate (Tasa Objetivo), Mexico

This value can be returned by the Get interest plan and List Org interest plans endpoints.

Docs

In the Create interest plan endpoint, updated the type and tier_calculation fields of the interest_by_tiers object to show the possible values for the enums.

Docs

The “Overwrite account interest” endpoint was renamed to Update account interest.

Instant payments

Updated

For Instant payments - Pix management > Keys > Update key entry > reason, the enum value RFB_VALIDATION has been added. RFB stands for Receita Federal do Brasil and is the Brazilian federal revenue service.

Transaction banking

New

The following new operation block endpoints (v2) are now available. They allow you to block all operations for entire account groups, while still permitting certain authorized activities—such as earmarks or check processing. This ensures that essential internal processes can continue even when most activities are frozen.

New

The check posting API is now available in beta release. It allows you to post a check to a specified external account, with the option to settle the amount immediately or at a future date. This API includes the following endpoints:

Updated

The Post multi-leg payment and Get multi-leg payment status endpoints include several enhancements.

  • multileg_id replaces tracking_id as the identifier for an entire multi-leg payment transaction.
  • Validation and error handling was improved with per-leg options to override or force account status and ledger checks, reducing the likelihood of rollbacks.
  • Custom metadata provided in the request is returned in responses and included in events to support reconciliation and reporting.
  • Instant clearing and earmark support are available for debit and credit legs.

The Multi-leg payments guide was updated to reflect these enhancements.

Docs

The following new guides are now available:

  • Get started with transaction banking provides step-by-step instructions for onboarding to transaction banking.
  • Operation block allows financial institutions to temporarily restrict account activity at the program, division, or organization level.
  • Restrict funds enables financial institutions to block full or partial amounts in their clients’ accounts. This capability is essential in situations where specific funds must be excluded from the general asset pool available to unsecured creditors, ensuring they receive priority handling or special protection.
  • File-based processing allows you to upload UTF‑8 NDJSON files that contain a specific operation type, such as RESTRICT_FUNDS, to execute multiple transactions in bulk. Each file is processed asynchronously, line by line, ensuring that a failure in one instruction does not halt the rest.

Card network integration

Docs

The following new validation codes were added to the Validation codes for authorization events guide and their definitions were added to the Validation code definitions guide as linked below:

Docs

The description for the Network authorization received event was updated for clarification and to indicate the event is for Full balance only.

Cards

Updated

A new validity_period_hours field was added to the Create card, Reissue card, and Create noname card bulk endpoints. This field is for PLASTIC and VIRTUAL cards and allows callers to set how long, in hours, the card is valid. This period cannot exceed the expiration date. These endpoints and the Get cards for customer and account, Get account cards, and Get non-PCI card information endpoints return this field in the response and also return a valid_until field that uses validity_period_hours to calculate the validity end datetime in ISO 8601 format. Two new endpoints were added to manage this field - Renew card validity and Delete card validity period.

As part of this, a new Custom expiration for plastic and virtual cards section was added to the Cards management guide.

Docs

A new Card reissue reissue section has been added to the Card reissuing guide. This section details how to create a new reissue reason via Pismo’s Jira service desk.

Deprecated

The deprecated stage field was removed from Cards API reference documentation.

Disputes

New

There is a new Disputes API section: Card issuing - Disputes > Fraud report. This section contains 4 new endpoints - Create fraud report, Get fraud report, Update fraud report, and List fraud report logs.

New

There are new fee endpoints - Create fee V2 and Get fee V2. A dispute fee is a way for an acquirer and issuer to exchange money outside the normal chargeback process. The V1 fee endpoints were associated with the dispute/installment and the V2 endpoints can only be created with transaction ID (Full balance), transaction information (Zero balance), card ID and customer ID, or NetworkCaseID (VisaCaseNumber). The new endpoints currently support Visa fees, more card networks will be supported in the future.

Updated

New fields were added to the Card issuing - Disputes > Disputes > Update dispute endpoint’s request and response. Added to the request are transaction_amount, transaction_date and arn. Added to the response are transaction_amount, transaction_date, and currency_code.

Statements

Updated

The following event files were updated and moved to the appropriate Statement refinancing section.

Updated

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

  • New body parameter presentToPast was added.
  • Descriptions of startFromCurrentCycle and presentToFront were updated.
  • Endpoint description was updated to explain how startFromCurrentCycle, presentToFront, and presentToPast work together.

Updated

The withStatements query parameter was added to the List transaction balances endpoint. When this parameter is set to true, a statement object field is included in the items array of the 200 response.

Docs

An alert message was added to the introductory section of Credit liquidation to explain that once an account has been through the CRELI process and closed, it cannot be reopened.

Docs

The Accrual status changed event documentation was updated with added field titles, updated most of the field descriptions, and other minor changes.

Docs

A new guide Accrual status changed event flows is now available. It explains how to interpret the “Accrual status changed” events based on the value of their account_status field.

Docs

A note was added to the description of the Configure features by account status endpoint explaining that if the status is set to bypass the billing cycle closure and the account reaches that status, it cannot revert to a previous status.

Docs

The description of the total_due_amount field in 200 response for the Get statement endpoint was corrected. The original description said that the field did not include debits from previous statements. It should have said that it only includes debits from previous statements.

Docs

In the Create transaction category endpoint, the descriptions of the following body parameters were updated:

  • default_rate
  • overdue_rate_after_due_date
  • refinancing_rate_after_due_date

Docs

The Over-limit fees guide was rewritten and reorganized to fix some inaccuracies and add clarity.

Docs

The missing strategy field was added to the FIXED CYCLE CLOSING STRATEGY object in the Create program calendar strategy endpoint.

Lending

New

The new List account loans endpoint is now available. It enables you to list all loans belonging to a customer account.

Merchants

Deprecated

The following endpoints were marked as deprecated and are scheduled to be removed 8 October, 2025. Refer to API endpoint deprecation and removal schedule for the full deprecation schedule.

Pismo Control Center

Deprecated

Disputes management documentation was removed from the Control Center documentation. This feature is not released in Control Center yet and documentation for it was posted erroneously earlier.

Docs

A new section, Assign roles in Control Center, was added to the Get started with SSO for Control Center guide. This new section describes role mapping and explains how to map and assign user roles in Control Center. Control Center users can be assigned to multiple roles, each with different permissions. If you have multiple organizations, you can assign your users to different roles for each organization.

Docs

Directions for logging in were added to assist if you don’t get the welcome emails.

Postman

Docs

The following Postman developer guides were updated to adhere to documentation standards.