6 December 2024
Changes between 8 November and 6 December 2024
Core platform - Payment methods configurations
Docs
The Pismo platform provides advanced flexibility for configuring payment methods. Highly customizable configuration options enable you to modify the platform’s default authorization behaviors to better serve different business needs and use cases and to improve processing times. This functionality supports multiple levels of configurations for authorization, payment, and transfer operations at different hierarchy levels.
Two new guides are now available to further explain this functionality:
- Payment methods configurations overview provides concept information.
- Configure payment methods provides instructions and examples.
Core platform - Balance watcher
New
You can now enable over-limit functionality with the new balance watcher feature. This feature listens for platform and card network authorization events and triggers actions based on these events. It allows you to enable the over-limit setting at different levels of the Pismo platform hierarchy for different types of authorization and for different financial operations.
For details, refer to the new Over-limit configuration section of the Over-limit fee guide.
Banking - Bank slip management
New
You can now issue and manage bank slips with the following new endpoints.
- Issue bank slip to generate a charged amount
- Get issued bank slip and List issued bank slips to get information about the created charges
- Delete issued bank slip to revoke the charge
These endpoints are used in combination with the Pay bank slip endpoints to process payments. You generate a bank slip with the charge to the payer and the payer pays it to complete the transaction. For details, refer to the Issue bank slips section in the Bank slips guide.
Banking - Interest management
New
The Pismo platform offers a comprehensive interest management solution with robust capability to process large volumes of daily operations. This solution provides advanced features such as fully customizable fee and interest calculations, generation of treasury files and legal reports, and ability to manage your ledger within the Pismo platform or to integrate with an external system.
- The new Interest management API allows you to create and manage interest plan configurations and to apply them to a wide range of products.
- The new Interest operations API allows you to perform specific interest operations such as depositing money into an account based on a defined interest plan.
- The Interest-bearing accounts solution allows you to configure and manage interest-bearing products such as savings and time-deposit accounts.
For additional details, refer to the new Interest management overview and Interest management events guides.
Card issuing - Authorization configurations
New
The new Authorization configurations API offers options for the authorization flow management at the organization, program, or account level. It enables you to configure parameters that currently need to be done manually through service request tickets. The parameters that can be configured include options such as Enable Partial Authorization, Disable DCC (dynamic currency conversion), Zero Balance URL, and others.
This new API also allows overriding those configurations at BIN level, enabling you to do some configuration for specific BINs. Acceptances configurations are also available, where you configure parameters at processing code level and also enable/disable operations that are allowed or not allowed in your authorization flow.
Seller management - Settlements
New
The new Settlements API offers advanced capabilities such as running the settlement process for individual merchants and blocking and unblocking merchants. Blocking a merchant means that the settlement process skips this merchant.
Accounts
New
The new Account parameter changed event is now available.
Docs
In the Update customer information endpoint, type for the assets, income, and net_worth fields in the response has been corrected from string to float.
Docs
The country_code field type has been corrected on the following endpoints.
Docs
In the How to add reasons section of the Account status guide, the information has been updated to use the endpoint instead of contacting a Pismo representative.
Docs
In the Create account application endpoint, the description for the external_id field is has been updated to indicate that this field can't be changed.
Docs
In the Get account endpoint, the custom_fields type is now correctly labeled as string instead of object.
Client webhooks
New
New action codes for client webhook response to client anti-fraud webhook for card tokenization are now available:
46- Closed account57- Not permitted58- Not allowed at terminal
Flex controls
Fixed
In the Flex controls API, conditions attribute number_of_installments now accepts values 1-99. The validation that doesn't allow 1 in the value field when the attribute is number_of_installments was removed.
Payments
Updated
In the Request authorization endpoint, format of the authorization_datetime field has been updated.
Rates and fees
New
New configuration simulation endpoints are now available. These endpoints allow you to simulate configurations for possible custom payment options.
Security
Updated
Mutual TLS (mTLS) protocol is now mandatory for all API calls to the Pismo platform. This requirement, along with other clarifying updates, details, and related error messages, has been added to the Identity connectivity with mTLS guide.
Setup
Docs
The Programs, Holidays, and Divisions API reference documentation was updated for standards with improvements such as specifying field ranges and enhancing descriptions of endpoints, fields, and parameters.
Docs
The List holidays endpoint reference was updated to fix the name of the next_business_date property. The correct name is working_date.
Docs
The Holidays API documentation was updated to state that the following two endpoints have a one-minute cache:
When using these endpoints, the response message may contain outdated information for up to one minute after an update occurs to an administrative division.
Transactions
Docs
The Transactions overview and Processing codes and transaction types guides now include a transaction type definition.
Events
Docs
In the Timeline events guide, the table was updated to correct an error: the Category and Type column names were reversed.
Banking operations
New
The following endpoints have been added to the Transaction banking API. The purpose of these endpoints to allow customers to create/list/revoke operation blocks. An operations block prevents the execution of transactions for the specified division or program.
Updated
The following fields are added to the processing_codes object in the request and response payloads. These fields allow users to input or display processing codes for interest-bearing accounts product operations:
interest_processing_codedetach_processing_code
Updated
These new fields are added to the processing_codes object in the following endpoints:
Updated
Added a list of endpoints to the following categories in Endpoints that require an account-specific token:
- Bank accounts
- Integrated payments
- Interest-bearing accounts
Transaction banking
Docs
The File signature and encryption guide is now live. This guide explains how you can digitally sign, encrypt the file, and submit it to Pismo for validation using Pismo’s API.
Updated
Added a new 400 error message Transaction using this tracking ID in progress to the following endpoints:
- Create earmark (v2)
- Update earmark (v2)
- Cancel earmark (v2)
- Post payment (v2)
- Confirm payment (v2)
- Cancel payment (v2)
- Post float cash-in
Updated
The following v2 endpoints will replace their v1 counterparts. The v1 endpoints are scheduled to be deprecated on December 20th, 2024. The reason for this change is that in the v2 version, reason_id is replaced by reason_external_id:
- Update transaction banking account status
- Roll back transaction banking account status
- Create dormancy configuration
- Update dormancy configuration
Updated
A new endpoint List transaction banking account status reason is added as a proxy for the core platform's List account status reasons endpoint. This proxy includes the reason_external_id field to align with Pismo platform's naming conventions. Standardizing this field name enhances clarity for clients and improves the developer experience, ensuring smoother API interactions.
Updated
Added a new 400 error message stating that reason_external_id has a maximum length of 120 characters. This impacts the following endpoints:
Updated
In Upload bulk file, removed all mentions of 307 redirect status and examples that indicate clients must be able to forward the request themselves.
Instant payments
Deprecated
Deprecated Pix management V1 endpoints have been removed from the developer portal documentation.
Authorization
Updated
The Authorization events guide has been updated to include instructions on how to identify recurring transactions (such as subscription transactions).
Card network integration
Updated
The “Schema to send pending transactions to clients” event was renamed to Pending transactions sent. Description was updated for clarification.
Cards management
New
There is a new guide article about how a card’s Application Transaction Counter (ATC) is processed and used on the Pismo platform.
Disputes
New
A new dispute_installment_id field has been added to the response from Create dispute endpoint.
New
New sections have been added to the Disputes overview to give more guidance on opening a dispute with the different card networks the Pismo platform supports - Opening a dispute with Visa, Opening a dispute with Mastercard, and Opening a dispute with ELO.
New
Two new parameters have been added to the Create dispute migration endpoint - installment_amount and installment_number.
Statements
Docs
Added note in description of Create payment agreement explaining that it generates an Installment payment processed event.
Docs
In Minimum account due calculation, the second bullet point began “Strategy 3…”. This was incorrect and is now “Strategy 2…”.
Docs
Changed the wording of the first paragraph of Credit liquidation to explain what the effect is when an account's status changes to OVERDUE. (The account is blocked and the customer can't do a cash-out.)
Added a bullet point for CollectionStatus in this section: Validation code definitions
Updated description of Update account overdue status to explain what the effect is when an account's status changes to OVERDUE.
Updated
In the Create payment agreement endpoint, the metadata field is now available.
Updated
Made the following changes to the Get program future calendars endpoint.
- Changed the name of the
dayquery parameter todueDay. - Added three new query parameters:
programCalendarStrategyId
showCustomCalendars
divisionId
Merchants
Docs
Register terminal was incorrectly documented as having page and perPage query parameters. These parameters were moved to List terminals where they belong.
Docs
Updated descriptions for the fields terminal_type and terminal_status in the endpoints Register terminal and Update terminal.
Docs
Changed the name of the Recurring charges API to Revolving credit - Recurring charges.
Updated
Overview of changes:
Changed merchants create, list, get, and update to align the returned/accepted fields with the docs:
- Removed merchants
accountfield that was deprecated. - Removed the
crediting_frequencyandcrediting_frequency_dayfrom the merchants creditor object. - Removed merchants
custom_fieldsfrom the docs.
Details:
200 response changed:
- Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage
Request body changed:
- Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage - Modified description of
operations
201 response changed:
- New property:
account - New property:
bank_code - Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage
200 response changed:
- New property:
account - New property:
bank_code - Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage
Request body changed:
- Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage - Modified description of
operations
200 response changed:
- New property:
additional_area_code - New property:
additional_phone - New property:
business_category - New property:
creditor_id - New property:
merchant_name - Deleted property:
account - Deleted property:
brand_name - Deleted property:
category - Deleted property:
cid - Deleted property:
creditor - Deleted property:
initial_transaction_blocked_flag - Deleted property:
merchant_key - Deleted property:
org_id - Modified description of
name
Endpoint description changed.
New header param: x-marketplace-id
Request body changed:
- New property:
additional_area_code - New property:
additional_phone - Deleted property:
custom_fields - Modified description of
creditor
200 response changed:
- New property:
additional_area_code - New property:
additional_phone - Deleted property:
account - Deleted property:
custom_fields - Deleted property:
initial_transaction_blocked_flag_or - Modified description of
creditorobject and changed the following properties:- Deleted property:
bank - Deleted property:
bank_code - Deleted property:
crediting_frequency - Deleted property:
crediting_frequency_day - Modified property:
account
Properties changed:
- Modified description ofid
- Modified description ofadvancement_fee
- Modified description ofrate
- Modified description ofmaximum_advancement_percentage
- Deleted property:
200 response changed:
- New property:
additional_area_code - New property:
additional_phone - New property:
business_category - Deleted property:
account - Deleted property:
category - Deleted property:
cid - Deleted property:
initial_transaction_blocked_flag - Deleted property:
merchant_key - Deleted property:
org_id - Modified description of
creditorobject and changed the following properties:- Deleted property:
bank - Deleted property:
bank_code - Deleted property:
crediting_frequency - Deleted property:
crediting_frequency_day - Modified property:
account
Properties changed:
- Modified description ofid
- Modified description ofdiscount_rate
- Modified description ofmaximum_advancement_percentage
- Deleted property:
Request body changed:
- New property:
additional_area_code - New property:
additional_phone - New property:
creditor - Deleted property:
category - Deleted property:
id - Deleted property:
merchant_key
List advancements for merchant
Marked endpoint as outdated.
200 response changed:
- Modified property:
items
Properties changed:
- Modified description ofadvancement_fee
- Modified description ofdiscount_rate
- Modified description ofmaximum_advancement_percentage
Marked endpoint as outdated.
200 response changed:
- Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage
Marked endpoint as outdated.
201 response changed:
- Modified description of
advancement_fee - Modified description of
discount_rate - Modified description of
maximum_advancement_percentage
Pismo Control Center
New
Pismo Control Center now supports embossing. The Manage embossing configurations guide explains how to use Control Center to issue physical cards.
New
Pismo Control Center now supports adding and managing OpenID authentication configurations for an organization.
New
Pismo Control Center now supports viewing API permission groups.
Deprecated
The legacy CRM-API has been deprecated. The endpoints will continue to function normally during the sunset period, but are scheduled for removal in June 2025. For details, refer to the deprecation schedule.