Choose an integration

When you first use Taria Pay, decide which integration path to take. Each requires a different amount of development effort and suits different business scenarios.

Three checkout paths

Integration	Best for	What the merchant does
Hosted Checkout / No-code	Fastest launch, or you don't want to maintain payment UI	Use paylinks, subscription plans, or create a payment order and redirect to `checkoutUrl`
Checkout Button	Adding a payment button to your own checkout page	Your server creates a payment order; clicking the button opens hosted checkout
Checkout Panel	Letting buyers complete a wallet payment without leaving your site	Your server creates a payment order; your frontend embeds the payment panel with the `paymentId`

When to prefer Hosted Checkout / No-code

If you want to start accepting payments as quickly as possible, start with Hosted Checkout / No-code. It's a good fit for:

Creating paylinks in the merchant dashboard and sharing them
Creating subscription plan pages in the merchant dashboard
Your server creating a payment intent and your frontend redirecting to the Taria Pay hosted checkout page

When to prefer Checkout Button

If you already have your own website checkout page but don't want to maintain wallet connections, chain switching, and payment states, choose Checkout Button.

The standard flow is:

The buyer clicks the Taria Pay button on your page.
Your server creates a payment intent.
Your frontend opens the checkoutUrl returned by your server.
Taria Pay notifies you of the payment result via webhook.
Your system updates the order and fulfills it.

When to prefer Checkout Panel

If you want buyers to stay on your website, and you're willing to maintain frontend wallet dependencies and browser testing, choose Checkout Panel.

The standard flow is:

Your server creates a payment intent.
Your server returns only the paymentId to the frontend.
Your frontend renders CheckoutPanel.
Taria Pay notifies you of the payment result via webhook.
Your system updates the order and fulfills it.

When you need full customization

If you already have your own order system, customer system, membership system, or backoffice workflows, choose the API / SDK. That way you keep your own order numbers, customer data, inventory, and fulfillment logic.

Not sure which to pick

You can take your first real payment with a paylink, then integrate Checkout Button or Checkout Panel later. This lets you validate that buyers are willing to pay with stablecoins before investing in development.

Choose an integration ​

Three checkout paths ​

When to prefer Hosted Checkout / No-code ​

When to prefer Checkout Button ​

When to prefer Checkout Panel ​

When you need full customization ​

Not sure which to pick ​