Simulate Application Denial

Warning: The Highnote test environment allows you to freely explore the platform features and functionality. It is intended for experimenting, building integrations, and training your team.

To ensure the security of your real-world data, please refrain from entering production data into the test environment. Production data includes sensitive information like customer details, financial data, or personally identifiable information (PII).

Use only dummy or test data explicitly created for testing purposes in the test environment.

When a credit card application is denied, regulations require you to provide the customer with Adverse Action (AA) reason(s) for the denial within 30 days. This is a requirement to promote credit availability to all creditworthy applicants and ensure the credit decision is based on creditworthiness.

Adverse Action (AA) reasons are assigned and associated with each rule within your Product's credit policy and are populated based on the rules which failed in the credit decision. For example, if your credit policy has a rule that the Annual Business Revenue provided in the application must be greater than a specified amount, the application may be DENIED with the AA reason of "Income insufficient for the amount of credit requested."

If you use Collaborative Application Decisioning, you must provide the applicable Adverse Action Reasons in a DENIED response, based on your underwriting decision and credit policy's rules.

For a complete Adverse Action Reason Codes list, see the API Reference.

You can simulate denied responses by entering simulation values for legalBusinessName, annualRevenue, and totalAnnualIncome. For more information on simulating adverse action decline, see Simulate Credit Adverse Action Decline.