# Welcome!

Our API facilitates interoperability among various QR systems in Latin America, allowing wallets and mobile applications to scan and process QR codes from different countries through simple integration. This connection ensures that transactions are carried out efficiently and securely, complying with international payment standards. 

## Welcome to Depay API

Welcome to Depay API! Here you'll find all the documentation you need to get up and running with the API.

## Migrate from v1.0 to v2.0

Version 2.0 of the API introduces structural improvements aimed at increasing consistency and precision in financial data handling. One of the key updates includes the standardization of numeric values by changing the type of several amount fields to `DECIMAL`. These changes apply to different endpoints, including QR Preview and DictKey responses.

While the complete list of required adjustments is detailed in the migration section, it is important to note that these modifications are essential for ensuring compatibility with v2.0 and preventing integration issues. [See changes.](https://docs.payments.depay.us/reference/migrate-to-v2.0)

## Want to jump right in?

Feeling like an eager beaver? Jump into the quick start docs and get making your first request:

{% content-ref url="quick-start" %}
[quick-start](https://docs.payments.depay.us/quick-start)
{% endcontent-ref %}

## Want to deep dive?

Dive a little deeper and start exploring our API reference to get an idea of everything that's possible with the API:

{% content-ref url="reference/api-reference" %}
[api-reference](https://docs.payments.depay.us/reference/api-reference)
{% 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.payments.depay.us/welcome.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.