This section builds on the AA + PDF flow. Enabling checks does not change how you call any endpoint — it only adds the optional
checks_overrides field to the Initiate Consent request and a checks object to each account in the responses.How checks are enabled
- The set of checks that run for your product — and the parameter names they use — is agreed during onboarding. To enable checks or change which ones run, contact support@moneyone.in.
- Each check has a threshold (for example, a minimum salary amount) that is configured per product at MoneyOne’s end. With thresholds configured this way, you do not need to send anything extra on your requests — checks run automatically during the journey.
Overriding thresholds per request
If you want to use a different threshold for a particular request, pass the optionalchecks_overrides field in the Initiate Consent body. It is a simple set of key→value pairs, where each key is the name of a configurable check and each value is the threshold to use for that request.
Optional. A set of per-request thresholds for the business-rule checks evaluated during the journey. Each key is the parameter name of a configurable check and each value is the threshold that check is evaluated against for this request.
- Pass values in
checks_overridesto set thresholds dynamically for this request. - Omit the field to use the threshold configured for your product — no API change is required.
- A key that does not match a configurable check is ignored.
- The set of configurable checks and their parameter names is agreed during onboarding. To enable or change them, contact support@moneyone.in.
Next steps
Once checks are enabled, the outcome appears on each account in your responses. See Track Status and Fetch Raw Data for where thechecks object appears.