Skip to main content
AuthorizeNet is a payment gateway owned by Visa that provides payment processing solutions for merchants. The platform supports card payments with features like delayed capture, partial refunds, network tokenization, and digital wallet integration across multiple currencies and countries.

​
Setup

AuthorizeNet provides self-service sign-up for production and sandbox accounts:

​
Credentials

When setting up AuthorizeNet in the dashboard, configure the following credentials. All values can be found in the AuthorizeNet Admin Portal under Settings -> API Credentials & Keys.
  • Merchant account ID - Use the value listed as API Login ID.
  • Transaction key - Select New Transaction Key and then Submit to generate a new key. AuthorizeNet sends a confirmation PIN to the registered email address.
  • Signature key (optional) - Select New Signature Key to generate a new key. This field is optional, but AuthorizeNet requires at least one signature key to send webhooks.

​
Connector configuration

After setting up your AuthorizeNet connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:
  • Using Flow - Configure AuthorizeNet as the target connector in Flow to automatically route card transactions to this connector
  • Using the API - Explicitly set the payment_service_id parameter to the AuthorizeNet connector ID when creating transactions. This overrides any Flow routing rules.
The connector ID can be found in the dashboard under Connections -> Configured connections.

​
Features

AuthorizeNet supports the following features:
  • Delayed capture - Authorize a payment and capture it at a later time
  • Partial capture - Capture a portion of the authorized amount
  • Partial refunds - Refund a portion of the captured amount
  • Refunds - Refund transactions in full
  • Void - Cancel an authorized transaction before capture
  • Zero auth - Verify a card without charging it
  • Digital wallets - Support for Apple Pay, Google Pay, and other digital wallet integrations
  • Network tokens - Using network-level tokenization for enhanced security and approval rates (enabled by default)
  • Transaction sync - Automatic synchronization of transaction status updates

​
Supported countries

AuthorizeNet supports transactions from buyers in the following countries:
Country codeCountry codeCountry codeCountry codeCountry codeCountry codeCountry codeCountry code
ADAEAFAGAIALAMAO
AQARASATAUAWAXAZ
BABBBDBEBFBGBHBI
BJBLBMBNBOBQBRBS
BTBVBWBYBZCACCCD
CFCGCHCICKCLCMCN
COCRCUCVCWCXCYCZ
DEDJDKDMDODZECEE
EGEHERESETFIFJFK
FMFOFRGAGBGDGEGF
GGGHGIGLGMGNGPGQ
GRGSGTGUGWGYHKHM
HNHRHTHUIDIEILIM
INIOIQIRISITJEJM
JOJPKEKGKHKIKMKN
KPKRKWKYKZLALBLC
LILKLRLSLTLULVLY
MAMCMDMEMFMGMHMK
MLMMMNMOMPMQMRMS
MTMUMVMWMXMYMZNA
NCNENFNGNINLNONP
NRNUNZOMPAPEPFPG
PHPKPLPMPNPRPSPT
PWPYQARERORSRURW
SASBSCSDSESGSHSI
SJSKSLSMSNSOSRSS
STSVSXSYSZTCTDTF
TGTHTJTKTLTMTNTO
TRTTTVTWTZUAUGUM
USUYUZVAVCVEVGVI
VNVUWFWSYEYTZAZM
ZW

​
Supported currencies

AuthorizeNet supports processing payments in the following currencies:
Currency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency codeCurrency code
AUDCADDKKEURGBPNOKNZDSEK
USD

​
Limitations

The following features are not supported by this connector:
  • Payment method tokenization - Storing payment methods outside of transactions using a separate tokenization flow
  • 3-D Secure - Neither hosted nor pass-through 3DS authentication
  • Over capture - Capturing more than the authorized amount
  • Partial authorization - Accepting a partial amount when the full amount cannot be authorized
  • Settlement reporting - Automatic settlement reporting is not supported

​
Integration

To accept card payments with AuthorizeNet, use one of Gr4vy’s client-side integration methods to securely collect card details. Due to PCI compliance requirements, card data should never be sent directly to your servers. You can integrate using:
  • Embed - A pre-built, customizable payment form that handles the complete payment flow
  • Secure Fields - Embed card input fields for building custom payment forms while maintaining PCI compliance
  • Mobile SDKs - Native SDKs for iOS, Android, React Native, and other platforms
These methods handle card data collection and tokenization. Once the card details are collected and tokenized, create a transaction through the Gr4vy API, which automatically routes the payment to your configured AuthorizeNet connection based on your Flow rules or explicit payment_service_id parameter.

​
Webhooks

AuthorizeNet requires webhook setup to receive transaction status updates. To receive webhooks, generate at least one signature key in the AuthorizeNet Admin Portal under Settings -> API Credentials & Keys.

​
Testing

For testing in sandbox environments, you can use standard test card numbers. AuthorizeNet supports industry-standard test cards for simulating different transaction scenarios: Successful transactions:
  • Visa: 4111 1111 1111 1111
  • Mastercard: 5555 5555 5555 4444
  • American Express: 3782 822463 10005
Use any future expiry date and any 3-digit CVV (4 digits for American Express). For more test scenarios and additional card numbers, refer to the AuthorizeNet testing documentation or contact your AuthorizeNet representative.