Changelog
Sub-processorsAbout PismoContact us
Back to All

4 September 2026

25 days ago by [email protected]

Changes between 7 August and 4 September 2026

Core platform - Accounting

Docs

The Create accounting scripts guide was rewritten to provide more information and payload examples and to explain new features introduced with accounting scripts v2.

Control Center

New

Copy configurations feature is now available in Control Center. This feature helps you reuse existing configurations across Control Center environments, removing the need to recreate them manually. You can copy configurations between environments to:

  • Promote changes from sandbox to production
  • Keep environments aligned
  • Restore earlier versions when needed

Copy configurations is currently available for holiday calendars, with support for more features planned.

Card issuing - Statements

Docs

A new guide Discharging transactions—Default process is now available. This guide explains the default discharge process, which is the only process currently in production. A link to this new guide was added to Discharging transactions.

Flexible transaction controls

Updated

The Flex controls API was updated in the following ways.

  • New response fields available_amount and available_transactions are now available in all account and customer flex controls endpoints. These fields track the remaining amount and number of transactions for cumulative_limit controls.
  • The list of attributes for conditions was expanded and clarified, specifying which are valid only for card network operations and adding detailed explanations for each. This includes new guidance on using is_physical_card_present and is_token_present together to distinguish digital wallet transactions.
  • Field descriptions for max_limit and available_limit were updated to clarify their meaning for different control types (spending_limit, usage_limit, and cumulative_limit).
  • The reset_datetime field was removed from the list of request parameters and its description was clarified to indicate that this is a response-only field and to explain how it's calculated.
  • Field descriptions for currency_code, reset_strategy, customized, max_transactions, max_amount were updated and clarified throughout.

Ledger

Docs

The Available ledger balance changed event documentation was updated to reflect the correct placement of the impact_accounts field and to clarify its description. This field is deprecated and scheduled to be removed. It is only populated in specific situations when there are associated accounts in the operation.

Migrations

Docs

In the Migrate authorizations endpoint, merchant_city, merchant_name, and merchant_state_or_country are now defined as optional fields (previously shown as required in error).

Docs

In the Migrate transactions endpoint, "INSTANT PAYMENT" references were removed from the type field description.

Docs

The Statement organized migration completed event can now be emitted after the organize-statement flow runs during a migration. This is useful for historical visibility, reconciliation, and financial validation.

Docs

The merchant_state_or_country field in the Migrate authorizations endpoint was updated to indicate a string with length ≤ 3, described as "Merchant state or country using ISO 3166-1 alpha-2 or ISO 3166-1 alpha-3 country code," reflecting support for both 2- and 3-letter country codes.

Programs

New

A new card network brand - GPN - was added to the brand parameter for the following endpoints.

Updated

The holiday_calendar_id and cycle_closing fields were removed from the following “Platform setup - Programs” endpoints.

Support

Docs

The Confluent event configuration tutorial was enhanced in the following ways.

  • Added a Service Desk ticket template for Kafka topic provisioning, bootstrap server information, API key generation, and secure token file setup.
  • Documented Service Desk routing requirements.
  • Reorganized the Confluent event configuration tutorial into a quick-guide format to streamline onboarding and event configuration.

Transactions

Updated

In the following endpoints, parameters pageSize and pageOffset were updated and field descriptions on each endpoint were updated accordingly.

pageSize is now allowed up to a maximum of 1000 records per page. If the pageSize parameter is not passed, the platform continues to consider pageSize = 100 as the default.

pageOffset is now allowed up to a maximum of 5000 records per page. If the pageOffset parameter is not passed, the platform continues to consider pageOffset = 0 as the default.

Docs

In the Transactions overview guide, the note about installment purchases was updated to clarify that this payment method is available for transactions only within Brazil.

Security

Updated

The webhook lookup URL for retrieving public keys was updated in the Verifying webhook requests guide. You must use this updated URL to retrieve the current list of public keys from our JSON Web Key Set (JWKS) endpoint at the time of verification of the webhook requests sent by the Pismo platform. This ensures that your system always uses the correct key, even when scheduled rotation of the cryptographic keys used to sign webhook request tokens occur.   

