Product attributes control how the Deposit Account Origination intake Omniscript behaves for each product. They determine the available funding methods, validate initial deposit requirements, and store proposal details. Configure these attributes in the Product Catalog to ensure the Omniscript launches, validates inputs, and generates offers correctly.
Available in: Lightning Experience Available in: Professional, Enterprise, and Unlimited Editions |
The Deposit Account Origination intake flow requires these product attributes. Add these attributes to your deposit account product in the Product Catalog before deploying the Omniscript.
| API Name | Description | Used For |
|---|---|---|
| InitialFundingMethod | Specifies the method by which the customer funds the deposit account at opening. | Displays available funding method options in the Initial Funding Details step. Supported values: ACH, Debit Card, Cash Deposit, Wire Transfer. |
| MinimumBalanceAmount | The minimum balance required to maintain the deposit account as per product terms. | Validates the applicant's initial deposit amount against the product minimum. Set a numeric default value, for example, 130000. |
| InitialDepositAmount | The amount the customer initially deposits when opening the account. | Stored as an Application Form Product Proposal attribute against the selected proposal. |
| OmniscriptName | The name of the Deposit Account Omniscript to launch for the intake flow. | Used to navigate to the Deposit Account intake Omniscript. Set the value to DepositAcct_ApplicantIntake_MultiLanguage. |
| InitialDepositDate | The date on which the customer makes the initial deposit into the account. | Stored as an Application Form Product Proposal attribute against the selected proposal. |
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.