> 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/integration-guides/choosing-the-right-type-of-integration.md).

# Choosing the right type of integration

When integrating a payment gateway into your system, selecting the appropriate integration method is crucial for ensuring a smooth and efficient transaction process. This guide will help you understand the available integration types, their use cases, and the criteria for making the best decision for your business needs. 

The three primary integration types are:

1. Hosted Payment Page
2. Direct API
3. Hosted Component (Coming Soon)

<details>

<summary>Hosted Payment Page</summary>

The Hosted Payment Page method involves directing the customer to a secure, hosted payment page provided by Coda. This page is responsible for collecting payment information and processing transactions.

**Advantages**

* Simplifies PCI compliance and handling of PII data since sensitive payment data is handled by Coda.
* Quick and easy to implement, reducing development time.
* Supports various devices, including desktop browsers, mobile browsers, and in-app web

**Criteria for Use**

* You prefer a simple and quick integration with minimal technical overhead.
* You need to support multiple payment channels without extensive development.
* You want to offload PCI compliance responsibilities to Coda.

</details>

<details>

<summary>Direct API</summary>

The Direct API method allows you to integrate directly with Coda’s backend services, offering more control and customization over the payment process

**Advantages**

* Full control over the user interface and payment flow, enabling a customized payment experience.
* Direct communication with Coda’s services allows for advanced features and integration.
* Suitable for businesses needing a tailored payment experience.

**Criteria for Use**

* You require a highly customized payment process tailored to your business needs.
* Your business can handle the complexities of PCI compliance.
* You have the technical resources to implement and maintain the integration.

</details>

<details>

<summary>Hosted Component </summary>

The Hosted Component integration provides a prebuilt UI component that you can embed directly into your existing checkout flow. This method offers a balance between ease of implementation and a seamless user experience, as Coda is not visible to the end user during the purchase process.

**Advantages**

* Reduced Development Effort: Utilize a pre-built UI component to minimize the technical resources required for implementation.
* Seamless Brand Experience: Maintain full control over the user interface visibility, keeping the Coda branding hidden from the customer.

**Criteria for Use**

* You want an embedded experience: You prefer to keep the customer on your own site or app during the entire payment process.
* You have technical resources: You possess the necessary front-end development resources to embed and maintain the UI component.

</details>

<figure><img src="/files/GYN4hpmui3gdNl8IZvyB" alt=""><figcaption></figcaption></figure>

### Making the Decision

To decide which integration type suits your needs, consider the following criteria:

* **Technical Resource Availability:** If your team has limited development resources or expertise, the Hosted Payment Page is the better option due to its simplicity and ease of implementation.
* **Customization Needs:** If you need a highly customized user experience and have the technical capability to manage PII data, the Direct API provides the flexibility you require.
* **Compliance Requirements:** For businesses looking to minimize their PCI compliance burden, the Hosted Payment Page offers a significant advantage by offloading sensitive data handling to Coda.
* **Speed to Market:** If you need to launch quickly, the Hosted Payment Page allows for faster implementation and leverages Coda’s optimized and user-friendly interface.
* **Performance:** The Hosted Payment Page benefits from Coda's years of optimization, ensuring a high-performance, reliable payment process that can enhance user satisfaction.

By understanding the features and requirements of each integration type, you can make an informed decision that aligns with your business goals, technical capabilities, and timeline.

***

### Comparison between available integrations

<table data-full-width="true"><thead><tr><th width="174">...</th><th width="254">Hosted Payment Page</th><th width="215">Direct API</th><th>Hosted Component</th></tr></thead><tbody><tr><td></td><td><img src="/files/7h8T4etzcGdN9uUSzP80" alt="" data-size="original"></td><td><img src="/files/t2Dv4yUsiaNgE1E9W9Zu" alt="Caption text" data-size="original"></td><td><img src="/files/hdKKe3ifYvgZthFJRi4a" alt="" data-size="original"></td></tr><tr><td><strong>Customer interface</strong></td><td>A page designed and hosted by Coda on which a customer can initiate a purchase for onechannel. Coda can also customise this with publisher branding.<br><br>*Optional: <strong>Payment</strong> <strong>Channel Selection Page</strong><br>A page designed and hosted by Coda on which a customer can select from a variety of channels.</td><td>A set of APIs to integrate Coda’s payment channels into your own UI.</td><td>Prebuilt UI component to embed in your checkout flow.</td></tr><tr><td><strong>Who presents payment Information to end user?</strong></td><td>Coda</td><td>Publisher</td><td>Publisher</td></tr><tr><td><strong>Is Coda visible in purchase flow?</strong></td><td>✅</td><td>❌</td><td>❌</td></tr><tr><td><strong>Typical conversion rate</strong></td><td>High</td><td>Variable</td><td>Variable</td></tr><tr><td><strong>Integration complexity</strong></td><td>Low</td><td>High</td><td>High</td></tr><tr><td><strong>What payment methods are available?</strong></td><td>All</td><td>Selected</td><td>Selected</td></tr><tr><td><strong>How to get started?</strong></td><td><ul><li><a href="/pages/22IQChE6CwUnRx17X7mC"><mark style="color:blue;"><strong>Hosted Payment Page guide -></strong></mark></a></li><li><a href="/pages/6noelPac6O8nyEfCRV8d"><mark style="color:blue;"><strong>Payment Channel Selection Page guide -></strong></mark></a></li></ul></td><td><a href="/pages/B3BLc89e4XKu5XbrOGvV"><mark style="color:blue;"><strong>Follow this guide -></strong></mark></a></td><td><a href="/pages/QiFMApq4YFqNEbQ6wfOx"><mark style="color:blue;"><strong>Follow this guide -></strong></mark></a></td></tr></tbody></table>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coda.co/codapay/integration-guides/choosing-the-right-type-of-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.