> For the complete documentation index, see [llms.txt](https://even-financial.gitbook.io/developer-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://even-financial.gitbook.io/developer-center/marketplace-integrations/mobile-sdks/credit-cards.md).

# Credit Cards

Embed the Engine Credit Cards marketplace inside your mobile app.

Engine's Credit Cards Mobile SDK embeds the full credit card marketplace journey directly inside your app. It's available for React Native, Flutter, Kotlin, and Swift.

{% hint style="info" %}
The Credit Cards SDK renders the full marketplace experience inside your app as a native component, configured through native props and event callbacks — see [Mobile SDKs](/developer-center/marketplace-integrations/mobile-sdks.md) for more.
{% endhint %}

## User Experience & Demo

The SDK renders a complete Credit Cards journey inside your app. It collects any missing user inputs, submits the lead, and then displays offers.

Typical flow:

1. Landing screen
2. Personal details form
3. Offer results

<div><img src="https://3849802388-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeMvVDbjd8vJWZ9Hwf0%2Fuploads%2Fgit-blob-fca9c5af4d7ca6be76b538ea5d801426e86d0859%2FCC%20SDK%20Landing.png?alt=media" alt="Landing Screen" width="324"> <img src="https://3849802388-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeMvVDbjd8vJWZ9Hwf0%2Fuploads%2Fgit-blob-7a26fd3f56331b9b415694a7500241899645efbb%2FCC%20Personal%20Details.png?alt=media" alt="Personal Details" width="324"></div>

<div><figure><img src="https://3849802388-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeMvVDbjd8vJWZ9Hwf0%2Fuploads%2Fgit-blob-511ae343836bb17a61452dab053855b274752d4e%2FCC%20Personal%20Details%202.png?alt=media" alt="" width="324"><figcaption><p>Personal Details</p></figcaption></figure> <figure><img src="https://3849802388-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeMvVDbjd8vJWZ9Hwf0%2Fuploads%2Fgit-blob-9556f84f9bd43c22856fed6f1e17f309f4c7a4e6%2FCC%20Personal%20Details%203.png?alt=media" alt="" width="324"><figcaption><p>Personal Details</p></figcaption></figure></div>

<div align="center"><figure><img src="https://3849802388-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeMvVDbjd8vJWZ9Hwf0%2Fuploads%2Fgit-blob-79db3deabf7a5d4eb26102f51458648ec1240b28%2FCC%20Personal%20Details%204.png?alt=media" alt="" width="324"><figcaption><p>Personal Details</p></figcaption></figure> <figure><img src="https://3849802388-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MeMvVDbjd8vJWZ9Hwf0%2Fuploads%2Fgit-blob-88bf1a0939fbe4573fe5fad038ee948b50eb8e62%2FCC%20Personal%20Details%205.png?alt=media" alt="" width="324"><figcaption><p>Personal Details</p></figcaption></figure></div>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://even-financial.gitbook.io/developer-center/marketplace-integrations/mobile-sdks/credit-cards.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.