Skip to main content

SaaS Billing with TagadaPay

Time: ~20 minutes | Difficulty: Intermediate Bill subscriptions from your own SaaS app — not a storefront, not a funnel. You keep your UI; TagadaPay handles vaulting, routing, and recurring charges across any processor or TPA.
This guide is for SaaS builders migrating from Stripe Billing or building subscription billing from scratch. For e-commerce storefronts, see Build a Store with AI.

Why TagadaPay for SaaS (vs Stripe)

The killer feature: payment flows. Connect as many TPAs and processors as you want. If one TPA is banned, add a fallback in the flow — cards stay vaulted, rebills keep working.

Architecture: frontend vs backend

Package: @tagadapay/core-js
  • Tokenize the card → tagadaToken
  • Handle 3DS if the charge asks for it (requireAction: 'redirect' → send the customer to the processor’s hosted page; standalone 3DS sessions are only for gateway-style processors like NMI — see Quick Start)
  • Never put your CRM API key in the browser

Working example

Everything in this guide was tested against production. Clone and run:
Open http://localhost:5173, click Subscribe, and watch the flow log.

Next steps

Quick Start

Step-by-step: product → checkout → subscription in 15 minutes

Payment Flows

Multi-TPA routing, cascade, failover — the Stripe killer

Migrate from Stripe

Object mapping and cutover playbook

Subscriptions API

Rebilling, trials, cancel, processor migration