Changelog
Sub-processorsAbout PismoContact us
Back to All

6 February 2026

4 days ago by [email protected]

Changes between 9 January and 6 February 2026

Control Center

New

The dual approval feature was updated in Control Center. You can now request Pismo to enable dual approval for creating or deactivating access keys and creating, editing, or deactivating OpenID authentication configurations.

Lending

New

The new Cancel loan V2 endpoint is now available in beta release. The endpoint introduces loan cancellation functionality with the following enhanced features.

  • New request/response schemas with support for configurable processing codes and metadata
  • Comprehensive error handling
  • Supporting schemas for loan cancellation processing codes and refund options

Core banking - Transaction banking

New

The Dormancy reactivation exception guide is now available. It describes the enhanced feature that allows you to use the reactivation_exceptions_config object to specify values that bypass the standard dormancy reactivation logic.

Client webhooks

Docs

The response field merchant_denial_code was added to the Full balance anti-fraud webhook section of the Client webhooks guide. This previously missing field was added to the Response fields list and to the Sample response.

Docs

A duplicate request field, cardholder_postal_code, was removed from the Zero balance validations webhook section of the Client webhooks guide. This duplicate field was removed from the Request fields list and from the Sample request.

Flexible transaction controls

Updated

In the flex controls endpoints, in the conditions object, the attribute enum field now has a new value - avr - which indicates that the transaction is a card network Account Verification Request (AVR) transaction. The avr field is now also available in the Evaluation requested event, object.request field.

Migrations

Docs

The Migrate cards endpoint documentation was updated to remove incorrect fields within the migration object.

Payments

Updated

The requirements for the following fields in the Request authorization endpoint were impacted and their field descriptions were updated accordingly.

  • amount
  • original_authorization_id
  • original_tracking_id
  • processing_code

This impact occurs if the mti is equal to 0202 (confirmation request) or 0402 (confirmation of cancellation request) and the force original authorization is enabled in the payment method configuration or acceptance as follows. 

"ORIGINAL_AUTHORIZATION": {  
        "force": true  
      }

Updated

The new Payment methods multiple transfers completed event is now available. It occurs when the Pismo platform completes a multiple transfer process which moves funds between multiple accounts. This event was also added to the Payment scheduler guide and the guide that lists payments data events.

Docs

Documentation for the payments scheduler events was updated to remove [beta] tags, update field descriptions, and remove internal events. Additionally, the guide that lists payments data events was updated with the list of payment scheduler events.

Programs

Docs

Information about programs and creating programs from a template in Control Center was reorganized and clarified.

Rates and fees

The Fee models guide was reorganized and updated. The “Fee models methods” section was renamed to “Creating a fee model” and updated with additional information. The “Processing codes” section was moved after the “Creating a fee model” section.

Transactions

Updated

In the List transactions endpoint, if you provide at least one of the following parameters, the eventDateStart parameter is now optional.

  • id
  • authorizationId
  • authorizationIds
  • statementId
  • authorizationTrackingId
  • numberOfLatestTransactions

If you don't provide any of the above parameters, you must include the eventDateStart parameter, and the maximum allowed query range is 90 days.

Docs

Documentation for the transaction types events was corrected to remove duplicate and internal events.

Docs

The Transaction types guide was updated for documentation standards.

Support

Docs

The Pismo platform sub-processors page was updated to include support for AWS Australia.

Events

New

The new Bank statement cycle closing completed event is now available. This event indicates that a bank statement cycle closing has been completed for a specific target, such as an organization, program, or division.

Reports

Docs

The Regulatory scheduled reports guide was updated according to standards.

Docs

The Notes column was added to the table in Reports for Brazil.

Banking operations

Updated

In the Create deposit product endpoint, a new enum value FIXED was added to the withdrawal_fee object.

Updated

The AuthorizationToken account‑token parameter was removed from the following affected endpoints, as these endpoints support only bearer‑token authentication.

