PaymentKit

What it is

PaymentKit is a multi-processor billing platform for SaaS and e-commerce: run subscriptions, route payments across the processors you already use, vault network tokens independently of any single MID, and read revenue metrics in one place. We verified https://www.paymentkit.com/ on 2026-09-24 (HTTP 200). Public materials emphasize three pillars — subscription billing (flat, tiered, usage-based, or hybrid; hosted checkout and self-service portals, including a no-code path), payment orchestration (route by geography/card brand/method, automatic failover when a gateway is down, soft declines cascade to the next processor), and independent vaulting (cards, Apple Pay, and Google Pay vaulted as network tokens under your control so you can add or drop a processor without forcing customers to re-enter cards). Marketing also claims average authorization-rate lifts of about 10%+ after switch (one published case: 63% → 76%) and failed-payment recovery lift around 12.4% via adaptive retries plus brand-matched dunning. Site pricing (verified on /pricing/): $99/month + 0.65% per successfully processed transaction — framed as one predictable rate with no setup fees or minimums called out on the pricing page; free trial is advertised with no card required.

Who it is for

Founders and ops leads running recurring SaaS, digital products, or subscription brands who do not want a single processor (or a merchant-of-record that owns tokens and customer payment data) to be a single point of failure — especially teams that have felt a MID shutdown, rolling reserve, or painful processor migration. Verticals called out on the site include ecommerce/subscriptions, AI/SaaS, telehealth, wellness, gaming/digital goods, and higher-risk categories that need processor-agnostic billing. If you only need a simple Stripe Checkout for a low-volume hobby product, PaymentKit is heavier than you need. If you want a full Merchant-of-Record that files tax and remits payouts for you (Creem/Tiun-style), this is a different layer: you keep your processors and customer relationship; PaymentKit orchestrates billing + vault + routing on top.

Why we listed it

Fresh public surface within the preferred window: Product Hunt featured PaymentKit on 2026-08-24 (~31 days before this listing; #1 Product of the Day, ~451 upvotes / ~111 comments on launch-day tracking via hunted.space), live product at paymentkit.com verified 2026-09-24. Our Billing column was still thin (Creem MoR + Tiun auth/billing) while the board stays Dev-tools heavy — PaymentKit fills “multi-processor orchestration + independent token vault” without padding Stripe/Paddle as household brands. Distinct from Creem (seller-of-record commerce surface) and Tiun (auth + payments + customer data in one backend): PaymentKit’s pitch is processor-agnostic billing that survives a MID shutdown.

Caveats

We have not completed a paid trial, measured authorization lifts on our own volume, or audited vault/TRID portability ourselves. Pricing and recovery percentages come from the public marketing site and PH launch materials — treat them as maker-reported until you validate on a sandbox MID. Multi-processor setups add operational complexity (dispute reconciliation across MIDs, routing rules, underwriting per processor); the site’s “no code to launch” path may not cover every custom routing case without the API. Early-post-launch risk: documentation depth for enterprise routing rules and how chargebacks surface when cascading across processors.