Authorize.net website integration
Accept Hosted, the Accept UI lightbox, or Accept.js on your site, with card data sent straight to Authorize.net.
The Problem
When Your Gateway Works but the Code Around It Doesn't
It shows up in Authorize.net integrations built years ago. The gateway still approves cards, but the checkout, refunds, and reports around it weren't kept current.
01 · Retired code
An old SIM or AIM integration still runs your checkout.
We move it to Accept Hosted or Accept.js on the current API.
02 · Card scope
Card numbers pass through your server and widen PCI scope.
A hosted form or Accept.js sends card data straight to Authorize.net.
03 · Lost refunds
Refunds and voids don't reach your order records.
Signed webhooks update each order when a refund or void happens.
04 · Month-end
Deposits get matched to orders by hand every month.
Settled transactions post to QuickBooks or your CRM through the reporting API.
Your Authorize.net account has run for years, but the checkout code behind it was written for a method Authorize.net has since retired. Card numbers pass through your own server, which widens your PCI scope. A refund in the Merchant Interface doesn't reach the order record, so support refunds twice. Repeat customers type their card again because nothing is saved. At month-end, your bookkeeper matches deposits to orders by hand.
We start by choosing the method by PCI scope: Accept Hosted or the Accept UI lightbox for SAQ A, or Accept.js behind your own form for SAQ A-EP. Signed webhooks then update orders on every payment, refund, and void. Saved cards and subscriptions use customer profiles and recurring billing. Card data stays with Authorize.net, and your books stop waiting on spreadsheets.
Card data off your server
Hosted forms and Accept.js send card details straight to Authorize.net, not through your code.
Orders that match payments
Signed webhooks update each order when a charge, refund, or void happens in the gateway.
Saved cards and subscriptions
Customer profiles and recurring billing let repeat buyers pay without typing their card again.
Our Authorize.net Integration Services Process
From Payment Review to Live Checkout in Five Steps
You approve the method and its PCI scope first, watch every test outcome in the sandbox, and sign off before production keys go in.
We look at your Authorize.net account, your current checkout code, and where payments need to go afterward. Retired methods such as SIM, AIM, or DPM get flagged for replacement. You get a method plan, a PCI scope note, and a fixed price.
What's Included
What Our Authorize.net Integration Covers
Most merchants need a secure checkout and orders that update on their own before anything else. These six parts cover the payment work we build most often.
Compare Options
DeveloperLook vs Plugin Only vs Freelancer
An official plugin is the cheapest route on WooCommerce, and a freelancer can suit one small fix. Here is where each one fits and where it stops.
| Feature | DeveloperLookBest fit | Plugin only | Freelancer |
|---|---|---|---|
| Setup speed | 1 to 6 weeks | An afternoon | Depends on availability |
| Cost | Fixed project price | Low yearly license | Hourly, often open-ended |
| Checkout method | Chosen by PCI scope | The plugin's built-in method | Whatever they know best |
| Custom sites and apps | WordPress only | ||
| Webhooks | Signature checked on every event | Varies by plugin | Often skipped |
| Saved cards | Customer profiles and recurring billing | Some plugins | Varies |
| Reconciliation | QuickBooks, Salesforce, or ERP | Not included | Rarely included |
| Ownership | Code and keys in your accounts | Plugin license terms | Depends on the handover |
DeveloperLook
Plugin only
- Setup speed
- DeveloperLook: 1 to 6 weeksPlugin only: An afternoon
- Cost
- DeveloperLook: Fixed project pricePlugin only: Low yearly license
- Checkout method
- DeveloperLook: Chosen by PCI scopePlugin only: The plugin's built-in method
- Custom sites and apps
- DeveloperLook: Plugin only: WordPress only
- Webhooks
- DeveloperLook: Signature checked on every eventPlugin only: Varies by plugin
- Saved cards
- DeveloperLook: Customer profiles and recurring billingPlugin only: Some plugins
- Reconciliation
- DeveloperLook: QuickBooks, Salesforce, or ERPPlugin only: Not included
- Ownership
- DeveloperLook: Code and keys in your accountsPlugin only: Plugin license terms
Projects We've Built
Stores and Online Checkouts We Have Built
Hardware, fine art, furniture, and fashion stores that take payments online. They are shown as builds, not as Authorize.net case studies.
Borna's General Hardware Ecommerce Website
- Retail
- E-commerce
- Website
Sir Kenneth Riley Artwork Ecommerce Website
- Art
- E-commerce
- Website
Havenly Furniture Ecommerce Website
- Furniture
- E-commerce
- Dashboard
Modeverse Ecommerce Web Design & Development
- Fashion
- Retail
- E-commerce
What Our Clients Say
What Clients Say After Launch
Feedback from teams we have built websites, apps, and integrations for.
We had a pretty specific idea of what we wanted our website to become, but I wasn’t sure how easily we could explain all of it to a development team. There were quite a few moving parts, and we were working toward a deadline, so I expected a few things to get lost along the way. That never really happened. They understood what we were trying to achieve, kept us updated throughout the process, and got everything ready within the agreed timeline. The final site feels much easier to navigate, works beautifully on mobile, and is noticeably smoother for our customers. It was a huge relief seeing the original idea actually turn into the website we had in mind.
The mobile experience is probably my favourite part of the new site. We had spent a lot of time making sure the desktop version looked right, and the team kept pushing us to think about how everything would actually feel on a phone too. They were right. The navigation is clean, the interactions feel natural, and everything we’ve tested so far works exactly as it should. They also went through the links, forms, integrations, and other details more than once before launch, which I really appreciated. And even after going live, we could still reach out when something came up. The whole process felt friendly, organised, and surprisingly straightforward.
What I appreciate most is that the website is actually easy for us to manage now. We can update content ourselves instead of sending a developer a message every time we need to change something small. They also paid attention to the technical SEO side, which mattered to us because we didn’t want a new website to create problems for the traffic we already had. I’ve probably asked more questions than I should have since launch, but every question has been handled patiently and without any fuss. The team is easy to work with, they explain things clearly, and when we need something changed, they focus on getting it done rather than making the process complicated.
1,250+
Projects shipped
10+
Years of experience
Top 3%
Upwork Top Rated Plus
5 stars
Average review score
Want results like these?
Tell us what you are building. You get a reply within 24 hours on business days, then a written estimate.
Work Culture
Why Merchants Trust Us With Authorize.net
Payment code touches your customers' cards and your revenue. These habits keep it secure, current, and inside your own Authorize.net account.
Plugins before custom code
If the official WooCommerce extension or a hosted form covers your checkout, we'll tell you before we quote. Custom Accept.js work is for sites that need it.
PCI scope chosen on purpose
Authorize.net rates Accept Hosted and the Accept UI lightbox at SAQ A, and your own Accept.js form at SAQ A-EP. We explain the trade-off before you choose.
Sandbox before real cards
Every build runs through Authorize.net's sandbox first, where no real card processing happens. Production keys go in only after every outcome passes.
Retired methods replaced
SIM, AIM, DPM, and the old MD5 hash are deprecated, and Relay Response went with SIM. We move old code to the current API and signed webhooks.
Keys kept server-side
Your API Login ID, Transaction Key, and Signature Key stay on your server or secrets store. Only the public client key reaches the browser.
Your account, your code
The gateway account, keys, and webhooks stay in your name, and the code lives in your repository. Another developer can take over without starting again.
Overview
How do Authorize.net integrations work for websites and apps?
DeveloperLook builds Authorize.net integrations for merchants and software teams that already process cards through Authorize.net. We set up hosted or Accept.js checkouts, signed webhooks, saved cards, subscriptions, Apple Pay, and QuickBooks or Salesforce reporting. Projects start at $450, take 1 to 6 weeks, and card data stays with Authorize.net.
DEVELOPERLOOK
Project facts · Authorize.net Integration Services
- Service
- Authorize.net integration services (checkouts, saved cards, webhooks, reporting)
- Typical timeline
- 1 to 2 weeks for plugins, 3 to 6 weeks for custom builds
- Platforms
- Websites, WordPress, WooCommerce, custom apps, QuickBooks, and Salesforce
- Built with
- Accept.js, Accept Hosted, the Authorize.net API, and webhooks
- Experience
- 10+ years of development experience and 1,250+ shipped projects
- Post-launch support
- 30, 60, or 90 days, depending on plan
- Communication
- Calls in US, UK, and AU business hours
- Starting price
- From $450 USD, fixed scope after a free payment review
Reviewed 8 Oct 2026 by Saimul Islam
Good fit
Merchants with custom-built websites
Your site runs on custom code, and you need an Authorize.net website integration where card details go straight to Authorize.net, not through your server.
Software teams billing their customers
Your app bills customers by card, and you want an Authorize.net API integration with saved profiles and subscriptions handled by the gateway.
Retailers whose shoppers use iPhones
Your mobile shoppers expect Apple Pay, and you want an Authorize.net Apple Pay integration set up with your merchant ID and certificate.
Bookkeepers closing the month
Your bookkeeper downloads gateway reports every month to match deposits, and you want an Authorize.net QuickBooks integration that posts them for you.
Sales teams taking payments in Salesforce
Your team takes payments from Salesforce records, and you need an Authorize.net Salesforce integration through an AppExchange app or custom code.
Not a fit
In-store cards in Counterpoint
You want an NCR Counterpoint Authorize.net integration for in-store cards. Counterpoint processes cards through NCR Secure Pay, so our POS Integration page is a better start.
Card processing in Acumatica
You need an Acumatica Authorize.net integration for card processing inside Acumatica. Acumatica ended Authorize.net support on June 30, 2025, and points customers to Acumatica Payments.
No gateway chosen yet
You're choosing a payment provider from scratch and have no Authorize.net account. Our Stripe integration page covers a gateway that also handles billing and payouts.
Budget under $450
Your budget is under $450 and you run WooCommerce. The official Authorize.net extension costs $79 a year and installs in an afternoon, so start there.
Not sure we're the right fit?
Book a free call or message us. We'll tell you honestly whether we're the right team.
Pricing
Transparent Starting Prices for Authorize.net Integration Services
These are starting points in USD. Your final price depends on your checkout method, saved cards or subscriptions, and reporting, and you get a fixed proposal after a free payment review.
For one website that needs a secure Authorize.net checkout set up with a hosted form or plugin.
$450one-time, USD
- Free payment review and method plan
- Accept Hosted form or the Accept.js WooCommerce extension
- Sandbox tests of approvals, declines, and refunds
- Signature Key set and webhooks verified
- Card data sent straight to Authorize.net
- 30 days of post-launch support
Recommended
For custom sites and apps that need their own checkout, saved cards, or subscriptions.
$1,550one-time, USD
- Everything in Gateway Setup
- Accept.js or Accept UI checkout in your site or app
- Server-side charges with one-time payment tokens
- Customer profiles for saved cards
- Recurring billing or Apple Pay
- 60 days of post-launch support
For businesses that need settled payments posted to their accounting, CRM, or ERP.
$3,800one-time, USD
- Everything in Custom Payment Build
- Settled batches pulled from Transaction Details
- QuickBooks, Salesforce, or ERP posting
- Account Updater reports for expired cards
- Retired SIM, AIM, or DPM code replaced
- 90 days of post-launch support
For Agencies
White-Label Authorize.net Builds for Agencies
You own the client relationship. We supply the Authorize.net engineering: hosted forms, Accept.js checkouts, webhooks, and reporting, built on each client's own gateway account. Sandbox test logs come with every handover, so you can show the work.
How the partnership works
White label: your client only ever sees your brand
- Your client
- You, the agency
- DeveloperLook
Share the checkout brief
Send the client's site, gateway account details, and where payments must go.
- Client needs
- You share the details
- Details received
We scope and quote
You get a method plan, a PCI scope note, and a fixed price.
- Scope and plan
- Proposal to resell
- Your quoteYOUR LOGO
Deliver under your brand
A tested checkout and key guide, handed over under your agency's name.
- Done by our team
- Your brand on it
- Handed to your clientDone
Partner with DeveloperLookDelivered under your brand
You lead the client
You run every client call while we build and test quietly.
PCI scope explained
Each proposal names the checkout method and the questionnaire it keeps.
Sandbox test logs
Every outcome tested in the sandbox, with results you can share.
Fixed-price quotes
Each payment build is priced upfront, so your proposals hold their margin.
The Right Technology for Your Project
Technology Stack
We use Authorize.net's hosted forms, Accept.js, and current API, plus the website and back-office tools your payments need to reach.
- Authorize.net
- Accept.js
Apple Pay
Google Pay- Webhooks
WordPress
WooCommerce- Gravity Forms
React
QuickBooks
Salesforce- Transaction reports
- Account Updater
PHP
Node.js
Python
AWS
FAQ
Frequently Asked Questions
Straight answers on Authorize.net integrations for websites, WordPress, Shopify, QuickBooks, Housecall Pro, Apple Pay, and Salesforce.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
Pick one of 3 methods: Accept Hosted, the Accept UI lightbox, or Accept.js behind your own form. Authorize.net rates the first two at SAQ A and your own Accept.js form at SAQ A-EP. All three send card data straight to Authorize.net, and your server completes the charge with a one-time token that expires after 15 minutes.
On WooCommerce, use the official Authorize.net extension on WooCommerce.com, built by SkyVerge and priced at $79 a year. It uses Accept.js and supports eChecks and saved cards. For forms, Gravity Forms and WPForms both offer Authorize.net add-ons on their Elite plans. All of them need SSL, and we test each one in the sandbox first.
A DeveloperLook Authorize.net setup starts at $450 for a hosted form or the official WooCommerce extension, set up and sandbox-tested. Custom Accept.js checkouts with saved cards, subscriptions, or Apple Pay start at $1,550. Builds that also post settled payments to QuickBooks, Salesforce, or an ERP start at $3,800. Authorize.net's own fees are separate.
Plugin and hosted form setups take 1 to 2 weeks, including sandbox tests. Custom checkouts with saved cards or subscriptions take 3 to 4 weeks, and builds with accounting or CRM reporting take up to 6 weeks. Apple Pay adds a step, because your Apple merchant ID needs a certificate made from Authorize.net's signing request.
No, not directly: Authorize.net says it doesn't support direct QuickBooks integration. A legacy QuickBooks Download Report still exists for older desktop editions. For QuickBooks Online, third-party sync apps such as Synder work, or we build an Authorize.net QuickBooks integration on the Transaction Details API that posts settled batches.
Yes, in select countries. Shopify's help center has an Authorize.net payment provider page and lists it among its third-party providers. Your Authorize.net account must have test mode turned off before Shopify can use it. We check availability for your store's country before any setup work starts.
In Shopify admin, open the payments settings, add Authorize.net as a third-party provider, and enter the API credentials from your Authorize.net account. Turn off test mode in Authorize.net first, or orders will fail. Then run one small live order and refund it, to confirm both reach Shopify and the gateway correctly.
No, not for in-app card payments. Housecall Pro says its credit card option only works with its own payment processor. You can still take Authorize.net payments elsewhere, such as a payment link on your website, but those won't mark Housecall Pro invoices paid without custom work.
Yes, Authorize.net supports Apple Pay in Safari on iPhone, iPad, and Mac, and Google Pay through its Android SDK, at no extra fee. The account owner enrolls under Digital Payment Solutions in the Merchant Interface, enters the Apple merchant ID, and sends Authorize.net's signing request to Apple. Your site then submits the encrypted payment data with each charge.
Yes, through AppExchange payment apps such as Chargent, which lists Authorize.net among its supported gateways, or Blackthorn Payments. Both take card payments from Salesforce records. When neither fits your process, a custom build on the Authorize.net API can log each transaction to the right account or opportunity.
Saimul IslamFounder & CEO, DeveloperLookStill have questions?
Send a message or book a call with the team.
Free 30-min callGoogle Meet
Book a call
Book a free 30-minute call
In 30 minutes on Google Meet we walk you through how we would build it, how long it takes and what it costs. Then you get a written estimate.
Calendar not showing? Book on cal.com or send a brief.