Skip to main content
Preview. The Payments API (V3) is live at https://api.tagada.io/v1, but it is not open to self-serve integrations yet: merchant secret keys cannot be created from the dashboard. Every merchant processes on V2 today. Contact api-support@tagadapay.com if you plan a new integration.
The Payments API is TagadaPay’s new payments interface, also called V3. It replaces the payment calls of the Commerce API (V2) with one resource, the Payment, and one way to drive it: create on your server, confirm in the browser, follow next_action until the payment reaches a final status.

​
How it works

  1. Your server creates a payment with a secret key. The response carries a client_secret.
  2. Your page passes the client_secret to the browser client, @tagadapay/core-js/payments-v3, which holds a publishable key (tpk_).
  3. The browser confirms the payment. If the bank or the payment method needs the shopper, the payment moves to requires_action and carries a next_action (3DS, redirect, wallet confirmation). The browser client performs it.
  4. The payment ends in succeeded, requires_capture, failed or canceled. Your server reads it to fulfil the order.

​
What the API covers

The full list is in the API reference.

​
Conventions

​
Release phases

​
Next steps

V2 or V3?

Which API to use for a new or existing integration.

Payment lifecycle

Statuses, client_secret and next_action.

Browser client

Card fields, wallets and confirmation with core-js/payments-v3.

Migrate from V2

What changes, what stays, and the per-store switch.