Authorize.net
Keep Authorize.net in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
26 ways to read, 7 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Authorize.net, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create customer profile
customer_profiles.createApproval by rule - Create hosted profile page token
hosted_profile_pages.createApproval by rule - Get Account Updater summary
account_updater_summary.listRead
Example flow
- Authorize.net · Get Account Updater summary
account_updater_summary.listDone - Authorize.net · Create customer profile
customer_profiles.createMaker-checker - Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Authorize.net.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Authorize.net
- Authorize.net's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Authorize.net test account before you go live.
For developers
Technical detail
Authorize.net settled batches, batch transactions, refunds and chargebacks, subscriptions, Account Updater and webhooks (read); customer, payment and shipping profiles (read, create, update).
Authorize.net API docs- Source actions
- 26
- Destination actions
- 7
- Data types
- 20
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
account updater details1
- List Account Updater changesSource
Stored cards that Account Updater changed or removed in one month, with masked last four digits only.
account updater summary1
- Get Account Updater summarySource
Card update counts by reason code for one month of Account Updater runs.
authentication1
- Test credentialsSource
Confirm the API login ID and transaction key are valid (authenticateTestRequest).
batches1
- Get batch statisticsSource
One settled batch with charge, refund, void, decline and chargeback totals.
customer profiles4
- Create customer profileDestinationNot retried automaticallyApproval before production
Create a customer profile (no payment details). Add a payment profile separately with an Accept.js nonce.
- Get customer profileSource
One customer profile by profile ID, merchant customer ID or email, with its payment profile, shipping address and subscription IDs.
- List customer profile IDsSource
Every customer profile ID on the account (IDs only; use Get for details).
- Update customer profileDestinationProvider duplicate protectionApproval before production
Update merchant customer ID, description and email on a customer profile.
customer transactions1
- List customer profile transactionsSource
Transactions charged to one customer profile, optionally one payment profile.
disputes1
- List batch chargebacksSource
Transactions in one settled batch that Authorize.net marks as chargeback or chargeback reversal.
hosted profile pages1
- Create hosted profile page tokenDestinationNot retried automaticallyApproval before production
Get a token for Authorize.net's hosted page where a customer manages their own stored payment methods. Card data is entered on Authorize.net, never in Nexra, and nothing is charged.
merchant1
- Get merchant detailsSource
Gateway ID, merchant name, test mode, currencies, payment methods and processors.
payment profiles5
- Create payment profileDestinationNot retried automaticallyApproval before production
Store a payment method on a customer profile from an Accept.js or Accept Hosted nonce. Validation mode is none: no authorization is run.
- Get payment profileSource
One payment profile with masked card or account and billing address.
- List a customer's payment profilesSource
Payment profiles stored on one customer profile, with masked card or account.
- Search payment profiles with cards expiring in a monthSource
Payment profiles whose cards expire in the given month, across all customers.
- Update payment profileDestinationProvider duplicate protectionApproval before production
Replace the billing address, customer type or default flag, keeping the stored card (masked) or replacing it with a new Accept.js nonce. No authorization is run.
refunds1
- List batch refundsSource
Refunds settled in one batch (transactions with a refund status). Nexra never issues refunds.
settled batches1
- List settled batchesSourceIncremental
Settled batches with ID, settlement time and state; optionally with per-card statistics. Defaults to the last 24 hours.
shipping addresses3
- Create shipping addressDestinationNot retried automaticallyApproval before production
Add a shipping address to a customer profile.
- Get shipping addressSource
One shipping address stored on a customer profile.
- Update shipping addressDestinationProvider duplicate protectionApproval before production
Replace a shipping address on a customer profile.
subscription status1
- Get ARB subscription statusSource
Current status of one subscription (active, expired, suspended, canceled, terminated).
subscriptions2
- Get ARB subscriptionSource
One subscription with schedule, amount, status, customer profile and optionally recent transactions.
- List ARB subscriptionsSource
Recurring billing subscriptions by search type: active, inactive or expiring.
transactions2
- Get transaction detailsSource
Full details of one transaction: type, status, amounts, order, line items, batch and masked payment.
- List batch transactionsSource
Transactions settled in one batch, with masked account and profile references.
unsettled transactions1
- List unsettled transactionsSource
Transactions not yet settled, or only those pending approval (held for fraud review).
webhook event types1
- List webhook event typesSource
Event types a webhook can subscribe to.
webhook notifications2
- Get webhook notificationSource
One notification with its retry log and the subject entity ID.
- List webhook notificationsSource
Notification delivery history, optionally by date range and delivery status.
webhooks2
- Get webhookSource
One webhook endpoint by ID.
- List webhooksSource
Webhook endpoints with their event types and status (Webhooks REST API).
Access and limits
- Authentication
- API login ID and transaction key
- Plans and access
- An Authorize.net merchant account. Transaction Details API must be enabled for reporting; Customer Information Manager (CIM) and Automated Recurring Billing (ARB) for profiles and subscriptions. Reporting covers settled batches from 1 January two years ago. Customer profile and subscription operations need CIM or ARB on the account.
- Test environment
- Create a free sandbox account at developer.authorize.net and use apitest.authorize.net.
- Rate limits
- Authorize.net does not publish fixed limits. HTTP 429 and Retry-After are honoured with bounded retries; profile writes are not repeated automatically.
- Pagination
- Transaction, subscription and expiring-card lists use paging.limit (up to 1000) and paging.offset (page number from 1). Other reads return one page.
- Provider events
- Authorize.net webhooks notify of transaction, customer profile, payment profile and subscription events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Intentional exclusions: charges, authorizations, captures, refunds, voids, held-transaction approval, customer-profile transactions, creating, updating or cancelling ARB subscriptions, payment profile validation (it can run a live authorization), hosted payment page tokens (they carry a sale), live-mode validation on hosted profile pages, emailing receipts, decrypting wallet payment data, webhook creation, updates and pings, and every delete.
- The Webhooks REST API (/rest/v1) uses HTTP Basic with the same API login ID and transaction key; Nexra sends them in the Authorization header, never in the URL.
- Account Updater results show only the last four card digits; BINs, expiry dates and holder names are not mapped.
- Payment profiles accept only Accept.js or Accept Hosted nonces; raw card and bank numbers never pass through Nexra.
- Customer profile, payment profile and shipping address updates replace omitted fields with blanks, as Authorize.net documents.
- Transaction lists have no updated-since filter: sync by settled batch, or poll unsettled transactions.
- Fees: Authorize.net's API reports no processing, gateway or interchange fees on batches or transactions; fees are billed outside the API.
- Disputes: Authorize.net has no dispute or chargeback case API. Chargeback counts and amounts appear in settled batch statistics, and chargeback statuses on batch transactions where Authorize.net records them; reasons, evidence and deadlines are with your processor.
- Refunds, chargebacks and payout lines are read per settled batch (batch ID required); there is no date-filtered transaction or refund list. Use settled_batches.list (since last run) to find the batches.
- Card expiry, routing numbers, the Accept.js public client key and driver's licence data are not mapped.
- Authorize.net returns business errors with HTTP 200; Nexra classifies them from the response message code.
Developer reference
- Create the Authorize.net credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Authorize.net, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/authorize-net and the Connections API.