If you have a Developer Portal account conditioned appropriately, you can use the information below to perform non-Happy Path testing for both Flexiti’s POS and Online API’s.
In the Flexiti Apply flow the adjudication response will be predicated by the Response Key value entered as the middle name for the applicant, as follows:
Scenario Description | Response Key | Response | Response Description |
|---|---|---|---|
Applicant failed pre-bureau data checks from the application leading to a decline decision. | D-MISSING_INFO | Decline | Decline message for missing info |
Applicant failed pre-bureau data checks from the application leading to a pending decision. | P-REVIEW_MISC | Pending | Standard pending message |
Applicant has been declined for a duplicate application match. | D-DUPLICATE | Decline | Duplicate decline message |
Applicant has a possible match to an existing customer leading to a pending decision. | P-EXIST_CUST | Pending | Standard pending message |
Applicant has no matching credit bureau record, leading to a decline decision. |
| Decline | Standard decline message |
Applicant has been approved (there is one response key for each risk rating). |
| Approved | Standard approval message |
Applicant has been declined (there is one response key for each risk rating). |
| Decline | Standard decline message |
Applicant has been queued for credit reasons | P-CREDIT | Pending | Standard pending message |
Applicant has been queued for fraud warnings | P-FRAUD | Pending | Standard pending message |
Applicant has been declined due to failed Bureau/Device authentication | D-FRAUD | Decline | Standard decline message |
Applicant will need to retry due to third party timeout | D-EMAIL_DBL_TIMEOUT | Retry | Web event emitted from the widget to retry the application |