> For the complete documentation index, see [llms.txt](https://docs.pandablue.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandablue.com/api-reference-1/fragment-sdk/overview.md).

# Overview

### What is Cards SDK about?

Our SDK is designed to simplify the process of integrating payments into your application, allowing you to handle payments securely and efficiently without needing to meet strict PCI requirements. We offer two integration modes:

1. **With User Interface**: Ideal for quick and easy integration with a ready-to-use user interface, and very customizable.
2. **Without User Interface**: Perfect for those who need a more customized integration and full control over the payment process.

### Benefits of Using Our SDK

* **Easy to Integrate**: With straightforward instructions and code examples, you can have the payment system up and running in no time.
* **Secure**: Our system complies with the highest security standards, eliminating the need for your application to be PCI compliant.
* **Customizable**: We offer customization options to match the look and feel of your application.

### Select the SDK type that suits best for you!


---

# 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.pandablue.com/api-reference-1/fragment-sdk/overview.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.