Changelog
About PismoContact Us
Back to All

6 September 2024

2 months ago by [email protected]

Changes between 2 August and 6 September 2024

Accounts

Updated

In the Accounts analytic report, the new External_ID field is now available.

Updated

In the Address created [beta] and Address changed [beta] events, the new metadata field is now available.

Docs

In the Update address endpoint, the complementary_address field now indicates the maximum value of 100 characters.

Docs

In the Create account application endpoint, the birth_date and document_issued_date fields now specify the correct date format of yyyy-MM-dd.

Flex controls

New

The new Get account customers' flex controls endpoint is now available.

Docs

You can create flex controls with Pix in the Pismo Control Center and the Update account flex control endpoint. See more information in the Create a flex control on Pix transactions and Flexible transaction controls guides.

Updated

The new card_mode field that specifies the operational mode (debit or credit) of the card is now available in the following endpoints.

The new card_mode field is also available in the following events.

Updated

The new custom_code field that specifies the denial reason by the customer's anti-fraud solution is now available in the following endpoints.

The new custom_code field is also available in the following events.

Payments

Updated

In the Create cash-in or cash-out [beta] and Create transfer [beta] endpoint, the new validation_rules field allows you to set up validations such as forcing and disabling rules and changing response codes and denial codes.

Updated

In the Create installments payment endpoint, the new skip_account_status_validation field is now available.

Updated

The new additional_financial_details object field is now available in the Request authorization [beta] endpoint inside the calculated_amounts object and in the Platform authorization created event.

Updated

In the response of the Request authorization [beta] endpoint, the new datetime_utc field indicates when the authorization is created inside the Pismo platform in the UTC 0 time zone.

Docs

Documentation for the following endpoints is now available.

Docs

Documentation for the PCI endpoints in the Payment methods API and Payment configurations API has been updated to include the PCI URL and note to use the https://gw-pci.pismolabs.io environment.

Docs

In the Request authorization [beta] endpoint, the explanation of the description field has been expanded to clarify its impact on the customer statement.

Docs

In the Create transfer endpoint, the field name was corrected to be payment_datetime.

Transactions

Updated

In the List transactions endpoint, the new numberOfLatestTransactions filter is now available.

Setup

New

The new Processing codes management API is now available. The API allows you to manage processing codes at the organization, program, or account level.

Docs

The Orgs and Programs API reference documentation has been updated for standards.

Support

Docs

The new Incident lifecycle guide documents how incidents are escalated.

Events

Docs

The Azure event configuration tutorial has been updated to explain that Microsoft only provides guaranteed latency and throughput when using the Service Bus premium messaging tier.

Card network integration

Updated

Two new custom denial codes, PAT and PAE, can be returned in case of error while fetching the parameters details in the Programs API. Learn more about the denial codes in Validation codes for authorization events.

Updated

The new validation PARAMETER is now available. Refer to the Rule list guide for additional information.

Updated

In Card status validations, the Mastercard denial code for the UBT custom code has changed from 63 to 57.

Docs

The Partial authorization response section in the Zero balance anti-fraud and validations integration guide has been updated to note that decimal precision needs to be according to ISO 3166-1 and ISO 4217 standards.

Card tokenization

New

The Get calls - Get encrypted data for wallet token and Get encrypted card data for Apple Pay endpoints -have been deprecated and replaced with the Post calls - Create encrypted data for Apple Pay and Create encrypted card data with Google Pay.

Instant payments

New

In the Pix instant payments API, the following new endpoints are now available.

New

The new internal field has been added to the Validate key Pix management endpoint. This field indicates if the Pix key was validated locally on the Pismo platform without going to the DICT database.

New

The new internal field has been added to the List account receipts Pix instant payments endpoint response. This field indicates if the Pix transaction was made between a Pix organization’s accounts. The same field was added to the List account scheduled transfers endpoint response.

New

