2022-11-01 changelog

AccountsAccountingAuthorizationsCardsConsoleDocumentationExchange ratesMigrationsFlex controlsPaymentsProcessing codesSecurity

Highlights

📍Installment operations

A new Installments payment guide explains how you can use the new Installments payment endpoint.

📍New card embossing endpoints

There are five new card embossing endpoints:

📍 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 custom_fields object.

📍 Endpoints for account parameters

The following endpoints are now available to get and update account parameters:

• List parameters
• Get parameter
• Update parameter

📍 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 creation-1 event is now generated.

Time zone attribute for flex controls

A new time_zone attribute is now used to evaluate a flex control using the desired time zone for condition attributes such as week_day, month_day, time_now, and reset_period. If 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.

Updates and fixes

📍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 26.
• In Mastercard, a message with processing code (transaction type) 20 and reversal indicator R.

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:

• create_statements
• current_cycle integer

📍New network field

A new network field that indicates Visa or Mastercard network is now available in the response of the following endpoints:

• Get transaction
• List transactions

📍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

📍 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:

• Authorizations
• Payments
• Transactions

📍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

Updated fee model documentation with the type, precedence, and calculation_basis fields. The new calculation_basis was added as a parameter to Create fee model and return from Get fee model.

📍Clarified get merchant transactions

Improved documentation for the following endpoints in the API Reference for Merchants API > Transactions:

• Retrieves merchants transactions (V2)
• Retrieves merchants transactions (V3)

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 point_of_sales_id field.

📍Accounting amount field

In the Create an accounting entry endpoint, added the amount field.