Setup

Updated

In the Update filter template endpoint, the 204 response was changed to 200 response that returns the updated filter template.

Docs

The URL paths in the balance configuration filter template endpoints were corrected (/balances-configs/ replaced with /balances-config/).

Events

New

The following new events that feature a required external_account_id are available in beta release.

Docs

The Corporate account created event that was incorrectly documented in the Core platform > Accounts section was removed from documentation. In the Banking - Transaction banking guide, a reference to this non-existent event was updated to point to the correct Corporate account created event.

Banking operations

Updated

The grace_period_duration_days and accrue_during_grace_period fields were added to the following endpoints. These two fields introduce the product‑level setting that determines whether interest accrual continues during the post‑maturity grace period.

Updated

In the Update deposit account attachment endpoint, the maturity_period object was added to the deposit_configs object. This field enables immediate term recalculation through maturity_period, updating the current cycle’s maturity date from a relative period or explicit date.

Updated

The external_account_id field was added to the 200 response for the following endpoints.

Updated

The accrual_model field was added to the 200 response for the Get average balance and Create savings account product endpoints.

Updated

In the Configure timing for accrual calculation endpoint, an additional time, 04:05, was added to the list of times that are accepted by the time_utc field.

Updated

The incorrect and missing error codes were corrected in the Open deposit account endpoint. The following error codes were incorrect and were updated.

400 errors:

  • EIBACC0321 was updated to EIBACC0330: Corporate API validation error and a details‑field example was added showing that the underlying WCAC error code already appears there.
  • EIBACC0407 was updated to EIBACC0331: Provided account_id does not match the resolved external_account_id.

504 error:

  • EIBACC0318 was updated to EIBACC0329.