Pismo now supports a new instant payments system and API - the United Payments Interface (UPI) funds transfer for RuPay, a card network in India.

Protection Bulletin

The following new Protection Bulletin endpoints are now available.

Statements

Updated

In the Credit transaction used for discharge event, two new fields are now available.

  • credit_authorization_tracking_id
  • target > debit_authorization_tracking_id

Docs

The new Multivalue program parameters guide is now available. The endpoints in the Revolving credit - Statements > Multivalue program parameters section have been updated as follows.

  • All three endpoints have been updated to include the word “multivalue” in the name and description.
  • A link to the new guide has been added in the descriptions of all three endpoints.
  • The "Get program parameter values" endpoint has been renamed to List multivalue program parameters. Its description has been corrected. The description used to say that the returned value could be, for example, transaction type IDs. This was not correct, so it was removed.
  • The "Update program parameter values" endpoint has been renamed to Update multivalue program parameter values.
  • The "Delete program parameter values" endpoint has been renamed Delete multivalue program parameter values.
  • In all three endpoints, the description for the parameterId path parameter has been corrected. The description used to say that you could get parameter IDs with the "List program parameters" endpoint. This was wrong, because the parameter IDs returned by that endpoint don't include multivalue parameters.

Docs

In the How to automate closing delinquent accounts section of the Credit liquidation guide, an endpoint link was updated, and a link to the new Multivalue program parameters guide was added.

Docs

The Minimum amount due calculation guide has been extensively rewritten to fix mistakes and improve explanations.

Docs

A number of the endpoints that manage advancements do similar, but not identical things. As a result, there was some duplication in the endpoint titles. Those titles have been renamed to make it clear that they do different things. The following title changes have been made and the descriptions updated. Also, some of the endpoints had been incorrectly labeled “outdated”. This labeling has been removed and, where necessary, a note in the description has been updated accordingly.

In “Revolving credit - Statements > Advancements”:

In “Revolving credit - Installment management > Installment advancements”:

In “Revolving credit - Installment management > Simulations”:

Banking operations

New

The new Get program attachment endpoint in the Interest-bearing accounts API allows you to list programs that are attached to a savings or a deposit product using program ID.

Updated

The provider Pay2All is no longer Pismo’s partner for BaaS, and thus was removed from the following documentation:

Integrated payments

New

The new bank slip issuing feature is now available and has been added to the Bank slips guide. This feature enables financial institutions to issue bank slips to their customers to complete a payment transaction, similar to generating an invoice. The feature includes the following endpoints.

Bank slip issuance:

Transfer:

Transaction banking

New

The new Past business date toggle endpoint is now available in the Transaction banking API. This endpoint allows you to enable or disable posting payments to a past business date. Previously, posting payments to a past business date was enabled by specifying a date in the business_date field in Post payment or Post multi-leg payment. Now, using this new endpoint, you can choose to toggle between enabling or disabling this feature within a division. However, setting a business date that falls within the current or future business cycle is not allowed.

Updated

Two new fields are added to Get account balance and Get account balance history endpoints, corresponding to the account currency displayed in 3-letter alphabetic code format of ISO 4217.

  • currency_numeric_code
  • currency_alphabetic_code

Updated

In the Post payment endpoint, the new 400 response message is available for misconfigured administrative division: "WPMT0045: Administrative division is misconfigured".

Docs

In the Request bulk settlement endpoint documentation, added a note that says you can call this endpoint once with the same parameters, per division, settlement date, and operation type. If the process fails, you can retry up to 9 times per division, per business day.

Docs

The new Account balance definitions for transaction banking guide is now available.

Marketplaces

Deprecated

The 200 response for the following endpoints includes an operation_type_id field. This field has been marked as deprecated, and the note at the end of the description has been updated to reflect this.

Merchants

Docs

You must create a Merchant program before you can create merchants. To clarify this, a note has been added in the Create merchant endpoint description and a step in the Setting up a marketplace section of the Seller management overview page.