📍 New embossing event
New event embossing-summary-1 is now available. It indicates when embossing is complete and provides summary information.
📍 New fields in change event for cards
The card updated event has had 3 new fields added to it:
card_previous_status- Previous card status if card status has changed, otherwise, it's the same as current status.
operation_type- Operation causing change.
activation_date- Card activation date and time.
📍 New Get fee models endpoint
New endpoint Get fee models is now available. It allows you to get an organization's fee models.
📍 New Update customer information endpoint
New PUT endpoint to Update customer information is now available. It allows you to mark the customer on the account as active or inactive with the
is_active field. This field is informative only. There are no restrictions that prevent inactive customers to perform any actions.
The other endpoint to Update customer information is the PATCH operation, which allows you to update fields of the person or the company that is linked to the account, but you can’t activate or deactivate them.
📍 New Close dispute endpoint
New Close dispute endpoint is now available. Previously, you couldn't accept a second presentment and withdraw a chargeback. You had to either continue the dispute for a pre-arbitration or use the Mastercard interface. Now, the new endpoint allows you to close the dispute.
📍 Improvement of the reconciliation process
To support reconciliation of customer operations, new information is available in the authorization and authorization cancellation events. The new fields under root -> authorization -> available_change are:
id- Unique integrity identifier of the impact on the available account balance.
update_datetime- Date/time of the impact on the available account balance in the UTC 0 format (RFC 3339).
📍 New field in the anti-fraud default payload
You can now send the maximum credit amount approved for the account in the default anti-fraud request to the issuer in the new decimal field
max_credit_limit in the
📍 New repayment options for Create a loan product API
New repayment options are now available in the Create a loan product API:
FORTNIGHToption in the repayment_frequency field that allows you to create a loan product where a customer can repay every two weeks.
FLAT_BASISoption in the repayment_calculation_method field that helps calculate interest rate payments based on the original loan amount.
BEGINNING_OF_PERIODoption in the repayment_due field that helps calculate the loan repayment schedule.
📍 New options in Create a charge plan API
The following new options are now available in the Create a charge plan API:
- Collection methods
AMORTISEDin the collection_method field.
- Input percentage
max_charged_amountin the percentage field, which give you more control to create a better charge plan.
📍 Pismo API life cycle and deprecation strategy guide
This new guide discusses Pismo's API lifecycle policies, including communication methods.
📍 Pismo Console user guide
This new guide explains how to use the Pismo Console to manage programs, users, acquisition channels, and access keys.
📍 New events documentation
The following new pages list the endpoints and the events they generate:
📍 Create a loan guide
This new guide explains how to create both personal and Buy Now Pay Later (BNPL) loans. The guide shows you how to create a loan product, simulate a loan, book a loan, and disburse a loan.
📍 Create or replace credentials guide
This new guide shows you how to create or replace credentials from an external provider. This enables you to supply the Pismo platform with access credentials, such as API keys, that you obtained from an external provider in a secure way, without anyone at Pismo or the external provider being able to view the credentials.
📍 Migrations overview guide
This new guide explains how you can migrate non-Pismo accounts, cards, statements, transactions, and authorizations to the Pismo platform.
📍 SFTP file integration guide
This new guide explains how to set up SFTP to retrieve Pismo event files.
📍 GCP file integration guide
This new guide explains how to set up GCP to retrieve Pismo event files.
📍 Adjustments API updates
Standardized terms and corrected the links on the endpoints in the Adjustments API reference:
📍 Verifying webhook requests
Corrected the description how generate the hash for the message payload when checking message integrity.
📍 Renamed "Get transactions" guide to "Get transaction details"
Changed title to better clarify what this guide is about.