It is ultimately up to the organization to handle what to put inside the meta object and send in the payload. The workflow can use single or multiple data field(s) from the supplied payload’s meta object sent via API. These nested meta data can be used to create Input Attributes and can also be leveraged in informational and/or decisional tags. 

For example, the meta object can contain “existing_customer”: true / false data. This data can be used to create an Input Attribute, which then can be used in the “Existing Customer” and “New Customer” tags. These tags can be used to decide whether to run or not run certain data services. 

Below are some examples of meta data sent nested under the meta object:

Additional Information on Submitted Documents:

• In the above case, the meta object contains the applicant’s submitted document information, the applicant’s user ID, and the KYC status of the applicant.

Additional Information on Applicant’s Role/Type in Joint Accounts:

• The above are two examples of applicant role information that can be used in workflows that evaluate joint applicants. The top example (highlighted in red) shows an applicant who is the primary account holder in the joint application, while the bottom example (highlighted in blue) shows an applicant who is the secondary account holder. Applicant role information is supplemental data; however, it provides important information to the organization and can be considered in decision-making.

Additional Information on the Applicant:

• In the above case, the meta object contains supplemental information about the applicant, such as the reported annual revenue of the applicant’s business. Also, tag information collected by the organization during the application process has been passed to Alloy. Within Alloy, this information can be used to trigger certain actions (e.g., run a specific data service, send the application to a different workflow, send the application to a particular outcome).

• Collected information about the applicant during the application process can be sent in the meta object. These meta data may help an agent make decisions when reviewing applications (e.g., applications in the Manual Review outcome bucket).
• In the above case, additional applicant information, including employment information collected by the organization, is sent in the payload.

There are various ways to send and leverage supplemental data using the meta object. Input Attributes can be created and used in informational or decisional tags using meta data (e.g., deciding to run certain data services or deciding on an evaluation outcome). Nested data under the meta object are highly customizable.

Please don’t hesitate to contact support@alloy.com for further assistance and consider these other helpful articles:

• Meta Objects
• How to add Input Attributes in workflows
• How to add decisional Input Attributes in workflows
• Common use cases with Input Attributes