6 October 2023
over 2 years ago by [email protected]
Changes between 8 September and 6 October 2023
<div class="customTab"></div>
<summary class="tabContent" id="Core platform">
### Accounts
#### Fixed
On the [Create account application](ref:post-acquisitions-v3-s2s-applications) and [Create account application (outdated)](ref:post-acquisitions-v2-s2s-applications) endpoints, the platform now correctly validates the `document_number` field as required.
#### Updated
The [Accounts API](ref:post-acquisitions-v3-s2s-applications) now returns the "400 - Bad request - Invalid character in the request payload" error response when the request contains invalid characters such as special characters or emojis.
#### Updated
On the accounts onboarding [succeeded-1](https://developers.pismo.io/events/docs/onboarding-succeeded-1) event, under `applicant` > `account`, added the `creationDate` field.
#### Updated
On the accounts [address](ref:post-accounts-v1-accounts-accountid-addresses) endpoints, added maximum length values on the `address`, `complementary_address`, `neighborhood`, `zip_code`, `city`, `state`, and `country` fields.
#### Updated
On the [Create phone](ref:post-accounts-v1-accounts-accountid-phones) endpoint, `area_code` is no longer a required field.
### Migrations
#### Updated
On the [Account migration started](https://developers.pismo.io/events/docs/migration-account-incoming-1) event, under the `applicant` object, added the `company` object.
#### Updated
On the [Migrate authorizations](ref:postauthorizationsv1) endpoint, updated the default of `update_limit` to `false` and added the following enum list options to `authorization_status`.
* PENDING - Authorizations from Base I, pending confirmation
* PROCESSED - Base II confirmation
* DROPPED - Authorization discarded if confirmation (Base II) is not received within ten days
* DECLINED - Authorization denied when validation fails (response code <> 00)
* CANCELED - Canceled authorization
#### Updated
In the [Migrate accounts](ref:postaccountsv1) endpoint, the new field `percentage_over_limit` in the request body is now available.
#### Updated
In the [Migrate tokens](ref:posttokensv1) endpoint, the `phase_id` field is now added to the request body and is a required field. Also in the same endpoint, the following fields have been removed.
* `record_type`
* `entity_type`
* `primary_account_number_source`
* `previous_status`
* `wallet_provider_account_hash`
* `decision`
* `number_of_activation_attempts`
#### Docs
On the [Migrations overview](doc:migrations-overview) guide, added a note that says customers should contact the implementation team for the latest version of file templates.
#### Docs
In the [Migrate PCI cards](ref:postpcicardsv1) endpoint, updated descriptions in the following fields of the request body.
* `service_code`
* `pin_block`
* `password_updated`
#### Docs
On the [Migrate on-us authorizations](ref:postonusauthorizationsv1) endpoint, added a list of examples under `authorization_status_id`.
### Payments
#### Updated
On the [platform-authorization-1](https://developers.pismo.io/events/docs/platform-authorization-platform-authorization-1) event, added the `beneficiary_id`, `ledger_id`, `posting_date`, and `statement_id` fields, and changed format of the `posting_date` field.
#### Updated
On the [authorization-event-1](https://developers.pismo.io/events/docs/authorization-authorization-event-1) and [authorization-cancellation-event-1](https://developers.pismo.io/events/docs/authorization-authorization-cancellation-event-1) events, made the following updates.
* Added the `event_datetime` field in the UTC 3339 formal that includes milliseconds.
* Within `authorization`, added the `balance_impact` field.
* Updated titles, summaries, and field descriptions, added links to endpoints, and reorganized the fields with the required ones at the top.
#### Docs
Re-added and standardized the [pre-authorization-capture-1](https://developers.pismo.io/events/docs/authorization-pre-authorization-capture-1) event.
#### Docs
Marked the [platform-authorization-1](https://developers.pismo.io/events/docs/platform-authorization-platform-authorization-1) and [on-us-1](https://developers.pismo.io/events/docs/on-us-on-us-1) events with the \[beta] tags since they are currently only utilized in the on-us authorizations functionality, which is in the beta stage prior to general release.
#### Docs
On the request of the [Create installments payment](ref:post-payments-v1-installments) endpoint, in the `installments` array of objects, marked the `total_amount` and `principal_amount` fields required.
#### Docs
On the [Hold funds](doc:hold-funds#hold-funds) guide, made the following updates.
* Corrected information about the account status and program type.
* Added explanation of the `skip_balance_validation` field and removed this field from the [Unblock held amount](ref:post-payments-v1-hold-funds-unblock) and [Transfer held amount](ref:post-payments-v1-hold-funds-transfer) endpoints.
### Programs
#### New
The new endpoints for programs [export](ref:postprogramexport) (download) and [import](ref:postprogramimport) (upload) are now available in the Programs API.
#### Docs
Revised the description for the [program parameter](ref:program-parameters-reference-table) `ALLOW TOKENIZED TRANSACTION WITH CREATED CARD`. This setting allows the customer to create a token in their digital wallet to use a physical card as long as the card has status CREATED. It permits making transactions via wallet before the physical card is activated.
### Transactions
#### Fixed
In the result of the [List transactions](ref:listtransactions) and [Get transaction](doc:gettransactionbyid) endpoints, there were typos in two fields.
* The tax with type `INTEREST` was returned as `INTERESET`.
* The `number_of_installments` field was returned as `number_of_Installments`.
To maintain compatibility with previous versions, the new tax type `INTEREST` and the new field `number_of_installments` have been added. Going forward, you should use the values with the correct spelling because the incorrect fields are scheduled to be deprecated.
#### Updated
On the transaction [creation-1](https://developers.pismo.io/events/docs/transaction-creation-1) and [update-1](https://developers.pismo.io/events/docs/transaction-update-1) events and on the response of the [Get transaction](ref:gettransactionbyid) and [List transactions](ref:listtransactions) endpoints, added the `event_datetime` and `payment_datetime` fields in that UTC 3339 format that includes milliseconds, and updated descriptions for the `event_date` and `payment_date` fields.
{/*
### Security
#### Docs
On [Postman collection with OpenID authentication](doc:sample-project-with-openid-authentication), added the link to the [Pismo Gateway](https://sandbox.pismolabs.io/system/v1/sandbox#/README) documentation.
*/}
</summary>
<summary class="tabContent" id="Data and reporting">
### Data events
#### New
Documentation for the new [JSON schema change](doc:event-data#json-schema-change-notifications) event is now available.
#### Docs
Updated titles of most [events](https://developers.pismo.io/events/docs/event-base-main-event) according to standards.
</summary>
<summary class="tabContent" id="Card issuing">
### Card network integration
#### Docs
The new [Card network interchange fees](doc:card-network-interchange-fees) guide is now available.
#### Updated
On [Validation codes for authorization events](doc:validation-codes-for-authorization-events), added two new denial codes: RAD - Rates API denial and HCE - HSM communication error, and updated values for the ZBU, ZBT, ZBF, ZBA, and ZBE codes.
#### Docs
On the Simulate authorizations endpoint, added examples for installment authorization and replacement authorization.
### Statements
#### New
The following two new parameter codes are now available in [credit liquidation](doc:credit-liquidation).
* 505 - DELINQUENT\_ACCOUNT\_CLOSURE\_LATE\_TRX\_DEBIT\_PROCESSING\_CODE
* 506 - DELINQUENT\_ACCOUNT\_CLOSURE\_LATE\_TRX\_CREDIT\_PROCESSING\_CODE
#### Docs
The new [Recurring charges](doc:recurring-charges) guide is now available.
#### Docs
The API Reference documentation for some of the endpoints in the Statements API incorrectly stated that they require account tokens. The API Reference has been updated to correct this.
The [List discharges](ref:getaccountdischargetracking) endpoint does require a token endpoint, but it was not listed in [Endpoints that require an account-specific token](ref:endpoints-that-require-an-account-specific-token). It has been added to the document under a new section: STATEMENTS DISCHARGE TRACKING.
</summary>
<summary class="tabContent" id="Core banking">
### Corporate banking
#### New
The new Post a multi-leg payment endpoint is now available. This endpoint allows you to post multi-leg payments to the Pismo platform.
#### Fixed
The Save BCB SPB provider configuration endpoint has been updated to reflect accurate `document_number` string of Org’s ISPB. Also, required fields have been designated as such.
#### Deprecated
On the Bank accounts API, the older Register bank account, Get bank account by Pismo account, and Update bank account endpoints are now deprecated and scheduled for decommissioning on 25 March 2023.
#### Updated
The formerly International bank account endpoints have been updated to reflect their status’ as applicable for all regions — [Get bank account](ref:get-intl-bank-accounts-v2-bank-accounts-account-id-bank-accounts-scheme-name) and [Delete bank account](ref:delete-intl-bank-accounts-v2-accounts-account-id-bank-accounts-scheme-name) — and for specific regions, such as Brazil (IBAN, Brazilian bank account, and BBAN) and the UK (SCAN).
#### Updated
Added minimum and maximum values on the number of request and response fields on the following endpoints.
* Update corporate account status
* Rollback corporate account status
* [Get account info](ref:get-accounts)
* Create earmark
#### Updated
The Create earmark, [List earmarks](ref:get-corporate-earmarks), and [Get earmark](ref:find-corporate-earmark) endpoints, accepting internal operations in earmark requests is now enabled. It allows you to provide tracking ID and metadata in the `internal_operation` object.
#### Updated
On the Post a payment endpoint, added a note that says if the account has any reason-based force payment restrictions, the operation will fail, and provided reasons. On the same endpoint, made the following updates.
**Forced transfer**: When making a forced transfer; that is, setting the `debit`, `credit`, and `force_post` to `true`, the authorization-event-1 and creation-1 events are generated with additional fields. The `corporate_metadata` inside metadata (authorization-event-1) or the details (creation-1) fields are updated to include.
* `authorization_type`: Included to identify the payment type as `corporate-force-transfer` in the debit authorization event.
* `credit_tracking_id`: Included in the corporate\_metadata debit event to identify the credit operation tracking id.
* `debit_tracking_id`: Included in the corporate\_metadata credit event to identify the debit operation tracking id.
**Earmark payment transfer**: When making an earmark payment transfer (`debit`, `credit`), the events [authorization-event-1](https://developers.pismo.io/events/docs/authorization-authorization-event-1) and transaction [creation-1](https://developers.pismo.io/events/docs/transaction-creation-1) are generated with additional fields: the `corporate_metadata` inside metadata (authorization-event-1) or the details (creation-1) fields are updated to include.
* `earmark_id`: Included to identify the payment type as `corporate-earmark-transfer` in the consumer authorization event.
* `credit_tracking_id`: Included in the `corporate_metadata` debit event to identify the credit operation tracking ID.
* `debit_tracking_id`: Included in the `corporate_metadata` credit event to identify the debit operation tracking ID.
The response body returns only `authorization_id` from `debit`. The `authorization_id` from `credit` is generated asynchronously.
#### Updated
The `value_dated_balance` field is now available in the response body (200) of the following endpoints.
* [Get account info](ref:get-accounts)
* [Get account balances](ref:get-account-balances)
* [Get account balance history](ref:get-account-balance-history)
#### Updated
The following event schemas have been updated to indicate acceptable status, as well as minimum and maximum character values of these statuses.
* [Dormancy configuration updated](https://developers.pismo.io/events/docs/corporate-dormancy-config-change-1)
* [Dormancy configuration created](https://developers.pismo.io/events/docs/corporate-dormancy-config-creation-1)
* [Earmark created, updated, or canceled](https://developers.pismo.io/events/docs/corporate-earmark-1)
* [Multi Leg Payment lifecycle Events](https://developers.pismo.io/events/docs/corporate-multi-leg-status-change-1)
* [Current scheduled payment status displayed](https://developers.pismo.io/events/docs/corporate-schedule-payment-1)
#### Updated
In the account [balance\_change-1](https://developers.pismo.io/events/docs/account-balances-balance-change-1) and [balance\_history-1](https://developers.pismo.io/events/docs/account-balances-balance-history-1) events, added an object called `value_dated_balance`.
#### Updated
On the Update earmark endpoint, added `internal_operation` in the request body.
#### Updated
On the Cancel an earmark endpoint, added new error mapping and code for corporate accounts not found and removed 409 error from the response.
#### Docs
The new [Banking reports](doc:banking-reports) guide is now available.
</summary>
<summary class="tabContent" id="Seller management">
### Marketplace
#### Updated
On the [Update marketplace](ref:putupdatemarketplacev1) endpoint, the new request field `external_id` field is now available.
</summary>
</div>