...
Note |
---|
Note: While testing apply flows in the Training or Merchant Integration environments you will not receive an SMS or Email pin - just enter 2222 as the pin value in the widget. You (On the purchases however, you will receive a dynamic pin for purchases however pins to the email and or phone you’ve you have set up in the Developer Portal in the Validation tab). |
Scenario Description | Response Key | Response | Response Description |
---|---|---|---|
Applicant failed pre-bureau data checks from the application leading to a decline decision. |
P-MISSING_INFO |
Pending |
Pending 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 approved/declined (there is one response key for each risk rating). |
| Decline if standard account is not enabled, Approved otherwise | Standard decline/approved 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 |