3 November 2023

Migrations

New

The new endpoint Migrate customers is now available.

Updated

The following has been added on the migration endpoints.

• On Migrate cards, added a new field called combo_account_id.
• On Migrate accruals data, added a new field network_auth_id in the migration object of the body parameter.
• On Migrate customers, added a list of enum values to marital_status.

Updated

The following has been removed on the Migrate accounts endpoint.

• The company object was removed from the personal object in the request body.
• The total_overdraft_limit and percentage_over_limit fields were removed from the account object of the applicant object.

Payments

Updated

On the platform-authorization-1 event, added the payment_daytime field and the DENIED_CANCELLATION value in the category field.

Updated

Added Balances configuration retrieval to the list of authorization validation rules for platform operations.

Docs

On the Hold funds guide, updated the diagram and the text to correctly reflect the functionality of canceling transfer of held funds.

Security

Docs

The guide Configuring encryption keys for multi-tenant access was removed because it contained duplicated info.

Docs

Fixed a CSS issue that broke tabs in a code example in the Authentication with OpenID Connect for Servers guide.

Transactions

Updated

On List transaction types, the orderBy query parameter now lists possible values: transactionId and description.

Updated

On the result of the List transactions and Get transaction endpoints, the following fields now list possible enum values.

• amount > type (PRINCIPAL, LOCAL, SETTLEMENT)
• tax > type (IOF, IOF_DAILY, INTEREST)

Events

Docs

Standardized event documentation in the TIMELINE, DATAPLATFORM, and AUDIT sections.

Reports

Updated

The Transactions ISS report files has been updated as follows.

• Removed the EventTypeID, Day, and Month fields.
• Added the EntityType_ID, EventDescription, EntryType_ID, AccountingEntry_ID, Transaction_ID, Correlation_ID, Authorization_ID, AuthorizationType, and MerchantName fields.
• Clarified field descriptions throughout.

Updated

The [beta] tag has been removed from the following guides.

• Confluent event configuration tutorial
• AWS EventBridge event configuration tutorial

Docs

On the Transactions IOF report files, clarified descriptions for the date fields (EventDate, AccountingDate, and DueDate).

Statements

New

The new Revolving credit configurations API is now available. It contains the Create program transaction type endpoint which enables you to create program transaction types instead of having to create service tickets for it.

Credit receivables

Updated

The Credit receivables API has a new endpoint and a deprecated one. Get receivable has been deprecated and replaced with Validate receivable. The latter validates a credit receivable's uniqueness in the credit rights registry maintained by B3 - a large financial market infrastructure provider in Brazil.

Corporate banking

Updated

On Post a multi-leg payment, the following updates have been made.

• The field currency in both debits and credits objects of the body param is now a required field.
• Added the force_post field to POST /v1/payments/multileg request.
• Added closed accounts and force restrictions validation errors.

Updated

On Post a multi-leg payment, the following changes have been made in the credits object of the body parameters section.

• Removed the validations field grouping from the 400 response.
• Added the payment_datetime field to the request body that enables you to make backdated payments.
• Added the skip_account_date_validation field that enables you to skip validation of the transaction date time against the account creation date time.

Updated

On Post a multi-leg payment, the following changes have been made.

• Changed error codes WMLP1014, WMLP1016, and WMLP1017 to WMLP0005 in the following responses.
  • 400: Validation error: Closed credit account
  • 400: Force debit restrictions
  • 400: Force credit restrictions
• Added the following 400 error responses.
  • Payment date cannot be a future date and time
  • Payment date cannot be earlier than account creation date
• Changed the 400 response from Payment with less than 3 legs to Payment with less than 2 legs and changed the error message.

Updated

The value for the maximum numbers allowed has been updated in the following 400 responses.

• On Create earmark, earmark_id contains characters not permitted
• On Update earmark, Invalid JSON payload
• On Post a payment, Amount value exceed
• On Post a multi-leg payment, Amount value exceed
• On Schedule payment, Amount value exceed

Updated

On Get account dormancy by account external ID, the following update have been made.

• Changed the error code from WDOR0007 to WADC0002 in the 404 response body.
• Added text that explains how inactivity_time is calculated in the 200 inactivity_time response.

Updated

On Post a payment, the following updates have been made.

• In the 201 response, event_date has been corrected to event_datetime.
• In the 400 response, new error codes and their corresponding messages have been added.
  WPMT0025 for “Debit not permitted on a closed account”
  WPMT0026 for “Credit not permitted on a closed account”
  WPMT0027 for “Payment date cannot be a future date and time”
  WEAM0029 for “Backdating not permitted”

Updated

On the Corporate banking API, dormant_processing_codes have been added. These codes prevent an account from getting reactivated from dormancy when there are financial transactions in that account made with any of these codes. This change impacts the following endpoints.

• Get dormancyConfig by ID
• Create dormancy configuration
• List dormancy configurations
• Update dormancy configuration

The dormant_processing_codes have been added to the following events also.

• corporate/dormancy_config_creation-1
• corporate/dormancy_config_change-1

Updated

Added information to the following event schemas.

• corporate/multi_leg_creation-1
• corporate/multi_leg_status_change-1

Docs

On Get account balances, removed the field cycle_closing_datetime from the 200 response to correctly match the response payload.

Docs

Updated event links for the following endpoints.

• Create corporate account
• Update corporate account
• Post a payment
• Update dormancy configuration

Docs

The maximum length limit has been added or updated for the following fields.

• On Update earmark, added maximum length to the amount and release_datetime fields in the request body.
• On Get account balance history, added maximum length to the startDate and endDate query parameters.
• On Post a payment, in the 201 response payload, updated the maxLength value of event_datetime to 30.

Docs

The following documentation clarifications have been made.

• On Create earmark, added a note that says if the account has any reason-based force debit restrictions, the force earmark creation fails.
• On Post a multi-leg payment, added text in the description that says the payments are processed asynchronously.
• On Get account dormancy by account external ID, in the 200 response payload, added an explanation in the inactivity_time field about how inactivity_time is calculated.

Merchants

Docs

Images in the Settlement scenarios section of How merchant settlements are processed have been updated and replaced.

Control Center

New

Pismo Control Center is now available. Control Center is a web application that enables nontechnical users to use a web browser to perform common tasks on the Pismo platform. This application replaces the Pismo Console, which is scheduled to be decommissioned later in November 2023.