Configuring Product

The product description portion of the product configuration sets the look and the description text for each product. The diagram below shows how each of the keys relates to the presentation of the product.

The value in the client.webapp.products.productDescription is a reference to the client.custom.messages.en key. Refer to the section on User message text in this document for more information on changing message text configurations.

The product configuration allows you to define the message keys for each of the products. To set or edit the values of the message keys, please see the section on User message text in this document.

The funding attributes allow you to set and define the parameters around how a product can be funded. To access these configurations, go to the advanced configuration Type ID client.webapp.products.productDescription.

To limit a product to a certain type of funding, find the product in the same client.webapp.products.productDescription and add the applicable funding types from the client.workflow.app.funding.options (the options are generally ACH, card , and cash | fundLater). For example:

"funding": {
        "types": [
        "ACH"           ],
                "default_funding": 100,
                "min_funding": 50,
                "max_funding": 1000
}

There are two final values that can be set to reflect your overall minimum and maximum funding amounts. These limits are set for the overall shopping cart total. To access this configuration, navigate to client.webapp.custom.properties and change the following values:

"maxFundingAmount": 1000,
"minFundingAmount": 5

The age restriction data structure places age-based constraints on a product. This is typically used for products targeted to minors. The configuration found below in the client.webapp.custom.properties can be configured to reflect your financial institution's desired age.

"minimumAgeProductXA": 18,

The age rules are part of the overall product configuration. To add an age rule, copy and paste the text below and add to the configuration for the product that you desire to update in the client.webapp.products.productDescription. For example, here is a configuration and value set:

"ageRules": {"minAge": 18, "minAgeJoint": 14}

