Integrate payments once. Switch providers any time.

One integration for the payment providers you choose. Build your checkout against it once, and adding a backup provider or replacing one becomes a config change, not a new integration project.

Get early access See how it works

You sign with each provider yourself Card entry stays provider-hosted Free during early access

Your checkout

Web, mobile, or the platform you already run.

Connect one API

no double charges automatic retries one webhook format refunds that work

we build and maintain this part

Stripe

Adyen

Mollie

+1,300 more in the directory

The whole journey, one surface

Pick your providers

Get matched or browse the directory — choose the providers that fit your business.

Integrate once

One API for every provider you use. We handle the hard parts — no double charges, no lost payments when a provider blips, refunds that just work — so your team never builds that plumbing again.

Switch anytime

Add a backup provider or replace a lost one as a config change, not a quarter of engineering.

Card entry stays on provider-hosted surfaces and your agreements stay directly with each provider — Connect is integration plumbing, not a processor, and it never decides where your payments go.

Switching

A config change, not a rebuild

Lost a provider, found better fees, or need a regional backup? Repoint your routing in the dashboard or in your repo and ship it the same afternoon. Your checkout code doesn't change.

A fallback provider takes over if your primary goes down
Webhooks, refunds, and reconciliation keep working unchanged
Your contracts stay direct with each provider

routing.yaml deploys in seconds

1checkout:

2- provider: "stripe"

3+ provider: "adyen"

4 fallback: ["stripe"]

5 capture: auto

No rebuild. No re-certification. Same payment call.

Providers change their APIs without warning — we test every integration against the provider's real system, continuously, so breaking changes get caught by us before they reach your checkout.

runs in your CI

$ connect validate

✓ routing.yaml valid · 0 warnings

$ connect test

✓ 14 scenarios passed

$ connect simulate --traffic last-30d Coming with GA

→ 3.2% of transactions would route differently

connect-bot commented on #482 · routing.yaml

3.2% of last month's transactions would route differently under this change.

Dashboard or repo

Set routing in a dashboard, or check it into your repo.

You pick how you work. Click your rules together in the visual editor, or keep them as a file in your repo, where they run in your CI and get reviewed in your pull requests.

They are the same rules either way, so you can start in the dashboard and move them into your repo later. Bad change in the repo? git revert is your rollback.

Test live from the app. Send a test payment through any of your providers from the app and watch it go through, before real customers do.
Everything is audit logged. Every rule change and every test, with who made it and when, whether it came from the dashboard or your repo.

Every provider in the directory is a candidate

Connect builds on the same index you already browse — 1,300+ providers compared and tracked. Early-access signups decide which integrations get built first.