> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/in-app-payments.md).

# In-App Payments

In-app payments eliminate friction in the checkout experience, allowing users to complete transactions without ever leaving the app. By embedding payments directly into the mobile experience, businesses can drive higher conversions, encourage repeat purchases, and reduce reliance on traditional app stores.

With Codapay’s In-App Payments, you unlock:

* **Seamless experiences** – keep users engaged in your app with smooth, localized payment flows
* **Global reach** – access hundreds of payment methods across 70+ countries with a single integration
* **Faster growth** – increase conversion and retention by reducing drop-off during checkout
* **Peace of mind** – Codapay manages compliance, security, and fraud prevention so you can focus on growth
* **Flexible integration options** – choose **Native Integration** (SDK-based, fully in-app) or **Link-Out Redirection** (hosted page, quick rollout)

Whether you prioritize speed of integration or the most seamless user journey, this section will guide you through the right approach for your app.


---

# 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://docs.coda.co/codapay/in-app-payments.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.