8 November 2024

Changes between 4 October and 8 November 2024

Accounts

Updated

In the Create account application endpoint, account_type and division_id are now available.

Fixed

In the List phones endpoint, the account phone type now correctly includes COMMERCIAL also.

Docs

The following documentation corrections have been made in the Accounts API reference.

In the Get account endpoint, added the document_number, acquisition_id, entity_type, division_id fields and corrected the statuses to be only NORMAL, BLOCKED, and CANCELLED.
In the List addresses endpoint, added custom_fields.
In the Get customer endpoint, added entity.pep, entity.person, entity.company, customer.is_active.
In the Create customer endpoint, adjusted the birth date format to "YYYY-MM-DD".
In the Update customer information endpoint, removed the x-tenant path parameter and adjusted the document_issued_date field format to "DD/MM/YYYY".

Docs

The following endpoints have been added to the Endpoints that require an account-specific token.

General

New

The Pismo platform now supports a new attribute is_device_registered. This boolean indicates whether the device used for the operation is registered according to the financial institution's security policies.

In the Pix-out transfer endpoint, the new is_device_registered boolean in the request indicates if the device has been registered and validated for transfers.
In the Transfer funds endpoint, the new authorization_validations object contains the authorization validation data such as the is_device_registered field.
In the Flex controls API, the new is_device_registered is available as one of the conditions.attribute options and is also listed in the Evaluation requested event. The Flexible transaction controls guide has been updated accordingly.

Docs

In the Welcome to Pismo guide, several links and descriptions have been updated.

Flex controls

Docs

In the Flexible transaction controls guide, “global program” has been clarified as “program” and the value for type in the Get specific control section has been corrected to spending_limit.

Migrations

Docs

In the Account migration endpoint, field descriptions have been improved.

Payments

Updated

In the Payment config API, the description has been updated with generated events.

Updated

In the Request authorization endpoint, in the calculated_amounts object, the type fields for fees, interests, and taxes have been updated to be a string.

Fixed

In the Create installments payment endpoint, first_installment_date has been removed since this feature is not available.

Deprecated

The decommission date for the Adjustments API has been moved to 31 May 2025.

Transactions

Fixed

In the Get transaction and List transactions endpoints, the transaction id type in the response has been corrected to be an integer.

Events

Updated

Events in the Scheduler payments section have been updated to link to the Payment scheduler [beta] guide and Create pre-schedule [beta] endpoint and aligned to the Pismo guidelines.

Fixed

Beta events under Core platform > Account and Entity have been removed as the endpoints that trigger the events are not public yet.

Banking operations

New

The Interest management and Interest operations APIs are now available.

Updated

In the Interest-bearing accounts guide, the spread method, simple interest type, and all accrual basis descriptions have been updated as being already available on the platform.

Updated

In the Bank accounts API, the new Search bank account endpoint is now available.

Updated

In the Interest-bearing accounts API, added a new field interest_processing_code in the following endpoints. When no value is specified in this filed, processing code defaults to 009797.

Create deposit product
Get deposit product (under the processing_codes object in the 200 response payload)

Transaction banking

Updated

Added tracking_id locked errors to the API docs. These errors occur when multiple payment requests with the same tracking_id are made simultaneously. For example, if the first payment request is still being processed, the second request with the same tracking_id returns a 423 Locked error. This update impacts the following endpoints.

Instant payments

New

There are new endpoints for scheduling Pix payment transfers. The new Schedule transfer(s) V2 [beta] endpoint gives you more options for recurring payments.

Card network integration

New

The following authorization validation denial codes have been added to the Validation codes for authorization events guide.

The four new custom codes address internal and external anti-fraud API timeouts and generic errors:
AET - Anti-fraud external API timeout
AEE - Anti-fraud external generic error
AIT - Anti-fraud internal API timeout
AFE - Anti-fraud internal generic error
The new AUD - Authorization disabled denial code is generated when the option deny_all_authorizations is enabled on the network transactions configuration. This is useful for migration flow scenarios where you want a guarantee that you will process any authorizations before the go-live signal.

The definitions for the new denial codes have been added to the Validation code definitions guide.

New

In the Network authorization received event, the new merchant_denial_code is now available. This code communicates the reason for declining the authorization and the course of action that merchants can take. The code depends on the card network. For example, Mastercard uses Merchant Advice Code (MAC) and Visa uses Recurring Payment Cancellation (RPC).

Updated

The definition for the Invalid message format (IMF) validation code has been updated to reflect that it can be used across all networks.

Updated

The ELO network has been added to the Clearing/base II workflow and to the Consolidated file list in the Clearing/base II guide. An ISO8583 message event code sample was added to the Authorization Events guide for ELO.

Updated

The Visa Denial Code for BLOCKED status (UBT) has been changed from 59 to 78 to indicate blocked, first used or special condition—new cardholder not activated or card is temporarily blocked. This is reflected in the Validation codes for authorization events guide.

Docs

The Anti-fraud integration guide was updated for clarity.

Statements

New

The new endpoints for setting minimum values of accrual types are now available.

Updated

In the List statement balances endpoint, CLOSED_STATEMENT_WITH_CREDITS has been added to the list of possible values for type.

Updated

Removed deprecated endpoint “Create interest accrual transactions (deprecated)” from the API reference. The path for the deprecated endpoint is POST /v2/accounts/{accountId}/interest-accruals.

Updated

Removed disable_all_accounts query parameter from the Create creditor endpoint.

Docs

The new Overdue tolerance guide is now available.

Docs

The following documentation improvements have been made.

Added information about the 200 response to the description for the Post interest accruals endpoint.
In the 200 response for the List statements v3 endpoint, the description for the previous_balance field has been corrected.
Corrected name of query parameter from dueDay to day in the following endpoints:
List program due dates
Get program future calendars
The x-tenant fields in the API reference were incorrectly marked as required. Neither x-tenant or x-cid fields are required or needed, so they have been removed from all endpoints in the Revolving credit - Statements API reference.
In the table in the Multivalue program parameters guide, some text was added to the description for parameter ID 2 (PAYMENTS_TTS) to clarify how the parameter works.
The description for the disableProjection query parameter in the List statement balances endpoint has been updated to clarify what the parameter does.

Docs

Corrected the note about requiring the account ID in the token for the following endpoints.

Merchants

Docs

In the Create creditor and Get creditor endpoints, the descriptions for the following fields have been corrected.

advancement_fee
discount_rate
maximum_advancement_percentage