6 June 2025
Changes between 2 May and 2 June 2025
AI-powered search
New
Introducing the new AI-powered search—faster, smarter, and with deeper insights. Our more comprehensive search delivers instant responses plus direct links to related content. Need code? Copy snippets straight from the results with a single click.
Card issuing - Visa Flexible Credentials
New
Pismo now offers Visa Flexible Credentials, which allows a single card to access multiple funding sources as backup during transactions. A new VFC API and guide were published to support this feature.
This feature is currently in beta release to give you a chance to check out its functionality and provide feedback. Its functionality might change before being released to production. Contact your Pismo representative for more information or to participate in the beta program.
Core banking - Instant payments
New
Pismo now supports Pix Automatic, a Pix feature designed for recurring payments, such as gym memberships and rent. This includes new Pix Automatic endpoints for creating a recurring transaction, getting a recurring transaction, listing recurring transactions, cancel a recurring transaction and authorize or reject a recurring transaction.
This feature is currently in beta release to give you a chance to check out its functionality and provide feedback. Its functionality might change before being released to production. Contact your Pismo representative for more information or to participate in the beta program.
Client webhooks
Updated
A new request field, card_metadata
, was added to the Zero balance validations webhook. Both the request fields table and the sample request were updated with this new field.
Flexible transaction controls
Docs
On the Create account flex control page, the limit_duration
field is not longer marked as required.
Migrations
Docs
The Migrations overview guide was expanded and revised with more details about migrating different platform entity types.
Payments
Updated
In the Payment configurations API, the new fields confirmation_verification_mtls
and confirmation_verification_mtls_prefix
are now available.
Docs
In the Platform authorization created event, most fields were updated with the minimum and maximum length values and the description of the validation_results
field was updated with the link to the corresponding guide that lists all possible validations.
Docs
In the Create cash-in or cash-out endpoint, the links for the endpoint to create processing codes were updated.
Docs
In the Payment scheduler [beta] guide, information about creating a pre-schedule was corrected. Instructions to contact Pismo representative were removed and instructions to set the Post the pre-scheduled transactions when the cycle closes
program parameter were added.
Setup
Updated
The new program parameter Overdue strategy start
was added to the table in Program parameters.
Docs
The endpoint descriptions for Create program and Create program (async) were updated to clarify that neither endpoint generates an event.
Docs
- The description for the Change due date endpoint was updated. A note was added that the due date must be updated no later than two days before the cycle closes, otherwise it will not function properly.
- A similar note was added to the description of the Update statements calendar endpoint, explaining that the calendar must be updated no later than two days before the cycle closes to function properly.
Docs
A callout in the Program parameters guide was corrected. It originally stated that you could look up program parameter IDs in Control Center. This was not correct. You have to use an endpoint.
Events
New
Under Core banking, the new section Credit rights now includes the following new events.
- Contract digital receivable supplement created
- Contract digital receivable supplement creation failed
- Digital receivable create succeeded
- Digital receivable create failed
- Contract create success
- Contract create failure
- Digital receivable unit contract create success
- Digital receivable unit contract creation failed
New
The following new events are now available.
Reports
Updated
Brazilian reports were updated to put reports in alphabetical order by name in the Report column. Two new reports were added:
- APIX 001 - 1201
- COSIF 4111
The “National Transactions 6308 Report“ report was renamed to “6308 Payment Card Report”.
The entry for “SVR (Sistema de Valores a Receber / System of Receivables): [9800] and [9805]” originally covered two reports: 9800 and 9805. These have been separated into 2 entries in the table: “SVR 9800 (Sistema de Valores a Receber / System of Receivables)” and “SVR 9805 (Sistema de Valores a Receber / System of Receivables)”
Banking as a Service
Updated
The new Prospect creation service feature is now available. This feature enables banks to automate the account opening process. For details, refer to the Prospect creation service section of the Banking overview guide.
Banking operations
Updated
To comply with U.S. Regulation D, the Deposit product creation process has been enhanced by expanding the capabilities for configuring early withdrawal penalties on invested amounts. This was done by adding a penalties
object field to the following endpoints:
- Create deposit product - in the request body and 201 response
- Get deposit product - in the 200 response
- List product - in the 200 response
Instant payments
New
The following new Pix endpoints are now available:
Updated
In the Create recurrence [beta] endpoint, reason_code
values for cancellation were updated in the response.
Updated
In the Accept/reject recurrence authorization [beta] endpoint, the payment_date_time
and transaction_identification
fields are now available in the request body.
Updated
The Pix endpoint Validate QR code can now validate a QR code for a Pix Automatic recurring payment. For this, the endpoint now returns a recurrence
object.
Transaction banking
Docs
In the 400 error messages for Create division and Update division endpoints, the new error explanation “Administrative division is misconfigured” was added.
Docs
The description of the payment_datetime
field was clarified. It appears in the following places:
- Post payment - in the request body
- Get transaction - in the 200 response
- Post multi-leg payment - in debits and credits array objects of request body and 200 response
- Schedule payment - in the request body
Docs
The following, formerly missing, 400 errors were added to Post payment and Post multi-leg payment:
- 400 - Future payment datetime above limit
- 400 - Back payment datetime above limit
Card network integration
Updated
A new custom code was added for the network transactions. This new code, OON (Org operation not found), is returned when the operation related to the Transaction Type
subfield of the Processing Code (DE3) present in the body of the authorization message is not configured in the program of the card used. This new custom code was added to the Validation codes for authorization events guide and its definition was added to the Validation codes definitions guide.
Docs
The Rule list guide content for the Flex controls validation rule and the Available limits validation rule for Ledger were updated for clarity and now have updated payload examples.
Cards management
Updated
The List card status history endpoint now returns an operation
enum field, indicating the operation that caused the status change.
Docs
The new Card PIN, PAN, and tokens when a card is reissued section has been added to the Cards management guide. This section makes clear what happens to a card’s PIN, PAN, and tokens when a card is reissued. The same information has also been added to the Reissue card endpoint documentation.
Disputes
Updated
In the Disputes API, the x-account-id
parameter was removed and authorization header was included in all impacted endpoints.
Statements
Updated
In the response object of the List statements v2 endpoint , bar_code
was marked as deprecated and cycle_number
field was added to the cycle
object.
Updated
The Projected accruals guide was updated. Formerly, projected accruals could only be reversed for refinancing and overdue transactions. Now, you can configure reversal for other types of transactions using the new Update accrual type post configuration endpoint.
Updated
The stop_accrual_reason
field was removed from the additional_info
object in 200 response for the following endpoints:
Docs
The following calendar management endpoints were updated to correct the request and response parameters:
- Create program calendar strategy
- List program calendar strategies
- Get program calendar strategy
- Update program calendar strategy
Docs
The following updates were made in the Statements documentation.
- The endpoint “Save account interest rate” was renamed to Configure account transaction category rates and the endpoint description was updated.
- The endpoint “List account interest rates” was renamed to List account transaction category rates and the endpoint description was updated.
- The corresponding endpoint names were updated in Configuring accrual rates and Endpoints that require an account-specific token.
Docs
The List statements v3 endpoint includes a new query parameter called showAmounts
. If this parameter is set to true
, the following additional fields will be returned in the endpoint response:
amount_due
amount_paid_until_due_date
amount_paid_after_due_date
other_credits_until_due_date
other_credits_after_due_date
evolve_to_delinquency
Docs
In the first paragraph of the Credit liquidation guide, a correction was made to the explanation of what happens if you don’t set the program parameter Number of days to block the account for unpaid statement
.
Docs
A new section Accrual type post configurations was added with the following new endpoints:
- Create an accrual type post configuration
- List accrual type post configurations
- Update accrual type post configuration
Docs
The names of the following endpoints were changed.
- “Cancel installment payment” was changed to Cancel payment agreement.
- “Get installment payment” was changed to Get payment agreement.
Docs
Description of the grace_period_days
field was corrected for the following endpoints:
- List available due dates: 200 response
- Save program due date: 201 response
- List program due dates: 200 response
- Save program due date: in request
- Update program due date: in request
- List program due dates: query parameter
Docs
Made the following changes to the Installment advancements guide.
- Updated bullet point #3 in the first section of the guide.
- Updated the example in the Creating an installment advancement section.
Lending
New
The following new endpoints are now available in the Lending API.
- Create prepayment record [beta] enables you to create a prepayment record containing one or multiple repayments so you can implement Buy Now Pay Later (BNPL) programs.
- Create loan product [beta] defaults to BNPL for the
product_type
. - Get loan product [beta] gets a loan product by its ID.
- List loans [beta] filters loans by account ID, authorization ID, or loan product ID and provides information about scheduled repayments in the response.
Deprecated
The following endpoints were deprecated.
New
The Loan updated event now includes a repayment_schedule
object that includes the repayment, installment, amount, and due date information.
New
The new Prepayment created event signals when a prepayment has been created or changes status.
Docs
Lending events were rewritten and edited for clarity and standards.
Pismo Control Center
Updated
Accounts management in Pismo Control Center now supports two types of searches:
- Search by customer using a document, account, email or name. When using this type of search, you will select a customer and access all related accounts in the Accounts overview page.
- Search by specific account using the account number. When using this type of search, you can select the specific account and go directly to the overview page.