The following 400 errors were added to provide more details.

  • EIBACC0018: Accounts API - Request returned error 4xx
  • EIBACC0065: Product Type is not valid
  • EIBACC0103: Programs API - Request returned error 4xx
  • EIBACC0107: Informed program or account already has an attached product
  • EIBACC0109: Maturity period is below the configured MinTerm of the product
  • EIBACC0110: Maturity period is above the configured MaxTerm of the product
  • EIBACC0236: Product cannot be attached before its start date
  • EIBACC0284: Payout account is configured but is invalid
  • EIBACC0298: Validation error (details: Invalid maturity_period unit. Supported values: DAYS, WEEKS, MONTHS, YEARS)
  • EIBACC0299: Validation error (details: maturity_period value must be a positive integer (>= 1))
  • EIBACC0303: New attachments are not allowed after the deposit product end_date
  • EIBACC0305: Validation error (details: calendar_maturity_date must be in YYYY-MM-DD format)
  • EIBACC0306: Validation error (details: calendar_maturity_date must be a future date (after today))
  • EIBACC0307: Validation error (details: maturity_period accepts either calendar_maturity_date OR unit + `value, not both)
  • EIBACC0308: valid_until must be a future datetime
  • EIBACC0319: Effective date exceeds maximum backdating limit
  • EIBACC0320: Invalid effective date format. Expected YYYY-MM-DD
  • EIBACC0321: Effective date cannot be in the future

The following 422 errors were added:

  • EIBACC0191: Account status is not NORMAL and it is unprocessable
  • EIBACC0297: Program is not valid for attachment. Program must be DEBIT type and ACTIVE status

Two missing 500‑level errors were added:

  • EIBACC0328 : Corporate API request error
  • EIBACC0324 : Failed to unmarshal Corporate API response

Updated

Interest bearing accounts now support two accrual models for submitting data to the interest engine.

  • DEPOSIT_BASIS uses the balance change model, where interest is computed from movement‑level changes and remains the default.
  • BALANCE_BASIS uses the closing balance model, submitting the account’s closing balance on each cycle_closing event. Under balance basis, balance_type determines which balance is submitted:
  • VALUE_DATED_BALANCE provides the cleared, value‑dated balance (default)
  • LEDGER_BALANCE provides the raw ledger balance

This update impacts the following endpoints.

Instant payments

Updated

The interval and type parameters were removed from the List scheduled Pix transfers endpoint.

Updated

A new sort_code_validation object was added to the response from the Confirmation of payee endpoint. This object returns the results of sort code and account validation.

Updated

A response object with 3 fields was added to the 200 return from the Pix Automatic’s Cancel recurrence endpoint. For example:

{
  "recurrence_id": "RN2199525620260901XIQf6272qzA",
  "reason_code": "SLDB",
  "cancelled_at": "2026-09-01T20:25:14.402Z"
}

Payment rails

New

The Payment rails - BACS payments API was reorganized into two sections - BACS direct credit and BACS direct debit. In addition, two new endpoints were added - Amend BACS paper mandate and Cancel BACS paper mandate. A BACS paper mandate is a physical, signed authorization form that allows a UK organization to pull recurring or single direct debit payments directly from a customer's bank account.

Instant payments

Updated

A type field was added to the response from the List payment orders endpoint. This enum field identifies the payment order’s type.

Transaction banking

New

The following new channel endpoints are now available.

Updated

A new 400 error WCPT0018: Account has not finished onboarding was added to the following endpoints. This error is returned when a client attempts to create, release, or cancel a check while the external account is still undergoing onboarding.

Updated

New fields type and increase_datetime_limit were added to the following endpoints, enabling regulatory and judicial reasons to be used when calling fund restriction endpoints.

Updated

A new hold method, RECURRENT, is introduced to the following endpoints, applying the restriction to each incoming credit until the target amount is reached or the increase_datetime_limit occurs.

Updated

A 423 Locked error message, Earmark locked by a concurrent operation, was added to the following endpoints. This error is returned when another earmark or payment operation is already in progress.

Deprecated

The following endpoints were decommissioned on 6 August 2026 and removed from the Transaction banking API.

  • Post float cash-in (Pismo account ID)
  • Settle float payment

Authorization configuration

Docs

The Get authorization by organization and Get authorization by account endpoints are both now back on the Developers Portal after being mistakenly removed.

Card network integration

Updated

The network field of the Card network authorization return sent event was updated to properly list the valid network options: mastercard, visa, visa_vcc, tecban, rupay, and elo.

Docs

The Visa Consumer Authentication Service (VCAS) guide was updated to properly distinguish the one-time password (OTP) as one option of the overall Step-up validation.

Docs

The Verify authorization decline reason for Zero balance transaction definition in the Validation code definitions guide was updated to reflect the correct field name as custom_response_code and not CustomCode as previously listed.

Cards

Deprecated

The deprecated Create combo card endpoint was officially removed from the Developers Portal. An entry for the endpoint has been added to the API endpoints removed page.

Protection Bulletin

The bid field used in creating a Protection Bulletin rule for Visa has had its length extended from 6 digits to 11 digits. The Business ID (BID) number - is a six to 11 digit account number through which Visa bills their clients.

Statements

Updated

The following fields were added to the Simulate installment advancement endpoint.

  • authorization_id field in the response object
  • id field in the installments array in the response object
  • interest_removal_end_date field in body parameters and response object

The interest_removal_end_date field was added to body parameters of the Create installment advancement.

Docs

A list of restrictions was added to the Canceling an installment advancement section of the Installment advancements guide.

Docs

A link to Update multivalue program parameter values was added to the first paragraph of Multivalue program parameters.

Docs

In the Understanding statements guide, the following updates were made.

  • The “Statement management” callout at the end of the “Balances” section was deleted. It was replaced by the "Statement management" section near the beginning of the guide.
  • The “Accrual management” callout at the end of the “Accruals” section was deleted. It was replaced by the "Accrual management" section within the “Accruals” section. The new section provides a few more details than the callout.

Docs

In the first sentence of the Credit card refinancing guide, the word “payments” was changed to “billing periods”, which is more accurate. The following sentence was added to the end of the introductory section to clarify the purpose of the included figure: “If necessary, refer back to this figure when reading the guides linked to in the following sections.”

Docs

The field descriptions for fixed_interest_rate, margin, and margin_rate were updated in the following endpoints.

Deprecated

The following installment advancement endpoints are now deprecated.

The API endpoint deprecation and removal schedule was updated accordingly.

Docs

The following updates were made for clarification.

Docs

The description for the DELINQUENT_ACCOUNT_CLOSURE_DAYS program parameter was updated in the Multivalue program parameters guide.

Docs

The descriptions for the minimum payment calculation methods were clarified in the table in section Minimum amount due calculation.

Docs

The section header was renamed from “Full-amount transactions” to Setting the transaction in a category to full-amount and the text was updated for clarity.

Docs

The Strategy 2 examples section was updated to correct some inaccuracies.

Lending

New

The new Cancel all loans by account endpoint is now available.

Updated

The Simulate early final settlement endpoint was updated to remove the Idempotency-Key header.

Updated

The Restructure a loan endpoint returns an asynchronous tracking_id, not a new loan_id, so the endpoint response body was updated accordingly.

Updated

The List account loans endpoint now shows disbursement details for a loan that has MULTIPLE disbursements that include the following fields.

  • can_disburse_more—On a MULTIPLE disbursement loan, is the remaining amount to be disbursed greater than zero?
  • remaining_to_disburse_amount—On a MULTIPLE disbursement loan, the amount that remains to be disbursed. Calculated as loan_principal_amount minus total_disbursed_amount.
  • total_disbursed_amount—On a MULTIPLE disbursement loan, sum of all active disbursements, excluding any that are CANCELED or EXPIRED.

Updated

The Cancel loan endpoint now shows canceled_loans and total_to_be_canceled with summary information about the canceled loan or loans.

Updated

The List account loans endpoint now shows insurance_summary information. When you set the includeInsuranceHistory=true query parameter, each insured installment in repayment_schedule includes an insurance_premium_state field, and the response includes loan-level insurance_summary for loans that have an insurance policy. Also the response includes cancelled insurance and its installments. (The field is omitted entirely for uninsured loans.) The insurance_summary includes the following information:

  • insurance_ever_active—Was insurance ever collected in the history of the loan?
  • last_covered_date—End of insurance coverage period, either the last installment due date or the insurance cancelation date for a canceled policy.

Docs

The Lending prepayment or group payment created event was updated to indicate that the event is sent when a lending prepayment or group payment has been created. Previously the event indicated only “Lending prepayment created” in the title.

Docs

Multiple Lending API request fields, headers, path parameters, and query parameters were updated with better descriptions of the meaning of the field.

  • Idempotency-Key headers
  • loanId path parameter
  • accountId path parameter and query parameter
  • loan_id
  • loan_start_date
  • account_id
  • account_type
  • sortOrder query parameter for List loan products

Marketplace

Docs

The additional_phone_number field description in the Create marketplace V3 endpoint was updated to include that the additional phone number value should be of the E.164 format, which includes a max length of 15 characters.

Merchants

New

The List merchant advancement requests endpoint was moved from /v1/merchants/{merchantId}/advancements to /v2/merchants/{merchantId}/advancements. This avoids a routing collision with the still-active legacy /v1 endpoint served by the Merchants API, letting both versions run side-by-side during the migration window.

Control Center

New

The new pending transactions feature was added to Control Center. You can now view the list of pending transactions for an account and explore individual pending transactions in more detail.

Updated

The audit feature in Control Center now supports exporting the audit logs. The guide was also updated to align with Pismo documentation and style standards.

Updated

The transactions feature was updated in Control Center. You can now view the list of pending transactions for an account and explore individual pending transactions in more detail.

Updated

The Control Center Loan products and Create loan products guides were updated to:

  • Reflect support for creating both personal loans and Buy Now, Pay Later (BNPL) loans in Control Center. Previously, Control Center supported only BNPL loan creation.
  • Add more detailed information about creating processing codes, a prerequisite for creating loan products.

Updated

The Dual approval feature was transitioned from beta to full release. The following guides were also updated to reflect this.

In addition, the dual approval feature in Control Center was updated. You can now request Pismo to enable dual approval for issuing a refund.

Docs

The Control Center Holidays guide was updated to align with Pismo documentation and style standards.