Formats requirements for key persons associated with accountsBreaking changes
What’s new
The requirements
hash on the Account
and Capability
objects, and the verification_
hash on the Country Spec
object have newly formatted strings for requirements that are related to key persons associated with an account:
- Fields that are required for persons with
representative
,owner
,director
, andexecutive
roles will be prefixed withrepresentative
,owners
,directors
, andexecutives
, respectively. Person requirements are previewed as follows:- When the representative’s phone number is required, it appears as
representative.
instead ofphone relationship.
.representative - When an owner’s full name is required, it appears as
owners.
andfirst_ name owners.
instead oflast_ name relationship.
.owner - When an executive’s ID number is required, it appears as
executives.
instead ofid_ number relationship.
.executive - When a director’s date of birth is required, it appears as
directors.
,dob. day directors.
, anddob. month directors.
instead ofdob. year relationship.
.director
- When the representative’s phone number is required, it appears as
- The boolean values that indicate the associated owners, executives, or directors now appear as
company.
,owners_ provided company.
, orexecutives_ provided company.
instead ofdirectors_ provided relationship.
,owner relationship.
, orexecutive relationship.
, respectively.director
Impact
The new formatting of the requirements
and verification_
hashes creates a more intuitive naming convention, making it easier for you to identify and address the specific information needed for each person role.