# API Acquiring overview

Inqud offers an API-only crypto acquiring solution for businesses seeking a high degree of customization and control over their cryptocurrency payment processes. This option provides the utmost flexibility, allowing you to craft a unique payment experience while leveraging Inqud's robust backend processing capabilities.

<figure><img src="/files/PiiClOqTMgjNGSRUF5YR" alt="" width="375"><figcaption></figcaption></figure>

## **Tailored user experience**

The API-only acquiring option empowers you to design a payment flow that aligns precisely with your business requirements and user preferences. You have full control over the user interface and payment journey, ensuring a seamless and brand-consistent experience.

## **Deep Integration**

Integrate cryptocurrency payments deeply into your platform, incorporating them seamlessly into your existing systems and workflows.

## **Scalability**

Inqud's API is designed to handle high volumes of transactions, ensuring that your business can scale and grow without encountering payment processing limitations.

## **Begin on Your Crypto Widget Journey**

{% content-ref url="/pages/VTOwspRFEcoV4u1zf6aW" %}
[Get Started](/crypto-widget/get-started-1.md)
{% endcontent-ref %}

## Integration Guide

{% content-ref url="/pages/I42kLXTBO483hBvSgmAD" %}
[Using your own UI with Inqud processing](/crypto-widget/integration/using-your-own-ui-with-inqud-processing.md)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://docs.inqud.com/crypto-widget/overview/api-acquiring-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.