Changelog
Sub-processorsAbout PismoContact us
Back to All

5 September 2025

22 days ago by [email protected]

Changes between 8 August and 5 September 2025

Banking

New

The Overdraft API is now live. This API allows a bank to authorize a bank account for an allowable overdrawn limit to cover its debit transactions when the balance is insufficient.

The new How overdraft works guide explains this functionality.

Control Center - Balance configurations

New

We’re pleased to offer you program-level balance configurations in Control Center. Balance configurations are a flexible set of rules that define how account balances and limits are impacted based on transaction activity. Use balance configurations to proactively manage risk, encourage responsible spending, and deliver personalized experiences to your customers. Refer to these new guides to learn more:

Control Center - Dual approval

New

We’re excited to announce that dual approval is available in Control Center (beta release), adding a layer of oversight to critical processes. Dual approval is a security and governance feature that requires two separate individuals to review and approve a critical action or data change before it's finalized. One person initiates the request and a second person reviews and approves it. This process helps to prevent errors and unauthorized changes and reduce fraud.

Your company must opt-in to use dual approval. It's available for these Control Center processes:

  • Edit a program parameter
  • Make a single adjustment to an account

To learn more about dual approval, refer to Dual approval. To join the beta program, contact your Pismo representative.

Client webhooks

Updated

The following changes were made to the request fields in the Full balance anti-fraud webhook.

  • A new field, additional_data, was added under the validation_results object. This optional field contains important additional information related to the validation.
  • The unused field id_last_referral_unlock_date was removed.

Docs

The following updates were made to the request fields in the Full balance anti-fraud webhook.

  • An incorrect duplicate of the cvv_data field was removed.
  • The unlock_date field is now correctly defined as a string.

The following update was made to the results fields in the Zero balance validations webhook.

  • The description for available_credit_limit was updated to indicate that the result is for either Balance limit for processing code 30 (balance inquiry) or for Voucher authorizations - account_type 70.

Flexible transaction controls

Updated

The description for the week_day attribute in the flex controls endpoints was updated to specify that this is a day of the week when the operation occurs and that the valid values use the full lowercase weekday name: sunday, monday, tuesday, wednesday, thursday, friday, saturday.

Merchants

Docs

The descriptions of the following endpoints were updated to more accurately reflect the attributes and indicate which fields are required:

Transactions

Updated

The Transaction created and Transaction updated events now include the created_at field.

Security

Docs

A note indicating the access token expiration time of 10 minutes was added to the Basic authentication with client credentials guide for clarity.

Docs

A new security guide has been created for Authentication with OAuth2. The Pismo platform supports OAuth2 authentication using stored credentials. This new guide explains how to obtain access tokens using the Client Credentials grant type.

Docs

Guidelines on how to request mTLS support for webhook requests were added in the Verifying webhook requests guide.

Setup

Updated

The display name of the program parameter “Indicates whether the cycle opening event should be sent to the first cycle” was changed to “Send cycle opening event when first cycle is created” in both Control Center and the Program parameters guide.

Docs

The [beta] tag was removed from the balance configurations documentation. The new Balance configurations data events guide lists balance configurations data events.

Docs

The description of the "Accrual calculation strategy" program parameter was updated in the Program parameters and Calculating interest accruals guides.

Events

Updated

The unused field anti_fraud_url was removed from the Network authorization received event.

Instant payments

Updated

There is a new field - type - returned in the Instant payments - Pix payments > Automatic Pix > List payment orders endpoint response. This is the payment order’s type as a translation of the type coming from Brazil’s Instant Payments System (SPI).

Updated

  • The perPage parameter is no longer required for Instant payments - Pix payments > Automatic Pix > List recurrences.
  • The status and perPage parameters are no longer required for Instant-payments > Pix payments > Automatic Pix > List recurrence authorizations.
  • The recurrenceId and perPage parameters are no longer required for Instant payments - Pix payments > Automatic Pix > List payment orders.

Updated

For the Instant payments - QR Code > Recurring payment endpoints, the retry boolean field in the recurrence object has been renamed to allow_attempts_after_expiration. Its functionality, indicating whether to allow transaction retries after failure, remains the same.

