DashForDevsDocs
DocsNewsAPI v1
dashfordevs.comSign in

© 2026 DashForDevs

DocsNewsdashfordevs.comLegalStatus
DocsStorefront PaymentsAuthorize.net
Introduction
Getting Started
Authentication
Products
Categories
Cart
Checkout
Blog
Reviews
Webhooks
Customers
Orders
Inventory
Shipping
Discounts
Affiliates
Email
Media & Files
Analytics & Tracking
Locations
Tax
Global Data
SEO
Error Handling
Geography
Finance
Automations
Page Types
Surveys
Billing & Subscriptions
Storefront Payments
Stripe IntegrationAuthorize.netPayment FlowSaved CardsPayment WebhooksGoogle Pay
SDK Reference
REST API
Storefront Architecture
Notifications
Security
Team & Permissions
Migrations & Import
Calendar & Appointments
Contact Forms
AI Bots
Dashboard API
Deployment
Changelog
Troubleshooting
Recipes
CLI & Deployment
Image Pipeline
White-label Platforms
Records Engine
Platform Modules
Platform Security
Site Keys & Client Sites
Use Cases
Operations

Authorize.net

Set up Authorize.net for payment processing.

Updated September 29, 2026

On this page
  • Overview
  • Setup
  • How It Works
  • Saved Cards And Subscriptions
  • Next Steps

Overview

Accept payments using Authorize.net. The SDK includes a built-in Authorize.net client-side processor for PCI-compliant tokenization.

Setup

  1. Create an Authorize.net account
  2. Go to Settings → Payments in the dashboard
  3. Select Authorize.net
  4. Enter your API Login ID and Transaction Key
  5. Save

How It Works

typescript
import dash from "@/lib/dash"

// Load the Authorize.net processor
await dash.payment.load()

// Tokenize card — uses Authorize.net Accept.js
const { token, descriptor } = await dash.payment.tokenize({
  cardNumber: "4111111111111111",
  expDate: "12/26",
  cvv: "123",
})

// Complete checkout
const { order } = await dash.checkout.complete({
  cartId: dash.cart.cartId,
  shipping: { ... },
  payment_token: { token, descriptor },
})
Note: The SDK automatically loads the Authorize.net Accept.js library when dash.payment.load() is called.

Saved Cards And Subscriptions

Untick Card Code "Required" in the classic Authorize.net interface (Account, Settings, Payment Form, Form Fields) before using saved cards or product subscriptions. Charges to a saved card carry no card code, so while it is required they are declined with 33: Card Code is required. The newer interface can show the box unticked while the classic setting is still ticked.

Next Steps

  • Payment Flow — Payment lifecycle
  • Payment Processing — Tokenization
PreviousStripe IntegrationNextPayment Flow

On this page

  • Overview
  • Setup
  • How It Works
  • Saved Cards And Subscriptions
  • Next Steps