Authorize.net
Authorize.net is a leading payment gateway providing secure online payment processing for merchants. It offers a POST-based XML/JSON API, Accept.js hosted payment forms, the Accept Hosted solution, recurring billing (ARB), customer profile management (CIM), advanced fraud detection, and webhooks. Official SDKs are available for PHP, .NET, Java, Ruby, Python, and Node.js.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Authorize.net the way a machine reads it — 33 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Authorize.net scores 63.0/100 (strong), with a separate agent-readiness read of 67/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Authorize.net
Each block below is one kind of artifact we hold for Authorize.net. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Authorize.net Payment API
The Authorize.net Payment API enables merchants to process credit card, debit card, eCheck, Apple Pay, Google Pay, and PayPal transactions via a POST-based XML/JSON API with API...
Authorize.net Recurring Billing API
The Authorize.net Automated Recurring Billing (ARB) API enables merchants to create, update, and cancel subscription-based payment schedules for recurring charges.
Authorize.net Customer Profiles API
The Authorize.net Customer Information Manager (CIM) API enables secure storage and management of customer payment profiles including credit cards and bank accounts for reuse in...
Authorize.net Webhooks
Authorize.net Webhooks deliver real-time event notifications for transaction, subscription, and fraud management events to merchant-configured HTTP endpoints.
Authorize.net Transactions API
Charge, authorize, capture, void and refund transactions.
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Authorize.Net API
OPEN COLLECTIONMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
MCP Server
MCP SERVERPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Authorize Net Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Authorize Net Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Payment Processing
Accept credit cards, debit cards, eChecks, Apple Pay, Google Pay, and PayPal via a single unified API.
Accept.js
Client-side JavaScript library that tokenizes payment data in the browser to keep merchant servers out of PCI scope.
Accept Hosted
Fully hosted payment form that redirects customers to Authorize.net for payment collection with iframe support.
Recurring Billing (ARB)
Automated recurring billing for subscriptions and installment plans with flexible scheduling options.
Customer Profiles (CIM)
Securely vault customer payment methods for future charges without storing sensitive card data.
Fraud Detection Suite
Advanced fraud detection tools including velocity controls, IP blocking, card security code verification, and address verification.
Webhooks
Real-time event notifications for transaction completions, declines, fraud holds, and subscription events.
MCP Server
Official Authorize.net MCP server for AI-assisted payment processing integration at github.com/AuthorizeNet/authorize-net-mcp.
Scroll within the panel for all 8 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
E-Commerce Payment Processing
Accept payments on web storefronts using Accept.js or Accept Hosted for PCI-compliant card processing.
Subscription Billing
Manage recurring charges for SaaS, membership, and subscription-based business models using ARB.
Mobile Payments
Accept Apple Pay and Google Pay in mobile apps using the in-person and mobile payment SDKs.
Point-of-Sale Integration
Integrate card-present transactions via the iOS, Android, or Windows in-person payment SDKs.
B2B and eCheck Payments
Process ACH/eCheck payments for B2B invoicing and recurring bank account debit scenarios.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
WooCommerce
Official Authorize.net WooCommerce payment plugin for WordPress-based e-commerce stores.
Medusa
Official Authorize.net Medusa payment plugin for headless commerce implementations.
Visa and Mastercard Networks
Direct connection to major card networks for authorization and settlement of card-based transactions.
NACHA ACH Network
eCheck processing through the NACHA ACH network for bank-to-bank payment transfers.
Solutions 2
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Payment Gateway
Comprehensive payment gateway solution connecting merchants to card networks with fraud protection and reporting.
PCI-Compliant Payments
Reduce PCI scope using Accept.js or Accept Hosted to tokenize payment data without touching card numbers.
Resources
Every other property we hold for Authorize.net — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/authorize-net · machine-readable index on apis.io