2022-05-16 changelog
AdjustmentsBankingCardsFlex ControlsTransactions
Highlights
๐New transaction balances endpoint
A new endpoint to list balance details for credit card transactions is now available.
๐New embossing endpoints for noname cards
Noname cards, which are batch-generated, have two new endpoints to manage their embossing configuration - Update noname card embossing group and Get noname card embossing group
๐New update beneficiary endpoint
A new endpoint to update the name and alias of a beneficiary of a bank account is now available.
Updates & Fixes
๐ New error code for customer flex controls
Implemented a new error code for the create new customer flex control endpoint. When the customer does not belong to the domain of the organization (Org_ID), the platform will now return the 403 error code, as per HTTP standard for secure calls.
๐Updated validations of credit adjustment types
Implemented new validations for the adjustments API in the following credit adjustment type scenarios:
- Prevent the creation of credit adjustment types in cases where
isCredit = 1
andValidateBalance = 1
. - Stop validating the balance if the adjustment type has
isCredit = 1
๐Documentation updates
-
Force payments - Updated the API reference with clarifying information and the guide with additional information about the differences between a forced operation and an adjustment.
-
Anti-fraud - New webhook code sample for Go in Third-party wallets (such as Apple Pay) guide.
-
Flexible transaction controls โ Clarified the example to Deny purchase by entry mode.
-
Create adjustment โ Updated field descriptions in the
adjustment_type
object. -
Create accounting entries โ Created a guide for manually registering accounting entries.
-
Create and update dispute forms โ Created a guide for creating and updating dispute forms.
-
Create and update fraud reports โ Created a guide for creating and updating dispute fraud reports.