Transaction banking

Updated

A new validation error message: WEAM0040: The payment date cannot be earlier than the account creation date was added to the following endpoints. This validation error occurs when you specify a earmark payment date that is earlier than the account creation date.

Updated

Three new fields are now available in the Get account balance history endpoint. The purpose of these fields is to enable accurate interest accrual on accounts with positive balances, the balance history logic is updated to track daily net changes in balance.

  • credit_movement: Represents the total of all credits processed during the business day. Always expressed as a positive value.
  • debit_movement: Represents the total of all debits processed during the business day. Always expressed as a positive value.
  • net_movement: Is the change in an account’s balance between two consecutive business dates.

Updated

The following new query parameters are now available the List earmarks endpoint. These parameters allow you to query earmarks whose balances are greater than, less than, or equal to the specified amount.

  • balanceGt: Filters earmarks whose balance exceeds the specified amount.
  • balanceGe: Filters earmarks with a balance greater than the specified amount.
  • balanceLt: Filters earmarks with a balance less than the specified amount.
  • balanceLe: Filters earmarks with a balance less than or equal to the specified amount.

Authorization configurations

Updated

The use_anti_fraud_api field was removed from the Authorization configurations API because it is no longer necessary to send this field. The parameter list in the Authorization configurations guide was updated and the field was replaced with disable_dcc in the code samples in the Run the configuration requests guide.

Docs

The following updates were made to the Authorization configurations guide:

  • The bypass_card_status_canceled field was removed from the parameter list because it was a temporary field that was unused.
  • The four previously undocumented fields were added to the parameter list: days_to_cancel_pre_authorization, days_to_cancel_pre_authorization_migration, days_to_cancel_authorization_migration, and always_call_ledger_rules.

Card network integration

Updated

A new custom code, 91 - Authorization system or issuer system inoperative, was added to the Validation codes for authorization events guide. Validation code 91 is returned when the authorizations or route is not available, such as when the issuer host is unavailable, unexpected disconnection, or any unforeseen/platform-mapped error. The new validation code was also added to the Validation code definitions guide.

Docs

The new Card network mandates guide is now available. Card network mandates are rules, requirements, and deadlines that govern how banks, merchants, processors, and service providers must operate in their payment ecosystems. This guide provides a general overview about these mandates with a FAQ about how they are handled on the Pismo platform.

Disputes

Updated

The Card issuing - Disputes > ELO section has been removed. It contained 3 endpoints: Create authorization fraud report, List authorization fraud reports, and Count authorization fraud reports.

Statements

New

The following new endpoints are now available.

Docs

Two values in two of the tables in Delinquency buckets were corrected. $54.97 was changed to $54.96. 2, and $113.99 was changed to $113.98.

Docs

The transaction_category_id body parameter was marked as required in the Configure account transaction category rates endpoint documentation. It was already a required parameter—the documentation was updated to reflect that.

Docs

The description for the Cancel account transaction category endpoint was updated to clarify what happens to the rates when an account transaction category is canceled.

Docs

Many details in the Minimum amount due calculation guide were clarified.

Docs

The description of the body parameter reversal_projection_processing_code in the Create an accrual type post configuration endpoint was updated to clarify when it’s used.

Docs

The description of the split_iof body parameter of the Create payment agreement endpoint was updated.

Docs

The “Transaction categories” section of How the program uses configurable entities was updated.

Docs

The last sentence in Transaction categories was changed to link to a different guide.

Docs

The definition of “account transaction category” in Transaction category structure was modified.

Docs

The description of open_due_date in Account was updated to clarify how it differs from the statement due date.

Docs

The description of the type field in the table in the Accounts balances report files guide was updated and definitions for the possible values were added.

Docs

The description of the payment_datetime field was updated in the following endpoints:

Merchants

Docs

The Managing merchant transactions guide is now available. This guide describes how to create, cancel, retrieve transactions for a single merchant, and how to split transactions across multiple merchants.

Control Center

Docs

The Get started with Control Center was updated to include directions for users logging in with single-sign on. Also, troubleshooting guidance was added for users who don’t get the login emails.

Docs

The new section Resend login emails was added to the Create and edit users guide.