Taria Pay Docs

English

简体中文

English

简体中文

Appearance

FAQ ​

This page answers the questions merchants ask most often while onboarding, integrating, testing, and going live.

Which pages should I read first ​

If you're new to Taria Pay, we recommend this order:

  1. What is Taria Pay
  2. Pricing
  3. Choosing an integration
  4. Using the Dashboard

If you're integrating payments into your website, go straight to:

  1. Quickstart
  2. Creating a payment order
  3. Receiving payment results

I just want to start accepting payments quickly, without changing my website first ​

Start with payment links or subscription plans.

They're a good way to start collecting payments first, and decide later whether to integrate Taria Pay more deeply into your website.

I want to add Taria Pay to my own website — where do I start ​

Start with the Quickstart.

The recommended approach is to have your own server create the payment intent, then return the checkoutUrl to your frontend for the redirect.

Where do I configure API keys and webhooks ​

On the Developers page in the Dashboard:

  • API Keys: create and revoke test / live keys
  • Webhooks: create endpoints and get the signing secret
  • Delivery Logs: view webhook delivery results and failure reasons

The customer paid, but the order status on my site hasn't updated ​

Check first:

  1. Whether the webhook endpoint is configured.
  2. Whether the webhook signing secret is correct.
  3. Whether your server verifies the signature and returns 2xx.
  4. Whether your order-update logic is idempotent on paymentId or orderId.
  5. Whether Delivery Logs show failed deliveries.

Continue reading: Troubleshooting payments

The buyer reached the success page — can I ship now ​

Not necessarily. successUrl only means the buyer's browser returned to your website. Shipping, granting access, and bookkeeping should be based on the webhook payment-confirmation event or the query API.

Do I need to pass a chainId when creating a payment order ​

Usually not. When your server creates a payment intent, providing the order ID, amount, currency, and redirect URLs is enough. The checkout page shows the currently available payment networks.

Can I control which payment methods the checkout shows ​

Yes. Use the optional paymentMethods field when creating a payment order: you can turn off the wallet module or direct transfer (not both), and you can make the transfer section open by default. Omitting the field keeps the default (both shown, transfer collapsed). See Create a payment.

Can buyers who don't use a wallet still pay ​

Yes. On supported networks, in addition to wallet payments the checkout page offers direct transfers: it shows a deposit address and QR code dedicated to that order, and the buyer simply transfers from an exchange withdrawal or any wallet using the network, currency, and amount shown — the payment is confirmed automatically on arrival. No integration changes are needed on your side, and the webhook events are identical to wallet payments. See Supported payment methods.

Yes. Checkout links are now unified as checkout.tariapay.com/ plus a typed-prefix ID (such as pi_…, pl_…, su_…), but every old-format link you've already shared will keep working — no need to re-share anything. The checkoutUrl returned by the API is always the current authoritative form; just use it as-is.

What if I need human support ​

Email support@tariapay.com.

Please include:

  • Your merchant email
  • Your order ID
  • The paymentId
  • The transaction hash
  • A screenshot of the problem page
  • The approximate time the issue occurred