Connect Early access
Add a local payment provider. Test it in the portal before anyone pays.
Give the assistant in the portal your provider's docs or a link. It builds a checkout link for your site, no code, and you run a test payment right there before any customer pays.
For independent and regional payment providers, with a backup for when one goes down.
- You sign with each provider
- Connect never holds your money
- Card details stay with the provider
Test payment approved
- Your provider's docs Addedapi-docs.pdf docs.provider-a.example
- Integration and checkout link Built
pay.example/c/demo
- Test payment, in the portal Approved
Test mode or live mode, your choice. A live test is a small real payment, refunded right after. Names and links are examples.
See every route. Change it by asking.
The assistant lays your setup out as a flow: which provider takes which payments, and where they go when one is down. Click any box for its settings, switch on an outage, or ask for a change in plain words.
Connect Routes Demo
Drag the boxes, click one for its settings
From your provider's docs to a tested checkout.
Give it the docs.
A PDF, an API reference or a link. The assistant in the portal builds the integration and a checkout link, no code.
Connect assistant Demoapi-docs.pdf docs.provider-a.exampleHere are my provider's docs. Connect it for my customers in Brazil.
Done. Your checkout link is ready to test.
pay.example/c/demo
Checkout linkTest it in the portal.
Run a test payment before any customer pays, in test mode or live mode: your choice. A live test is a small real payment, refunded right after.
Test payment · in the portal
DemoApproved, then refunded
- Payment through your checkout link Approved
- Refund Done
Test mode or live mode: you choose. A live test is a small real payment, refunded right after. Pick a backup.
If your provider times out or goes down, new payments go to the backup.
Test payment
DemoApproved on the backup
- Your checkout
- Brazil provider · primary Down
- Card provider · backup Approved
Takes new payments if the primary goes down. Provider names are roles, not real companies.
Here are my provider's docs. Connect it for my customers in Brazil.
Done. Your checkout link is ready to test.
pay.example/c/demo
Checkout linkTest payment · in the portal
Demo
Approved, then refunded
- Payment through your checkout link Approved
- Refund Done
Test payment
DemoApproved on the backup
- Your checkout
- Brazil provider · primary Down
- Card provider · backup Approved
Technical detail for your developers
- Provider
- Brazil provider (docs.provider-a.example)
- Signing
- HMAC-SHA256 in the X-Signature header
- Create payment
- POST /v2/payments
- Refund
- POST /v2/payments/{id}/refunds
- Status mapping
- PAID → captured · PENDING → pending · DECLINED → failed
- Webhooks
- payment.updated, signature verified
Backup rule: BRL checkout goes to the Brazil provider; on a timeout, a 5xx or an outage, new payments go to the card provider.
Which providers? The ones you name.
658 regional providers are listed in the directory. The ones early-access merchants name get connected first. Yours isn't listed? The assistant works from its docs.
CatalystPay
PayKings
Paystack
Mollie
Swish
Viva Wallet
Razorpay
Vipps
Xendit- Browse 1,300+ providers
Logos show providers listed in the PaymentProviders.io directory. Showing a provider here doesn't mean it is integrated with, partnered with or endorsed by Connect. All trademarks belong to their owners.
Your next provider, without an engineering project.
Free during early access. Before it ends, you'll get the price, and nothing is charged unless you agree to it. Questions about pricing?
Who holds what
- Money
- Goes from the provider to you
- Card details
- The provider's checkout
- Contracts
- You sign with each provider
On every payment
- Full tracing: every request, response and webhook
- One dashboard across all your providers
- Export payments to CSV
- A backup takes new payments on an outage
- Webhooks retried
- Safe retries: a retry doesn't charge twice