Skip to content
TX TuxoPay
Start building

Route every payment with precision.

One routing layer for Stripe, Whop, PayFast and more. Decide which gateway takes each payment, retry when one declines, and keep your checkout code unchanged.

Start building Read the docs

Six gateways connected once. Unlimited flows on every plan.

Routing decision card-checkout-eu

POST /api/payment-flows/initiate

49.99 USD / DE / card

Rules

Business hours
09:00 to 22:00 CET
pass
Country filter
DE allowed
pass
Amount per period
48,120 of 50,000
pass

Strategy failover

  1. Stripe EU declined
  2. PayFast ZA skipped
  3. Whop approved
Webhook forwarded payment.approved
Every decision is recorded like this, for every payment.

Connect once

  • Stripe
  • Whop
  • PayFast
  • NOWPayments
  • OpenPay
  • Blackpay

See where the money goes.

Revenue, acceptance rate and gateway share on one screen, with the previous period drawn alongside. When a provider starts declining, you see it the same hour, not on the monthly invoice.

TuxoPay analytics dashboard showing revenue over time, transaction volume and success rate across gateways

Draw the route. Publish it. Change it without a deploy.

  1. 1

    Connect each gateway once

    Credentials, callbacks and event models live in one place. Your application talks to TuxoPay only.

  2. 2

    Publish a routing policy

    Attach rules for geography, amount, time of day and gateway health to a flow, then pick a strategy.

  3. 3

    Adjust in production

    Shift traffic between providers from the console. The flow name your checkout calls never changes.

TuxoPay flow builder canvas routing an incoming payment through a failover strategy to Stripe, PayFast and Whop

Everything between checkout and the gateway.

Routing, retries and reporting in one console. Operations owns the policy. Engineering integrates once.

Rules-based routing

Business hours, country filters, amount limits, transaction caps and weighted load balancing. Rules are reusable and applied per flow.

  • Business hours
  • Country filter
  • Min and max amount
  • Transactions per period
  • Amount per period
  • Weighted load balancing
  • Gateway warming
Four strategies

Each flow selects a gateway by priority, round robin, weight or failover. Health checks skip providers that are down, and retries are capped per flow.

One API surface

Initiate a payment against a flow name. TuxoPay picks the gateway and returns the checkout.

POST /api/payment-flows/initiate
{
  "flow_name": "card-checkout-eu",
  "amount": 49.99,
  "currency": "USD",
  "customer": { "email": "[email protected]" }
}
Audit every decision

Provider choice, rule results, retries and forwarded webhooks are stored per payment and visible to operators and engineers.

Webhook event reference
Portable by design

Move traffic between gateways with a configuration change instead of an SDK rewrite. When a contract changes, the checkout does not.

Priced by gateway footprint.

Every plan includes unlimited flows and full API access. A one-time setup fee of $500 covers onboarding.

Starter

One gateway, one clean integration surface.

$49 per month

  • 1 gateway
  • Unlimited flows
  • 0.75% per transaction
  • Full API access
Choose Starter

Growth

Most chosen

Routing logic and failover across several providers.

$149 per month

  • 3 gateways
  • Unlimited flows
  • 0.75% per transaction
  • Full API access
Choose Growth

Enterprise

Broad orchestration coverage for larger payment operations.

$399 per month

  • 10 gateways
  • Unlimited flows
  • 0.50% per transaction
  • Full API access
Choose Enterprise

Connect your gateways this afternoon. Publish the first flow before you leave.

Start building Read the docs