Docs

The Interest-bearing accounts guide was updated to reflect the latest information.

Docs

The Prospect creation service was renamed to Prospect management service in the Banking overview guide to reflect its expanded functionality, which now includes updating and deleting accounts.

Instant payments

New

The new Instant payments - Pix management > Anti-fraud > List fraud markers endpoint is now available in beta release.

New

The following new endpoints are now available in beta release in the Instant payments - Faster Payments (UK) API.

Updated

The new psp_account object was added to the Pix-out transfer endpoint. This field is required if transaction_type = REFUND. It provides information about the Payment Service Provider’s (PSP) account.

Updated

The new funds_recovery_id query parameter was added to the following Instant payments - Pix management endpoints:

The same parameter was removed from the Get infraction report endpoint.

Docs

The Pix Automatic guide was updated with more information about journeys, payment orders, and recurrence use cases.

Interest management

Updated

The x-program-id header is no longer required in the Create interest plan endpoint.

Transaction banking

Updated

The following error code was added to the List hierarchies endpoint to set a maximum cursor value for results that the endpoint can return.

  • WCMN0006: Limit must be less than or equal to 100

Docs

The following note about processing sequence was added to the Post multi-leg payment endpoint documentation.

Processing sequence: Debit legs are always processed before credit legs. Within each group, the sequence is not guaranteed, and the order of execution among debits or among credits is non‑deterministic.

Docs

Two balance types were added to Account balance definitions for transaction banking.

  • Accrued remunerative interest (remunerative_interest_accrued): This is the total interest amount that has accrued but has not yet been capitalized.
  • Held checks balance (held_checks_balance): This is the balance from checks that the bank considers available but temporarily holds in order to earn interest.

Authorizations

Updated

The obsolete parameter use_anti_fraud_api was removed from the following endpoints.

Network authorizations

Docs

The Network authorization received event was updated to correctly reflect the title for the Token information ID as “Pismo-created token ID”.

Statements

Updated

The following endpoints that were previously available in beta release are now available in production.

Updated

The word “informed” was replaced with “provided” in some of the 4xx error messages for the following endpoints.

Updated

In the List program due dates endpoint, the query parameter dueDay was renamed to day The original name was incorrect.

Updated

The following parameters were added to Multivalue program parameters. Note that they are in beta release and are not yet available on the public server.

  • 512 - PAYMENT_AGREEMENT_SIMULATION_INTEREST_CAP_ENABLED
  • 513 - PAYMENT_AGREEMENT_SIMULATION_FIRST_INSTALLMENT_AS_DOWNPAYMENT
  • 514 - PAYMENT_AGREEMENT_SIMULATION_ENABLED

Additionally, the following parameter that was previously missing was now added to the guide.

  • 501 - DELINQUENT_ACCOUNT_CLOSURE_PROCESSING_CODE

Docs

The contract_condition field was added to the contracts array in the body params for Create installment advancement (V2). This field was missing in the original documentation. Also, the REQUIRED label was removed from the number_of_installments field in the contracts array. This field is only required if contract_condition is set to SPECIFIC_NUMBER_OF_INSTALLMENTS.

Docs

The following guides were updated for standards.

In addition, Creating and configuring a Full balance credit program was moved into a separate guide.

Docs

The body parameters default_rate and rate_if_overdue in the Configure program accrual rates were incorrectly listed as required. One or the other is required, but not both. The documentation was updated to reflect this.

Docs

The “transaction category” was renamed to “program transaction category” and their descriptions were updated to avoid confusion with “account transaction category” in the following endpoints.

The “Interest rates” menu section was renamed to “Account transaction categories” and the following endpoints in that section were renamed and their descriptions updated.

The text of the following guides was renamed to use “program transaction category” and “program transaction categories”.

Merchants

Docs

The How merchant settlements and installments are processed guide was updated for standards and clarity.