Authorize.net · Authentication Profile

Authorize Net Authentication

Authentication

Authorize.net secures its APIs with apiKey across 1 declared security scheme, as derived from its OpenAPI definitions.

Accept.jsCredit CardseChecksFraud DetectionPayment GatewayPaymentsRecurring BillingTransactions
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

merchantAuthentication apiKey
· in: header (X-Anet-Merchant-Auth)

Source

Authentication Profile

authorize-net-authentication.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/authorize-net-openapi.yml
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: merchantAuthentication
  type: apiKey
  in: header
  parameter: X-Anet-Merchant-Auth
  description: |-
    Authorize.Net does not use HTTP authentication. Instead, every request
    must include a `merchantAuthentication` object in the JSON/XML body
    containing the merchant's API Login ID (`name`) and `transactionKey`.
    This security scheme entry is a placeholder so OpenAPI tooling can model
    the requirement.
  sources:
  - openapi/authorize-net-openapi.yml