AccountsAccountingAuthorizationsCardsConsoleDocumentationExchange ratesMigrationsFlex controlsPaymentsProcessing codesSecurity
📍New card embossing endpoints
There are five new card embossing endpoints:
|Start card embossing||Start card embossing for a specific embossing configuration.|
|Update card embossing address||Create a temporary mailing address for a newly-embossed card. It could be a hotel's address, for example.|
|List embossing files info||List an organization's embossers with filters and paging.|
|Get embossing file||Download an embossing file that the Pismo platform sends to embossers.|
|List org embosser info||Get detailed information about an organization's embossing configurations.|
📍 New endpoint to list transaction types
A new list transaction types endpoint allows you to list transaction types by filter.
📍 New endpoint to update account custom fields
A new Update account custom fields endpoint allows you to update account custom fields by providing key-value pairs in the
📍 Endpoints for account parameters
The following endpoints are now available to get and update account parameters:
📍 Transfer funds requires account token
The Transfer funds endpoint now requires an account-specific access token.
📍 Transaction types event
When a new transaction type is created, a new transaction types event is now generated.
Time zone attribute for flex controls
time_zone attribute is now used to evaluate a flex control using the desired time zone for condition attributes such as
time_zone is empty, the control is evaluated using the UTC time zone.
With this update, the
utc_time attribute inside the
reset_period is now deprecated.
📍 Visa pre-arbitration chargeback
You can now create a Visa chargeback and send a pre-arbitration event with the Create dispute endpoint. You can also fill out the Visa collaboration and pre-arbitration forms in the Create dispute form endpoint.
📍 Visa - more chargeback types
With the Create dispute endpoint, you can now open a chargeback for Visa allocation reason code 11, in addition to 10. These codes refer to chargeback types.
📍 Mastercard - pre-arbitration for partial amount
With the Create dispute endpoint, you can now open Mastercard pre-arbitration for a partial amount, and not just the full amount, with new pre-arbitration fields.
📍Correct cancellation of a credit voucher
The authorization flow on the Pismo platform now correctly handles cancellation of a credit voucher. Credit voucher cancellation is represented as:
- In Visa, a message on the Base II file of the TC
- In Mastercard, a message with processing code (transaction type)
20and reversal indicator
When this type of message matches a credit in the database, this credit is now canceled, creating a debit impact on the account. The platform can now post a debit voucher to the customer's account when it doesn't find a reversal credit voucher clearing in the settlement clearing file. Previously, the platform ignored the credit voucher cancellation messages and didn't cancel the credit nor issued the debit.
📍Withdrawal limit fix
The value, type, and description of the withdrawal limits parameter are now corrected to avoid future problems with the withdrawal limits configurations. The Withdrawal limits percentage program parameter on the Pismo Console specifies maximum allowed percentage for withdrawals or payments and is set in decimal places. Previously, a problem with this configuration resulted in miscalculation of the withdrawal limit.
📍Two migration properties removed
Removed the following properties from the
migrations object of the Migrate accounts endpoint:
📍New network field
network field that indicates Visa or Mastercard network is now available in the response of the following endpoints:
📍New CMD validation code
A new custom denial code CMD (Card Mode Disabled) has been added to the Validation codes for authorization events guide.
📍 Documentation feedback section
A new Documentation feedback section explains how you can best provide feedback about documentation.
📍 Updated API reference for standards
The following API reference sections were updated to improve the descriptions and to bring them in line with the new standards:
📍Legal blocks documentation
A new Legal blocks guide in the Accounts section discusses how the Pismo platform handles total and partial legal blocks that are placed on an account for legal reasons. A legal or judicial block prevents or limits financial movement within the account.
📍Updated fee model documentation
📍Clarified get merchant transactions
Improved documentation for the following endpoints in the API Reference for Merchants API > Transactions:
Added a note to the first endpoint, improved its description, and added (V1) and (V2) to the endpoint names to clarify that they represent different versions of the same endpoint documentation.
📍Clarified field description
In the Transfer funds endpoint, in the
merchants object, clarified description of the
📍Accounting amount field
In the Create an accounting entry endpoint, added the