Class | ActiveMerchant::Billing::AuthorizeNetGateway |
In: |
lib/active_merchant/billing/gateways/authorize_net.rb
|
Parent: | Gateway |
For more information on the Authorize.Net Gateway please visit their Integration Center
The login and password are not the username and password you use to login to the Authorize.Net Merchant Interface. Instead, you will use the API Login ID as the login and Transaction Key as the password.
Automated Recurring Billing (ARB) is an optional service for submitting and managing recurring, or subscription-based, transactions.
To use recurring, update_recurring, and cancel_recurring ARB must be enabled for your account.
Information about ARB is available on the Authorize.Net website. Information about the ARB API is available at the Authorize.Net Integration Center
API_VERSION | = | '3.1' |
FRAUD_REVIEW | = | 1, 2, 3, 4 |
RESPONSE_REASON_TEXT | = | 0, 2, 3 |
CARD_CODE_RESPONSE_CODE | = | 5, 6, 38 |
CARD_CODE_ERRORS | = | %w( N S ) |
AVS_ERRORS | = | %w( A E N R W Z ) |
AUTHORIZE_NET_ARB_NAMESPACE | = | 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' |
RECURRING_ACTIONS | = | { :create => 'ARBCreateSubscription', :update => 'ARBUpdateSubscription', :cancel => 'ARBCancelSubscription' |
Creates a new AuthorizeNetGateway
The gateway requires that a valid login and password be passed in the options hash.
Performs an authorization, which reserves the funds on the customer‘s credit card, but does not charge the card.
Captures the funds from an authorized transaction.
Credit an account.
This transaction is also referred to as a Refund and indicates to the gateway that money should flow from the merchant to the customer.
Perform a purchase, which is essentially an authorization and capture in a single operation.
Create a recurring payment.
This transaction creates a new Automated Recurring Billing (ARB) subscription. Your account must have ARB enabled.
Update a recurring payment‘s details.
This transaction updates an existing Automated Recurring Billing (ARB) subscription. Your account must have ARB enabled and the subscription must have already been created previously by calling +recurring()+. The ability to change certain details about a recurring payment is dependent on transaction history and cannot be determined until after calling +update_recurring()+. See the ARB XML Guide for such conditions.
Void a previous transaction