Authorize.net
Authorize.net payment gateway integration guide covering setup, supported functionality, testing procedures, and configuration requirements for secure payment processing.
Supported Functionality
| Feature | Supported |
|---|---|
| Authorization | ✅ |
| Capture | ✅ |
| Refund | ✅ |
| Void | ✅ |
| Card Tokenization | ✅ |
| Dynamic Merchant Descriptors | ❌ |
| 3D Secure | ✅ Pass your own |
| $0 Transactions | ❌ |
Setup
To connect a Merchant using the Authorize.net Gateway,
- First add Merchant
- Select Authorize.net as the Gateway
- Add Gateway Details as outlined below
| Gateway Details | Description |
|---|---|
| API Login* | provided by Authorize.net |
| API Transaction Key* | provided by Authorize.net |
| Merchant Payment Methods* | The types of payment methods this merchant accepts — credit card only. |
| Merchant Card Types* | Card types to be accepted on this Merchant |
| Merchant Default Currency* | Default currency that will be used, if currency is not specified |
| Merchant Currencies* | All currencies accepted on this merchant |
| Bypass $0 Transaction Authorizations | Check this box to bypass card validation with Authorize.net for $0 transactions. When unchecked, a $1 authorization (voided immediately) will be used to validate the card — the result of this authorization will determine if the transaction is successful. This setting only applies to initial transactions — $0 renewals will always bypass the gateway. Learn more about $0.00 transaction handling. |
*Required
Supported Payment Methods
Credit Card
Card Tokenization
Charges made with card data ask Authorize.net to save the card. Vrio stores the returned customer profile and reuses it for every renewal.
Dynamic Merchant Descriptors
Vrio does not send a descriptor to Authorize.net with the charge, so the customer's statement shows whatever is configured on your Authorize.net account.
3D Secure
Authorize.net accepts 3D Secure authentication data that you generate with a third party provider. Values are sent whenever authentication data exists on the order for the cycle being charged.
| Vrio | Authorize.net |
|---|---|
order_eci | cardholderAuthentication.authenticationIndicator |
order_cavv | cardholderAuthentication.cardholderAuthenticationValue |
Authentication data is only sent when both an ECI and a CAVV are present on the order.
See Third Party 3DS Providers for the full parameter reference.
Testing
Note : Placing test orders using Authorize.net test cards will not automatically set the order as a test in Vrio. Be sure to flag the order as a test using the is_test flag after the order is processed. For more details on placing test orders, click here.
For Authorize.net test cards, check here.
Updated 2 days ago
