Delayed Funding is a feature available from the Gro Admin Portal that allows FI employees with the Application Support user role to collect funding information from a referred applicant. When enabled, applicants can still enter funding information using ACH transfers only, even if they don't pass KYC or other validation checks. After providing funding information, the applicant is presented with the following message:
In order to successfully run delayed funding, there are a few prerequisites:
-
The app must have been referred via KBA, challenge questions, OLB, or cores submission.
-
The user must have provided their ACH funding information on the Funding page.
-
Unless the FI has no core, they must trigger core submission before delayed funding. Otherwise, delayed funding will fail due to no account number.
After verifying the referred application, complete the following steps from the Application Details page:
-
Select Run Delayed Funding from the Actions dropdown, as shown in the image below.
-
Select the applicant to run Delayed Funding for, then select Run Delayed Funding (Criteria will be ignored).
Note
If there isn't a joint application, this will show as Run.
-
If the applicant provided funding account information in their application, the account will be funded using that information.
-
If the applicant didn't provide funding account information in their application, an error message will say, "Perform Portal Action - Couldn't run delayed funding, ACH information is missing for application: [application number]."
-
To verify if Delayed Funding was successful, check internal comments at the bottom of the application.
To enable Delayed Funding, add the following configuration to the server.workflow.service.funding.delayedFunding Type ID:
{
"enabled": true,
"fundingOptions": [
"ACH"
]
}
Note
The configuration above is included in the Gro Admin Portal by default, however the enabled property will be set to false by default.
Add the following configuration to the server.workflow.service.custom.portalAction Type ID:
{
"portalActions": [
{
"workflowStep": "delayedFunding",
"criteria": {
"products": [
"all"
],
"applicationAttribute": {}
}
}
]
}
Add the following configuration to the server.workflow.service.custom.portalActionSettings Type ID:
{
"delayedFunding": {
"settings": {},
"className": "delayedFundingStep"
}
}