# Payments SDKs (v1)

{% hint style="danger" %}
We are migrating to V2 soon, and all the payments SDK for V1 will become deprecated

in V2 you don't need to have a backend for your application - all the catalog management is performed through our [Management Dashboard](/developer-tools/management-dashboard.md) / [API](/developer-tools/api/api-v2.md)
{% endhint %}

Our Payment SDKs offer a streamlined and straightforward implementation of our payment solutions, serving as versatile building blocks that cater to a wide range of use cases and scenarios.

{% hint style="success" %}
Before diving into implementing our payment solutions, get in touch with us to discover the perfect fit for your needs and receive an API key to bring your web3 integration to life.
{% endhint %}

{% hint style="info" %}
 We recommend using our [quick integration guides](/getting-started/token-checkout-or-payments.md) for step-by-step instructions on seamlessly implementing our payment solution into your application.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>F<strong>rontend SDKs</strong></td><td>Frontend SDKs for a wide range of frameworks, including React, Next.js, React Native, and vanilla JS + HTML.</td><td><a href="/pages/0GnEhCJGkkJuvYJeMd2B">/pages/0GnEhCJGkkJuvYJeMd2B</a></td></tr><tr><td><strong>Backend SDK</strong></td><td>Take a look at our backend SDKs and implement them in your backend, whether you're using Express.js, NestJS, or any other framework.</td><td><a href="/pages/979CGcru5juNEQeMtDxT">/pages/979CGcru5juNEQeMtDxT</a></td></tr></tbody></table>


---

# 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.paytweed.com/developer-tools/tweed-sdks/payments-sdks-v1.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.