7.14.0
Release 7.14.0 (#627)
This release introduces several enhancements and extensions to the Accounts API client, focusing on improved schema versioning support, expanded entity management, and broader business type and role coverage. The changes add flexible API methods to specify schema versions, introduce new model fields and types, and extend enums to support a wider range of business and company scenarios.
API client enhancements for schema versioning:
- Added overloaded methods to
ApiClientandAccountsClient(both async and sync) to accept custom headers, specifically to support specifying aschemaVersionfor requests. Default schema version is set to"3.0"if not provided. (src/main/java/com/checkout/ApiClient.java,src/main/java/com/checkout/ApiClientImpl.java,src/main/java/com/checkout/accounts/AccountsClient.java,src/main/java/com/checkout/accounts/AccountsClientImpl.java) [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16]
Model and enum extensions:
-
Added new model classes and fields to support additional business requirements:
- Introduced
AgreedTermsmodel for capturing agreement metadata. (src/main/java/com/checkout/accounts/AgreedTerms.java) - Added
additionalTradingNamesandisRegisteredCompanyfields toCompany. (src/main/java/com/checkout/accounts/Company.java) - Added
dayfield toDateOfIncorporation. (src/main/java/com/checkout/accounts/DateOfIncorporation.java) - Introduced new enum
CompanyPositionfor more granular company role identification. (src/main/java/com/checkout/accounts/CompanyPosition.java)
- Introduced
-
Expanded supported business types and entity roles:
- Extended
BusinessTypeenum with many new types (e.g.,INDIVIDUAL_OR_SOLE_PROPRIETORSHIP,NON_PROFIT_ENTITY, etc.). (src/main/java/com/checkout/accounts/BusinessType.java) - Extended
EntityRolesenum with new roles (DIRECTOR,CONTROL_PERSON). (src/main/java/com/checkout/accounts/EntityRoles.java)
- Extended
These changes provide greater flexibility for clients to interact with the API using different schema versions, and ensure the models and enums better reflect the diverse range of business entities and roles that may be encountered.