Authorize.net - Card

Connect to Authorize.net to accept credit and debit card payments.

Authorize.net 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

Authorize.net provides self-service sign-up for production and sandbox accounts:

• Authorize.net sign-up
• Authorize.net sandbox registration

Credentials

When setting up Authorize.net in the dashboard, configure the following credentials. All values can be found in the Authorize.net 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. Authorize.net 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 Authorize.net requires at least one signature key to send webhooks.

Connector configuration

After setting up your Authorize.net connector in the dashboard, configure how transactions are routed to it. Choose one of the following options:

• Using Flow - Configure Authorize.net 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 Authorize.net connector ID when creating transactions. This overrides any Flow routing rules.

The connector ID can be found in the dashboard under Connections -> Configured connections.

Capabilities

Supported countries

Supported currencies

Integration

To accept card payments with Authorize.net, 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 Authorize.net connection based on your Flow rules or explicit payment_service_id parameter.

Webhooks

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

Testing

For testing in sandbox environments, you can use standard test card numbers. Authorize.net 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 Authorize.net testing documentation or contact your Authorize.net representative.