Forcing an outcome
Some applicant names force a decision regardless of the company. The environment matches on the applicant’s name, so the same identity works on consumer, business and corporate onboardings.
The environment decides these at submission, so the response to your
POST already carries the
final status. There is nothing to poll for.
Consumer
The credit decision on a consumer onboarding comes from the applicant, not a company, so the applicant has to be an identity the environment knows. Use the identities above to force a rejection or a failure — those three come back decided on thePOST, which is why they show no PROCESSING.
The environment matches Lena Probst on both the name and the date of birth. A different date of
birth fails with INTERNAL_ERROR, and so does a different name on 1993-03-22. The three forced
outcomes above go by name alone, except Kyc Denial, which also needs its date.
Business
On a business onboarding the applicant is personally liable for the company’s debts, so the credit decision follows the applicant rather than the company. That makes the applicant part of the test data. Where the table names one, use that name and date of birth, because the environment only scores identities it knows.
No register holds a freelancer or a GbR, so you identify both by tax number (
1234567891234), and
both always trigger a document request. A GbR also needs a second partner named as co-signer.
Corporate
The credit decision on a corporate onboarding comes from the company, and most companies pass through a review step on the way to signing. Nothing scores the applicant here, soany in the
table below is literal. Name, date of birth, place of birth and address can be anything at all.
HRB125567 is the one exception, matched on both the name and the date of birth. Either of its two
registered signatories works as the applicant, and the other becomes the co-signer.
HRB99999999 and HRA 3774 are not register numbers the environment can resolve, so both prove
that an unrecognised company produces a document request rather than a rejection. HRA 3774 is
written with a space because that is the form our own tests use — HRA3774 behaves exactly the
same, so the space is not what makes it unresolvable.
Reaching a parked review
HRB300004 is the company to use when you need to see AWAITING_MANUAL_REVIEW and act on it. It
waits for a person rather than clearing on its own, so the status holds instead of passing through
in a few seconds.
HRB300005 does the same for AWAITING_DOCUMENT_REVIEW. Its uploaded documents wait for a person,
while HRB300001’s are approved automatically about 10 seconds after upload. On the way, HRB300001
can briefly report AWAITING_DOCUMENTS again before it moves to AWAITING_SIGNING.