2 August 2024

Changes between 8 July and 2 August 2024

Accounts

Updated

In the List accounts by document number endpoint, updated pattern of the account_status field.

Fixed

Removed the application object from the request body in the following endpoints.

Docs

Updated titles of the List accounts by phone number and List accounts by document number endpoints.

Docs

Removed [beta] tags from the following endpoints.

Migrations

New

The new Migrate accounts pre go-live endpoint enables you to verify the result of a go-live operation without actually activating any accounts.

Updated

In the Migrate accounts endpoint, the unused personal.printedName field has been removed.

Updated

In the Migrate cards endpoint, the unused fields last_blocked_date and additional_customer_id have been removed and description of the endpoint has been updated with information about what data events are generated when migrating COMBO cards.

Docs

The Migrations overview guide has been expanded and updated.

Docs

The migration events in the Events reference are now listed in the alphabetical order.

Payments

New

The following new PATCH endpoints are now available in beta release.

Additionally, the titles for the PUT endpoints in these sections have been renamed with the "Replace" verb instead of "Update".

Updated

In the Platform authorization created event, made the following updates.

Updated description of the tid field and corrected its type to string.
Removed the skip_timeline field.

Updated

In the Request authorization [beta] endpoint, the new description field is now available.

Updated

In the Transfer funds endpoint, inside the from.card.aquirer.wallet objects, the new first_name and last_name fields are now available for REDE acquirer only.

Updated

In the Create cash-in or cash-out and [beta] and Create transfer [beta] endpoints, the currency field was updated to indicate that if you don't provide the value in this field, the platform uses the currency registered in the Pismo hierarchy (first looking at the account, then program, and then Org levels).

Fixed

Corrected URLs for the Payment method configs [beta] and Payment method acceptances [beta] endpoints.

Fixed

In the Hold funds guide, removed erroneous statement that blocking an amount impacts the available_savings_account_limit field.

Docs

In the Payment methods [beta] and Authorization validation rules for platform operations [beta] guides, added notes to explain the Pismo beta program.

Setup

Updated

The Holidays API and Divisions API are improved to better support both core banking and transaction banking functions. The Holidays API maintains two versions of some endpoints — v1 for core banking and v2 for transaction banking. The Platform setup - Holidays and administrative divisions guide also is updated accordingly.

Fixed

In the Client webhooks guide, corrected typos in the amount_transaction and processing_code field names and corrected descriptions of the amount_settlement and amount_transaction fields.

Docs

The new Balances configuration overview guide is now available.

Transactions

Updated

The Transaction created and Transaction updated events have been updated to include fields settlement_conversion_rate and reference_to_cardholder_exchange_rate.

Events

New

The new Data events recovery guide provides advice for situations where your application becomes unable to receive Pismo data events for a period of time. You can recover missing events using cloud backups maintained by Pismo.

Assets

Docs

The Banking - Assets API reference documentation now conforms to standards with updated ordering and descriptions.

Banking operations

Docs

The two events Deposit product created and Deposit product updated are updated and are now aligned to the Pismo standard.

Instant payments

New

The new API to support Indian RuPay and UPI instant payments is now available in beta release.

Updated

In the Pix management’s Validate DICT key endpoint, the new internal field has been added to the response. This boolean field indicates if the field was validated internally at Pismo using local data or validated through DICT.

Updated

For the Pix instant payments system, the internal field has been added to the List account receipts and List account scheduled transfers endpoint responses. This field indicates if a transaction was made between an organization’s accounts within Pismo without accessing the Pix instant payments system.

Updated

In the Pix-out transfer endpoint, the new psp_transaction_created_at field is now available. This date-time field indicates how much time has passed since the client created the transaction.

Updated

In the Create dynamic COBV QR code endpoint in the QR Code API, the charge object has had the discount_final_amount field removed. In the Create dynamic COB QR code endpoint in the same API, the id and status parameters have been removed.

Updated

The Pix management API has been reorganized and updated. Endpoints that interacted directly with DICT, the national key repository, are no longer beta. Endpoints that indirectly interacted with DICT have been deprecated.

Transaction banking

New

The following new endpoints are now available.

Confirm payment serves to settle/confirm pre-authorization for future dated payments.
Request bulk settlement processes fund settlements/clearing in bulk.

Updated

Added processing codes for Request bulk settlement (future value dated payment) to the Transaction banking table in Processing codes and transaction types.

Updated

In the Post multi-leg payment and Schedule payment endpoints, the new instant_clearing field allows you to notify Pismo whether the funds are available at the time when the payment is posted.

Docs

The Transaction banking API reference documentation now conforms to standards with updated ordering and descriptions.

Card network integration

Updated

In Validation code definitions, the following new denial codes are now available.

PAE and PAT while retrieving parameters
ACT and AGE while retrieving account details

Docs

The Clearing/base II guide has been updated to clarify the debit and credit clearing adjustment.

Disputes

Updated

In the Create dispute endpoint, the network_brand_type field is now required. Previously, if no value was entered for this field, the default was “Mastercard”.

Updated

Four new statuses have been added to the Disputes state machine: FILED_IN_ERROR, FAILED_DOCUMENTATION, CHARGEBACK_PENDING_DOCUMENTATION, and CHARGEBACK_REJECT_COLLABORATION.

Statements

New

The new Revolving credit - Installment management API is now available.

Updated

The new codes 507, 508, 509, and 510 are now listed in the table in the “How to automate closing delinquent accounts” section of the Credit liquidation guide.

Updated

In the Revolving credit - Statements > Advancements section of the API reference, added “outdated” labels to the endpoints and added links to the new endpoints.

Fixed

In the Create payment agreement endpoint, the following fields had been incorrectly placed inside the installments object: compulsory, settle_accrual, spit_iof, use_oriinal_rate. They have been moved up a level, outside of that object. Also, all fields have been reordered.

Docs

The new Installment management guide is now available.

Docs

The new How payments are applied to accruals guide is now available.