> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/authorizedotnet.md).

# Authorizedotnet

Accept card and wallet payments.

Authorize.net is an online payment provider. Its card and selected wallet methods can be used for recurring charges, while PayPal mandates are not declared. Payments can be captured automatically, manually, or through sequential automatic capture, with payment and refund webhook flows available.

### Status and capabilities

**Integration status:** live

**Category:** payment gateway

**Webhook flows:** payments, refunds

| Payment method | Type        | Mandates      | Refunds   | Capture methods                         | 3DS            | Card networks                                     | Countries | Currencies                                       |
| -------------- | ----------- | ------------- | --------- | --------------------------------------- | -------------- | ------------------------------------------------- | --------- | ------------------------------------------------ |
| card           | Credit Card | supported     | supported | automatic, manual, sequential automatic | not supported  | American Express, Discover, JCB, Mastercard, Visa | -         | CAD, USD                                         |
| card           | Debit Card  | supported     | supported | automatic, manual, sequential automatic | not supported  | American Express, Discover, JCB, Mastercard, Visa | -         | CAD, USD                                         |
| wallet         | Apple Pay   | supported     | supported | automatic, manual, sequential automatic | not applicable | -                                                 | -         | 44 ([full list](https://hyperswitch.io/pm-list)) |
| wallet         | Google Pay  | supported     | supported | automatic, manual, sequential automatic | not applicable | -                                                 | -         | 11 ([full list](https://hyperswitch.io/pm-list)) |
| wallet         | PayPal      | not supported | supported | automatic, manual, sequential automatic | not applicable | -                                                 | -         | 24 ([full list](https://hyperswitch.io/pm-list)) |

### Authentication

Supply the API Login ID and Transaction Key in the connector configuration. Hyperswitch maps them to the connector's body-based authentication fields. See [`AuthorizedotnetAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs#L96-L108).

### Before you start

1. Register with Authorize.net at [authorize.net](https://www.authorize.net/).
2. Create or sign in to your account in the [Hyperswitch control center](https://app.hyperswitch.io/).
3. In the Authorize.net dashboard, go to **Account → Security Settings** to find the API Login ID and Transaction Key.
4. Under **Account → Digital Payment Solutions**, enable the payment methods you plan to select in Hyperswitch.
5. Have the credentials listed in [Authentication](#authentication) ready.

To connect Authorize.net to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what Authorize.net supports.

### Webhooks

Authorize.net webhooks are verified with HMAC-SHA512. Hyperswitch reads the signature from `X-ANET-Signature` and verifies the raw request body. See [`get_webhook_source_verification_algorithm()`](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/authorizedotnet.rs#L1024-L1059).

The connector recognizes six webhook event names:

| Event                                            | Effect in Hyperswitch        |
| ------------------------------------------------ | ---------------------------- |
| `net.authorize.payment.authorization.created`    | Payment is marked successful |
| `net.authorize.payment.priorAuthCapture.created` | Payment is marked successful |
| `net.authorize.payment.authcapture.created`      | Payment is marked successful |
| `net.authorize.payment.capture.created`          | Payment is marked successful |
| `net.authorize.payment.void.created`             | Payment is marked successful |
| `net.authorize.payment.refund.created`           | Refund is marked successful  |

The event names and mappings are defined by [`AuthorizedotnetIncomingWebhookEventType`](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/authorizedotnet/transformers.rs#L2340-L2368).

### Source reference

[Authorize.net connector implementation](https://github.com/juspay/hyperswitch/blob/2ef1f9ee5bdf65356c3169f4f5db67fa1d4de7bc/crates/hyperswitch_connectors/src/connectors/authorizedotnet.rs)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/authorizedotnet.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.