Approve more payments on your Authorize.net gateway
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.
Authorize.net + PaymentKit
What you can do with Authorize.net
Authorize.net is your gateway: it connects your business to your merchant account and moves the transaction. PaymentKit is the layer above it.
Authorize.net processes the payment
It sends each charge to your merchant account, connected to PaymentKit with your API Login ID and Transaction Key.
PaymentKit runs the layer above
Subscription billing, routing, and failed-payment recovery across every Authorize.net account.
Your accounts stay yours
Keep your Authorize.net account and your banking relationships.
One view of everything
Approvals, recovery, and revenue across your whole setup in one dashboard.
Payment path: Checkout, then PaymentKit, then Authorize.net account, then Acquiring bank.
- Connection type
- Payment gateway, connected with an API Login ID and Transaction Key
- Payment methods
- Credit and debit cards, and Apple Pay
- Transaction types
- Charges, refunds, and subscription renewals
- Merchant accounts
- Multiple Authorize.net accounts, each connected as its own route
- Markets and currencies
- Follows your Authorize.net merchant account
- Account requirements
- Live Authorize.net account with our recommended fraud filter settings
How it works
Connect Authorize.net in three steps
From your existing Authorize.net account to live payments, with a full test run before any customer is charged.
Step 1: Get your API credentials
In Authorize.net, open Security Settings, copy your API Login ID, and generate a new Transaction Key.
Step 2: Adjust fraud filters
Set the Fraud Detection Suite to our recommended settings, so charges process as normal and filters report instead of blocking.
Step 3: Connect and test
Add both credentials in PaymentKit under Payment processors and run a test charge, refund, and renewal. Turn off test mode before going live.
AI dunning
Recover failed Authorize.net renewals
When a renewal fails on Authorize.net, 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 Authorize.net 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.

Authorize.net vs. Authorize.net + PaymentKit
Authorize.net alone vs. Authorize.net with PaymentKit
You keep your Authorize.net account and your banking relationships. PaymentKit makes them work harder.
| Authorize.net alone | With PaymentKit | |
|---|---|---|
| Checkout | Authorize.net aloneOne checkout per Authorize.net integration | With PaymentKitOne checkout in front of every Authorize.net merchant account and any other processor |
| A soft decline | Authorize.net aloneThe sale is usually lost | With PaymentKitCascades to your next merchant account in the same session |
| Stored cards | Authorize.net aloneTokens tied to one processor | With PaymentKitVaulted independently and portable across processors |
| Failed renewals | Authorize.net aloneRetries on a fixed timer | With PaymentKitAI dunning timed by decline code and billing cycle |
| Processor outage | Authorize.net aloneCheckout goes down with it | With PaymentKitTraffic fails over to a healthy route automatically |
| Expired or reissued cards | Authorize.net aloneRenewal declines, customer has to act | With PaymentKitNetwork tokens and account updater refresh them |
| Reporting | Authorize.net aloneOne dashboard per processor | With PaymentKitApprovals, recovery, and revenue across every route in one view |
Unified checkout
One checkout for every Authorize.net account
Customers enter their card once. PaymentKit vaults it and can charge it through any Authorize.net merchant account or other processor you connect.
Every Authorize.net account behind one checkout
Each Authorize.net 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 Authorize.net account.
Add other processors anytime
Run Authorize.net next to Stripe, Adyen, Airwallex, or any supported gateway, all through one API.
Payment orchestration
Route every payment to its best Authorize.net account
PaymentKit picks the right Authorize.net 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 Authorize.net 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.
Loading integrations…
FAQ
