PaymentKitconnects with Carry1st

Available

Approve more payments on your Carry1st gateway

Keep your Carry1st account. PaymentKit adds one unified checkout, payment orchestration, and AI dunning on top, so more of your payments get approved.

Talk to our team

Tell us about your business

Leave your details and a real person will follow up with next steps. No pitch deck, just straight answers.

Prefer to talk it through? Book a call.

Carry1st + PaymentKit

What you can do with Carry1st

Carry1st is your gateway: it moves the transaction. PaymentKit is the layer above it.

  • Carry1st processes the payment

    It moves the transaction and runs eligible charges through your merchant accounts.

  • PaymentKit runs the layer above

    Subscription billing, routing, and failed-payment recovery across every Carry1st account.

  • Your accounts stay yours

    Keep your Carry1st account and your banking relationships.

  • One view of everything

    Approvals, recovery, and revenue across your whole setup in one dashboard.

Connection scopeAvailable

Payment path: Checkout, then PaymentKit, then Carry1st account, then Acquiring bank.

Connection type
Payment gateway
Payment methods
Cards and the methods your account supports
Transaction types
Charges, refunds, and subscription renewals
Merchant accounts
Multiple accounts, each connected as its own route
Markets and currencies
Follows your Carry1st account setup
Account requirements
Active Carry1st account with API access, approved for recurring billing

How it works

Connect Carry1st in three steps

From your existing Carry1st account to live payments, with a full test run before any customer is charged.

  1. Step 1: Check your account

    Confirm you have an active Carry1st account with API access, and that it is approved for recurring billing.

  2. Step 2: Connect Carry1st

    Add your Carry1st API credentials in PaymentKit under Processors. Each account connects as its own route, so you can add more than one.

  3. Step 3: Verify your workflow

    Run a test charge, a refund, and a subscription renewal in test mode before sending live customer payments.

AI dunning

Recover failed Carry1st renewals

When a renewal fails on Carry1st, AI dunning reads the decline code, retries at the best moment, and only emails the customer when it has to.

  • Retries timed by decline reason

    Soft declines get well-timed retries, hard declines skip wasted attempts, and a retry can move to another Carry1st account or processor.

  • Dunning emails that adapt

    Branded sequences change tone and timing based on the type of failure.

  • Self-serve card updates

    Customers fix their card in a secure portal, and the payment retries right away.

A branded dunning email asking the customer to update their card so their subscription stays active

Authorization optimization

More approvals from your Carry1st accounts

Keep Carry1st and win back more of the payments it declines today, with smart routing, network tokens, account updater, and one set of fraud rules.

  • Network tokens

    Card credentials the networks keep current, so reissued and expired cards approve the first time.

  • Account updater on the vault

    Expired and reissued cards refresh automatically before Carry1st ever sees the charge.

  • One set of fraud rules

    The same rules across every route, tuned to stop blocking good customers.

Carry1st vs. Carry1st + PaymentKit

Carry1st alone vs. Carry1st with PaymentKit

You keep your Carry1st account and your banking relationships. PaymentKit makes them work harder.

Carry1st alone vs. Carry1st with PaymentKit
Carry1st aloneWith PaymentKit
CheckoutCarry1st aloneOne checkout per Carry1st integrationWith PaymentKitOne checkout in front of every Carry1st merchant account and any other processor
A soft declineCarry1st aloneThe sale is usually lostWith PaymentKitCascades to your next merchant account in the same session
Stored cardsCarry1st aloneTokens tied to one processorWith PaymentKitVaulted independently and portable across processors
Failed renewalsCarry1st aloneRetries on a fixed timerWith PaymentKitAI dunning timed by decline code and billing cycle
Processor outageCarry1st aloneCheckout goes down with itWith PaymentKitTraffic fails over to a healthy route automatically
Expired or reissued cardsCarry1st aloneRenewal declines, customer has to actWith PaymentKitNetwork tokens and account updater refresh them
ReportingCarry1st aloneOne dashboard per processorWith PaymentKitApprovals, recovery, and revenue across every route in one view

Unified checkout

One checkout for every Carry1st account

Customers enter their card once. PaymentKit vaults it and can charge it through any Carry1st merchant account or other processor you connect.

  • Every Carry1st account behind one checkout

    Each Carry1st merchant account connects as its own route, so your checkout never has to change when you add or retire one.

  • Cards that belong to you

    Cards live in PaymentKit's PCI Level 1 vault, so subscribers stay billable across every Carry1st account.

  • Add other processors anytime

    Run Carry1st next to any other supported gateway, all through one API.

Payment orchestration

Route every payment to its best Carry1st account

PaymentKit picks the right Carry1st account for each payment by card, currency, region, and live performance, then cascades soft declines.

  • Rules you control

    Route by card brand, BIN range, currency, country, or ticket size, and set the order accounts are tried.

  • Cascading on soft declines

    A soft decline on one Carry1st account moves the same charge to your next account. The customer never re-enters a card.

  • Failover when a route goes down

    If an account or processor stops responding, traffic moves to a healthy route automatically.

Integration directory

Find an integration

Search every gateway, processor, and payment method PaymentKit connects with, and see what's available today.

FAQ

Frequently asked questions