4 October 2024
Changes between 6 September and 4 October 2024
Accounts
Updated
The custom_fields
object for any custom key/value information is now available in the following endpoints.
- Create account application (in the request,
application
>applicant
>address
) - Create address (in the request)
- Get address (in the response)
- Update address (in the response)
Updated
In the Account status changed event, the new reason_external_id
field is now available.
Updated
In the Update account status endpoint, the status
field is now required.
Updated
The Migrate account to different program endpoint has been renamed to Transfer account to different program.
Flex controls
Updated
In the Evaluation requested event, the new evaluated_controls
array field returns the list of validated flex controls.
Docs
The Rules events section was renamed to Flex controls.
Docs
The Flexible transaction controls guide has been updated to include the following options in the attribute
body parameter.
number_of_installments
is_physical_card_present
is_password_present
Payments
New
The payment scheduler functionality is now available in beta release to create payment pre-schedules. In addition to the new API, the following new events are available.
Updated
The payment methods guides and APIs have been reorganized and the following changes have been made.
- The new Payment methods overview outlines two main payment methods categories supported by the Pismo platform.
- The [beta] tag was removed from the Payment methods and Authorization validation rules for platform operations guides and the Payment methods, Payment method configs, and Payment method acceptances APIs.
- The introduction section of the Payment methods has been updated with the recommendation note and additional information about the API scope.
- The Payments and transfers guides have been updated with the recommendation note.
Docs
In the Create transfer endpoint documentation, the name of the payment_datetime
field has been corrected.
Setup
Docs
The Orgs and Programs API reference documentation has been updated for standards.
Bank accounts
New
Two new endpoints have been added to the Bank accounts API. These endpoints allow you to register ACH or Fedwire accounts with Pismo.
Instant payments
New
The new Check DICT keys endpoint has been added to the Pix management API. This endpoint enables you to check whether a key exists in the national DICT database, given the seed value (such as an email) used to generate it. Multiple keys, each based on a different seed value, can be checked in the same request.
New
The new Withdrawal services category in the Pix instant payments API contains two new endpoints.
Update
The new authorization_datetime
field has been added to the 200
response for the Transfer payments and Get funds transfer status endpoints. It represents the date/time when the transfer was authorized.
Update
The new optional name_type
field has been added to the following Pix management endpoints.
Deprecated
The deprecation schedule has been updated with the planned deprecation of the Pix management endpoints.
Integrated payments
New
The discount
object has been added to the instructions
object in Issue bank slip. The discount
object is for to discounts applied to bank slips that are paid either before or on the deadline.
Interest-bearing accounts
Updated
The new savings_accounts_configs
field has been added to the following endpoints.
Transaction banking
New
The new Upload bulk file endpoint has been added to the Transaction banking API. This endpoint enables you to manage the upload of bulk source files with their corresponding signatures to Pismo.
Updated
The error message Invalid payment datetime for instant clearing payment
is no longer needed and has been removed from the Post payment and Schedule payment endpoints for the following reasons.
- The
instant_clearing
property can now be configured in themetadata
field in the Create holiday endpoint. If you don't provideinstant_clearing
in the payment request, the value from the holiday API will be used. If there is no configuration inmetadata
, the default valuefalse
is used. - For future-dated transactions with
instant_clearing
set totrue
, there is no longer a validation blocking this type of request. Instead, it will be treated as a future-dated transaction with regular clearing.
Updated
The following fields have been added to the restrictions
object of the 200
response payload in Get dormancy configuration. The purpose of these fields is to enable you to use custom reason codes in dormancy.
current_reason_external_id
new_reason_id
new_reason_external_id
Updated
The new reason_external_id
field has been added to the 200
response payload of Get transaction banking account information. This field enables users to use custom IDs for reason codes.
Updated
In the Post payment endpoint, the descriptions of the following fields have been updated.
payment_datetime
— You can now backdate payments up to seven calendar days or postdate them up to ten calendar days.business_date
— You can now set this field to the current working day or up to one working day before or after.
Updated
The note has been added to the Schedule payment endpoint explaining that the validation of a transaction only occurs during the scheduled payment execution.
Updated
The error message Invalid business date format
has been updated to include a statement about the date format validation mechanism. This mechanism not only verifies the date format (yyyy-mm-dd), but also checks for invalid dates such as 2024-09-31. This mechanism is included in the following endpoints.
Updated
In the Post payment endpoint, the description of the skip_account_date_validation
field has been updated to read "If FALSE
, the payment_datetime
is validated against the account creation date/time. If TRUE
, the validation is skipped."
Docs
Two new guides are now available.
Card network integration
New
The new RED validation code for credit vouchers has been added to Validation codes for authorization events.
Updated
In RED - Operation not allowed by rules / Rules do not honor / Rules internal error / Operation not permitted - credit voucher, the description for the RED validation code has been updated to include credit vouchers
Updated
In Validation codes for authorization events, the RED validation code “Operation not allowed by rules” for Visa has been changed to 78.
Card tokenization
New
There is a new card tokenization endpoint that allows someone using the Samsung Pay SDK to get encrypted card data for tokenization.
Docs
The card tokenization process for 3rd party wallets has been revised and improved. Sequence diagrams have been added showing where in the tokenization process events are generated.
Cards management
Update
The new How the Pismo platform handles credit voucher authorization section has been added to the Full balance credit program guide.
Statements
New
The new Payment tolerance guide describes the new feature.
New
The new INTEREST_RATE_PERIOD
program parameter is now available. Its display name in Pismo Control Center is Interest rate period. This parameter has been added to the Program parameters reference table and the new Changing the interest accrual rate section has been added to Configuring accrual rates to explain the purpose and use of the new parameter.
Update
In the List account accruals endpoint, three new query parameters are now available.
interestAccrualId
transactionId
statementId
Update
The new additional_info
object field has been added to the List account accruals v2 and List account accruals v3 endpoint. The new field contains one property, account_financial_classification
, which is a customer-defined number representing the financial classification of the account.
Update
The new addition_info
object field has been added to the following events.
The field contains one property, account_financial_classification
.
Update
The following endpoints now require a JWT token that includes the account ID. The API has been updated accordingly, with a note added to the description of each endpoint, and the endpoints have been added to Endpoints that require an account-specific token.
Delinquent account API:
Delinquency bucket API:
Recurring charge API:
- Create recurring charge plan
- List recurring charge plans
- Get recurring charge plan
- Disable recurring charge plan
- Create link
- Get link between a plan and an account
- Delete recurring charge link
- List recurring charge plan links
- List account links
- List scheduled charges
- Get scheduled charge
- Update scheduled charge
Setup
Docs
The new Zero balance integration - issuer’s guide guide is now available.
Merchants
Deprecated
In Create merchant, Create creditor, and Update creditor, the following fields have been deprecated:
BANK
credit_frequency
credit_frequency_day
Update
In the Create merchant endpoint, crediting_method
used to allow either ACCOUNT
or BANK
. It now only allows ACCOUNT
. The endpoint definition has been updated to clarify how a new merchant is assigned to a program.
Update
The new Overriding the scheduled payment date section has been added to How merchant settlements are processed. A new bullet point with a link to the new section was added to the note earlier in the article.
Pismo Control Center
New
Pismo Control Center now supports the following features.
- Interest plans, which define how interest is calculated and applied to a product or account.
- Deposit products, which include savings deposit accounts and time deposit accounts.