Funding limits can be set by payment method to allow more control over how products are funded. This can allow for a payment type to be restricted to a certain minimum, maximum, or default funding. To access these configurations, go to the advanced configuration Type ID client.workflow.app.funding.options.

  "ACH": {
        "channels": [
            "web",
            "native"        ],
        "label": "bankTransfer",
        "funding": {
                "min": 25,
                "max": 10000,
                "default": 25
        }

For the specific payment method, enter this configuration and tailor the amounts to your financial institution's needs ("max" is most likely the only value that will be necessary to set here):

The set limits allow for different error messages to display in the workflow based on the funding configuration and the funding type. Below is a table describing min, max, and default funding limits:

You can configure payment methods to be offered based on the user workflow (unauthenticated existing member, authenticated existing member, or unauthenticated new member) or on the channel used to access Gro (the web application or the native iOS application (available for in-branch account opening).

To access this configuration, navigate to the client.workflow.app.funding.options. Below is sample configuration of all the restrictions that your financial institution can leverage. You can add this configuration information to a specific payment method to enable available workflows or channels.

"channels": [
            "web",
            "native"        ],
        "flows": [
            "unauth",
            "existing",
            "auth"        ],

The available fields in the channels array are as follows:

The available fields in the "flows" array are as follows:

You can configure products, like payments, to be offered based on the user workflow (unauthenticated existing member, authenticated existing member, or unauthenticated new member) or on the channel used to access Gro (the web application or the native iOS application (available for in-branch account opening).

To access this configuration, navigate to the client.webapp.products.productDescriptionType ID. Below is sample configuration demonstrating the restrictions that your financial institution can leverage. You can add this configuration information to a specific product to enable available workflows or channels.

"channels": [
            "web",
            "native"        ],
        "flow": [
            "unauth",
            "existing",
            "auth"        ],

The available fields in the channels array are as follows:

The available fields in the flow array are as follows:

There are additional product attributes that define the behavior of the products:

Q2 Gro has added a standardized debit card response page to the application page flow. Previously, FIs needed to manually create this page using a custom page, custom questions, and custom configuration. Now, FIs can use Gro's standardized page to capture responses to debit card questions.

To enable this feature, make the following configuration changes in the indicated Type IDs.

{
    "id": "debitCardQuestions",
    "headerLabel": "debitCardPageLabel",
    "nextButtonLabel": "next",
    "products": [
        "chk_platinum",
        "chk_student"    ],
    "location": "#debitCardQuestionsPage",
    "backButton": true,
    "defaultFields": [
        "wouldYouLikeADebitCard",
        "wouldYouLikeADebitCardJoint"    ]
  }

{
    "id": "wouldYouLikeADebitCard",
    "label": "wouldYouLikeADebitCardLabel",
    "defaultValue": false,
    "type": "checkboxDouble",
    "errorMsg": "",
    "display": "vertical",
    "required": true,
    "showFields": {
        "true": [
            "wouldYouLikeOverDraftTransfer"        ]
    }
},
{
    "id": "wouldYouLikeOverDraftTransfer",
    "label": "wouldYouLikeOverDraftTransferLabel",
    "defaultValue": false,
    "type": "checkboxDouble",
    "errorMsg": "",
    "display": "vertical",
    "required": true
},
{
    "id": "wouldYouLikeADebitCardJoint",
    "showIfJoint": true,
    "header": "wouldYouLikeADebitCardHeaderJoint",
    "label": "wouldYouLikeADebitCardLabelJoint",
    "defaultValue": false,
    "type": "checkboxDouble",
    "errorMsg": "",
    "display": "vertical",
    "required": true,
    "showFields": {
        "true": [
            "wouldYouLikeOverDraftTransferJoint"        ]
    }
},
{
    "id": "wouldYouLikeOverDraftTransferJoint",
    "label": "wouldYouLikeOverDraftTransferLabelJoint",
    "defaultValue": false,
    "type": "checkboxDouble",
    "errorMsg": "",
    "display": "vertical",
    "required": true
}

"debitCardPageLabel": "Debit Card",
"wouldYouLikeADebitCardLabel": "Please confirm that you'd like us to mail you a debit card.  It's an easy way to access your funds and make purchases.  I would like to receive a debit card for use with my new checking account.",
"wouldYouLikeOverDraftTransferLabel": "Would you like overdraft transfer plan added?\n\nBy checking “Yes” that you would like overdraft transfer plan added and signing this Overdraft Transfer Plan Request and Designation by checking “Yes” below, I request that FI NAME honor transactions that would overdraw my FI NAME checking account including Automated Teller Machine (ATM) withdrawals and debit card transactions by initiating a transfer of the necessary funds from my savings account and agree that such transfers are subject to the terms, conditions and limitations.",
"wouldYouLikeADebitCardHeaderJoint": "<br><strong class='font-size: 20px;'>For Joint Applicant:</strong>",
"wouldYouLikeADebitCardLabelJoint": "Please confirm that you'd like us to mail you a debit card.  It's an easy way to access your funds and make purchases.  I would like to receive a debit card for use with my new checking account.",
"wouldYouLikeOverDraftTransferLabelJoint": "Would you like overdraft transfer plan added?\n\nBy checking “Yes” that you would like overdraft transfer plan added and signing this Overdraft Transfer Plan Request and Designation by checking “Yes” below, I request that FI NAME honor transactions that would overdraw my FI NAME checking account including Automated Teller Machine (ATM) withdrawals and debit card transactions by initiating a transfer of the necessary funds from my savings account and agree that such transfers are subject to the terms, conditions and limitations." 

Within the pageFlow, pageFlowAuth, pageFlowNative, andjointFlowOverride sections, insert the debitCardQuestionsPage into the workflow, as show below.

"pageFlow": {
  ...
    "#privateInfoPage": "#employmentPageApp1",
    "#employmentPageApp1": "#debitCardQuestionsPage",     "#debitCardQuestionsPage" : "#almostDonePage",     "#almostDonePage": "#walletQPage",
    "#nativeAlmostDonePage": "#walletQPage",
   ...
  },
  "pageFlowAuth": {
   ...
    "#privateInfoPage": "#employmentPageApp1",
    "#employmentPageApp1": "#debitCardQuestionsPage",
    "#debitCardQuestionsPage": "#almostDonePage",     "#collectProductInfoPage": "#privateInfoPage",
   ...
  },
  "pageFlowNative": {
   ...
    "#verifyPhonePage": "#NATIVEPage",
    "#employmentPageApp1": "#debitCardQuestionsPage",
    "#debitCardQuestionsPage": "#almostDonePage",     "#NATIVEPage": "#collectProductInfoPage",
   ...
  },
  "jointFlowOverride": {
    "#validateInfoPageApp2": "#privateInfoPage",
    "#validateInfoPage": "#validateInfoPageApp2",
    "#debitCardQuestionsPage": "#almostDonePage",
    "#privateInfoPage": "#privateInfoPageApp2",
    "#privateInfoPageApp2": "#employmentPageApp1",
    "#employmentPageApp1": "#employmentPageApp2",
    "#employmentPageApp2": "#debitCardQuestionsPage"  }