Developer Center
Back to Engine.tech
  • Welcome!
  • Top of Funnel Applications
    • Embeddable Calculators
      • Embeddable Personal Loan Calculator
      • Embeddable Debt Consolidation Loan Calculator
      • Embeddable Personal Loan vs Debt Relief Calculator
      • Embeddable Savings Calculator
      • Adding Your Client Tags for Reporting Attribution
  • Loans / Savings / Second Look Marketplace
    • Hosted Integrations
      • Partner Pages / Embeds
        • Loans Partner Pages
          • Frond-End Customization Options
          • Preferred Look Partner Pages
          • Bridge Partner Pages
          • Special Offer Partner Pages
        • Loans Embeds
        • Pre-Populating Existing Customer Data
        • Adding Your Client Tags for Reporting Attribution
      • Mobile SDK
        • Mobile SDK - Prefilling Lead Data
        • Adding Your Client Tags to Reporting for Mobile SDK Integrations
        • Event Handlers for Real-Time Tracking in the Engine Mobile SDK
    • Native API (Build Your Own)
      • Financial Product Verticals
        • Loans
          • Personal Loans
            • Collecting User Information for Personal Loans
            • Displaying Personal Loan Offers
            • API Specifications
            • FAQs
          • Home Equity Line of Credit (HELOC)
            • Displaying Offers HELOC
            • Risk Factors & Requirements
            • Dos & Don’ts for All HELOC Supply Partners
            • Dos & Don’ts for HELOC Native Partners (API)
            • Our Embed/Partner Page Implementation
            • HELOC-specific disclosures
          • Auto Loan Refinancing (ALR)
            • Collecting User Information
            • Displaying Auto Loan Refinance Offers
            • API Specifications
            • FAQs
        • Savings
          • Collection User Information for Savings
          • Displaying Savings Offers
          • Marketplace Display Requirements
          • Reporting
          • API Specifications
        • 2nd Look Marketplace
          • 2nd Look Marketplace (Financial Services Providers)
          • 2nd Look Marketplace (Channel Partners)
            • Collecting User Information for 2LM
            • Displaying 2L Marketplace Offers
      • Adding Your Client Tags to Reporting for Native API Integrations
      • General Compliance Guidelines
        • Consumer Information Fields
          • Additional Compliance Recommendations & Best Practices
        • Disclosures
        • Consents
        • Offer Display Fields
    • Reporting Options for Channel Partners
      • Channel Partner Reporting - Looker
      • Channel Partner Reporting - Analytics API
  • Credit Cards Marketplace
    • Native API (Build Your Own)
      • Getting Started
      • Flow Design
      • Collecting User Information for Credit Cards
      • Displaying Credit Card Offers
      • API Specifications
      • Compliance Guidelines
  • New Marketplaces (Credit Builders, Earned Wage Access, Debt Relief)
    • Hosted Integrations
      • New Marketplaces Embeds
      • Adding Your Client Tags for Reporting Attribution
  • References
    • Brand Guidelines and Assets
    • Appendix
      • Appendix A - Notices
      • Appendix B - Disclosures
      • Appendix C - Consents
      • Appendix D: API Field to Offer Card Mappings
      • Appendix E: Appending Client Tags for Partner Page and Embed Integrations
Powered by GitBook
On this page
  • Search Entry Point
  • Compare Offer Display
  • Recommendations for Native API Integrations
  • Best Practices for Displaying Offers

Was this helpful?

  1. Credit Cards Marketplace
  2. Native API (Build Your Own)

Flow Design

PreviousGetting StartedNextCollecting User Information for Credit Cards

Last updated 1 month ago

Was this helpful?

This section provides design samples from our experiences, which you can reference to guide the design of your own experience.

Search Entry Point

To search for credit card offers, there are various entry points for leads to enter the funnel. Below is an example.

Clicking on “See all offers” directs the user through the search flow, where they will answer a series of questions to receive personalized, preselected offers tailored to them.

In the example below, the user selects a benefit option to enter the search funnel. The search quiz is then customized based on their selection, and the credit card offers are tailored to their preferences.

Below is an example of Engine’s Credit Cards partner page, where the user enters the search funnel by clicking on “Get Pre-Approved”.

Search Flow Questions

In the search flow, we ask users a series of questions to help them receive preselected offers. Most of these questions are required by our partners to ensure eligibility and increase the likelihood of issuer approval.

The first question is Card Purposes. This question is optional; however, including it can provide valuable insights into the types of benefits the user is seeking and help display cards that align with their preferences. Additionally, displaying the Mobile Carrier Disclosure is not required, as it is specific to our flow.

The next question is Annual Income. Annual income is mandatory to provide users with Pre-approved, Pre-Qualified or Pre-Selected credit card offers.. We also provide a disclaimer to clarify what should be included in the annual income. This disclaimer is required for compliance purposes:

“List your total available income, including wages, retirement, investments, and rental properties”

The next questions in the flow are Phone Number and Date of Birth, both of which are required to check a user’s eligibility for credit cards.

  • Phone Number: This is used to send users personalized offers via text messages, ensuring they can easily access their tailored credit card options.

  • Date of Birth: This information helps validate the user’s identity and ensures they meet the age requirements set by our credit card partners.

The next question is First Name/Last Name. This information is used to verify the user’s identity and access their credit history without impacting their credit score.

The following question is Address/City/State/Zip Code. This information helps verify the user’s identity and ensures they are provided with credit card offers available in their region. We use google powered address autocomplete feature to assist in typing address and making sure it is correct.

The final question is Email Address. This is used to share personalized credit card offers and to communicate important updates about their application or recommendations.

Once a user clicks on See My Offers, they are directed to this page while we match them with relevant credit card offers and generate a rate table with all available offers. The wait time for this process may take up to 15 seconds.

Compare Offer Display

Recommendations for Native API Integrations

Engine recommends that partners building a Native API integration display offers with isITA: false with the highest recommendation scores first, followed by offers with isITA: true.

Best Practices for Displaying Offers

isITA: false

  • These offers should be grouped together, badged for clarity (e.g., "Pre-Approved"), and displayed prominently.

  • Here are the badges recommendations:

Credit Card Offer Details
Recommended Badge
Show Disclaimer

  • preQualified: false

  • preApproved: false

  • preSelected: false

Do not show any badge for the offer

preApproved: true

Show Badge “You are Pre-Approved”

We have conducted a preliminary review based on the information you provided and think that you have an excellent chance of being approved for this offer. Final approval will still require a credit check and verification of your financial details by the issuing bank.

preQualified: true

Show Badge “Good chance of approval”

Your credit profile suggests you’re likely to be approved for this offer. Final approval will still require a credit check and verification of your financial details by the issuing bank.

preApproved: true

Show Badge “Credit profile matched”

Based on your credit profile, there is a reasonable chance you may be approved for this offer. Final approval will still require a credit check and verification of your financial details by issuing bank.

isITA: true - These can be placed in a separate section and the badges field in offer response can be used to determine what badge to display for each ITA offer.

Here is an example from Engine-owned experiences for your reference: