Application Decisioning - Pav2

preapproval v2 preapproval v2 provides an api set used to validate, submit, and supplement credit application data these apis are tailored, schema driven, and real time, designed to support the full lifecycle of credit applications under versioned credit policies partners are required to send the entire population of credit applications through the preapproval apis, including those that are funded , approved but not accepted , denied , incomplete , withdrawn , and prequalifications providing all application outcomes ensures that cross river bank (crb) can perform the fair banking statistical analyses required under regulatory guidance this complete dataset enables monitoring for potential disparities, supports model governance, and ensures compliance with fair banking and fair lending obligations each endpoint includes a schemaid in the url, representing the data model and validation rules agreed upon between crb and the partner for that schema version schema updates are requested through the change management process (via jira) and updated on our schema builder ui important to access the links below you must have the following ip addresses allowlisted sandbox 66 206 202 39 , 66 206 202 12 production 66 206 202 62 , 66 206 202 15 schema builder and data dictionary ui url https //lendingappsandbox crbcos com/preapproval/schemas https //lendingappsandbox crbcos com/preapproval/schemas the schema builder ui is an interface where partners can view and build together with cross river, the data schema that will be used for their api, according to the partner specific model each schema defines the required and optional fields for the application submission and dry run apis, including data types, validation rules, and field descriptions partners can use this interface to confirm their integration aligns with the agreed upon schema before submitting applications under the finalized and approved schema swagger https //lendingsandbox crbcos com/preapproval/swagger access to ui gaining access to the preapproval v2 schema ui is done via self service on org management portal docid\ c90jfvuq2mwirvdsawxgr your it manager should have admin access, and must add the following to your user role lending preapproval v2 readonly partner associate the partner created for preapproval with your user api suite an application in pav2, is identified by the partner's application id, which should be unique for each application in the partner's system base url for sandbox https //lendingsandbox crbcos com/preapproval base url for production https //lending crbcos com/preapproval api scope for sandbox is coslending\ preapproval\ stg api scope for production is coslending\ preapproval\ prd api description docid\ ptx0f232efvcvlbsyzt6i post or update an application, including the final decision you can call this multiple times, and we will only use the latest, according to application id post /api/v2/applications/{partner schema id}/dryrun this is identical to the above api, but is used only to test the validations and not actually submit the application docid\ igxxxxmwhg0xi ekgsvrd post file attachments to an application attachments are sent in a zip file notes during implementation, cross river and the partner will agree on additional fields to be passed to cross river based on the partner's unique operating model data types and schemas are available directly in the schema ui, as well as descriptions and other goodies that will help you build your api integration partners should ultimately send their final decision when using the api the rules that run when sending in the preapproval api, are informational they do not change the status of the application automatically cross river rules on preapproval when posting an application using the preapproval api, cross river can check the data against a set of regulatory rules and return the rule results in the api response the response body includes rule results in the rule results object, which includes information about the rule and the data used when running the rule if one of the rules fails on preapproval, you can assume it will also fail in arix speak to your {{}}, if you would like rules to run in preapproval currently, there are no webhooks in preapproval the results of the rules are returned synchronously in the response cross river ops cannot manually override the result of a rule in pre approval, as these results are purely informational for our partners to use pre approval rules do not alter the status of an application in pre approval sent in by an mpl the following is an example of a rule results object that contains the cross river internal list rule "rule results" \[ { "status" "success", "rule process date" "2023 09 06", "rule results" \[ { "ruleid" "92bc95b5 fa3c 468a b28b b06800bdb9d7", "version" "v1", "rulename" "internal list check", "ruledescription" "borrower information should not be on bank's internal list", "passed" true, "data" "anita loan 693952xxx,scrooge mcduck 014512994,unonx7enmokldcoxseauxw28serfp3xnelolpl2kopnzcq9n8y )}k;b,)sv8jco 78(yh^eu4|b ", "resultinfo" null } ] } ]