Request Field Description
createTransactionRequest
| Element | Description | Format |
|---|---|---|
| merchantAuthentication | Required. Contains merchant authentication information. | |
| name | Required. Merchant’s unique API Login ID. The merchant API Login ID is provided in the Merchant Interface and must be stored securely. The API Login ID and Transaction Key together provide the merchant authentication required for access to the payment gateway. | String, up to 25 characters. |
| transactionKey | Required. Merchant’s unique Transaction Key. The merchant Transaction Key is provided in the Merchant Interface and must be stored securely. The API Login ID and Transaction Key together provide the merchant authentication required for access to the payment gateway. | String, up to 16 characters. |
| refId | Merchant-assigned reference ID for the request. If included in the request, this value is included in the response. This feature might be especially useful for multi-threaded applications. | String, up to 20 characters. |
| transactionRequest | Required. This element is a container for transaction specific information. | |
| transactionType | Type of credit card transaction. | String. Use |
| amount | Required. Amount of the transaction. This is the total amount and must include tax, shipping, tips, and any other charges. | Decimal, up to 15 digits with a decimal point. Do not use currency symbols. |
| currencyCode | Required. Currency of the transaction. Use the ISO 4217 three-letter alphabetic code for the currency.Use the ISO 4217 three-letter alphabetic code for the currency. Currently supported currencies are | String, three characters. |
| payment | This element contains payment information. | |
| trackData | Conditional. Applies to Card Present transactions only. Contains track data read from the customer's card. Track data contains the full card number and expiration date by default. If you use the | |
| track1 | Conditional. Applies to Card Present transactions only. Track data includes the full card number and expiration date by default. If you send the | String, 76 characters. Do not include the start sentinel (percent sign), end sentinel (question mark), or Longitudinal Redundancy Check. |
| track2 | Conditional. Applies to Card Present transactions only. Track data includes the full card number and expiration date by default. If you use the | String, 37 characters. Do not include the start sentinel (semicolon), end sentinel (question mark), or Longitudinal Redundancy Check. |
| creditCard | Conditional. Applies to Card Not Present transactions only. Contains human-readable information from the customer's card. | |
| cardNumber | Conditional. Applies to Card Not Present transactions only. The customer’s credit card number. Only use | Numeric string, 13-16 digits. |
| expirationDate | Conditional. Applies to Card Not Present transactions only. The customer’s credit card expiration date. Only use | String, 7 characters. Use XML gYearMonth (YYYY-MM) formatting. |
| cardCode | Conditional. Applies to Card Not Present transactions only. The customer’s card code. The three- or four-digit number on the back of a credit card (on the front for American Express). This field is required if the merchant would like to use the Card Code Verification (CCV) security feature. Cardholder information must be stored securely and in accordance with the Payment Card Industry (PCI) Data Security Standard. For more information about PCI, please refer to the Standards, Compliance and Security developer training video at https://developer.authorize.net/training. | Numeric string, 3-4 digits. |
| profile | The following field enables you to create a customer profile from the data sent to make the transaction. | |
| createProfile | Indicates whether to create a customer profile. If set to true, a customer profile and payment profile will be generated from the customer and payment data. | Boolean. Either |
| solution | Contains information about the software that generated the transaction. | |
| id | The unique Solution ID which you generate and associate with your solution through the Partner Interface. See the Solution ID Implementation Guide for details. | String, up to 50 characters. |
| name | The name is generated by the solution provider and provided to Authorize.net. See the Solution ID Implementation Guide for details. | String, up to 255 characters. |
| terminalNumber | The merchant's in-store terminal number. Can identify the cashiers or kiosks used. Do not use your processor's terminal ID for this field. | String. |
| order | Contains information about the order. | |
| invoiceNumber | Merchant-defined invoice number associated with the order. Worldpay RAFT 610 merchants can view the invoice number in the Worldpay Reporting Portal. | String, up to 20 characters. |
| description | Description of the item purchased. | String, up to 255 characters. |
| lineItems | Contains one or more lineItem elements, up to a maximum of 30 line items. | |
| lineItem | Contains information about one item. | |
| itemId | Item identification. | String, up to 31 characters. |
| name | The human-readable name for the item. | String, up to 31 characters. |
| description | A description of the item. | String, up to 255 characters. |
| quantity | The quantity of items sold. | Decimal, up to four decimal places. |
| unitPrice | The cost per unit, excluding tax, freight, and duty. | Decimal, up to four decimal places. |
| taxable | Indicates whether the item is taxable. | Boolean. Either |
| tax | Contains information about applicable taxes. | |
| amount | Amount of tax. The total transaction amount must include this value. | Decimal, up to four decimal places. |
| name | Name of tax. | String, up to 31 characters. |
| description | Description of tax. | String, up to 255 characters. |
| duty | Contains information about any duty applied. | |
| amount | Amount of duty. The total transaction amount must include this value. | Decimal, up to four decimal places. |
| name | Name of duty. | String, up to 31 characters. |
| description | Description of duty. | String, up to 255 characters. |
| shipping | Items in this element describe shipping charges applied. | |
| amount | Amount of the shipping charges. The total transaction amount must include this value. | Decimal, up to four decimal places. |
| name | Name of the shipping charges. | String, up to 31 characters. |
| description | Description of the shipping charges. | String, up to 255 characters. |
| taxExempt | Indicates whether or not order is exempt from tax. | Boolean. Either |
| poNumber | The merchant-assigned purchase order number. If you use purchase order numbers, your solution should generate the purchase order number and send it with your transaction requests. Authorize.net does not generate purchase order numbers. | String, up to 25 characters. Use alphanumeric characters only, without spaces, dashes, or other symbols. |
| customer | The following fields contain customer information. | |
| type | Type of customer. | String. Either |
| id | The unique customer ID used to represent the customer associated with the transaction. If you use customer IDs, your solution should generate the customer ID and send it with your transaction requests. Authorize.net does not generate customer IDs. | String, up to 20 characters. Use alphanumeric characters only, without spaces, dashes, or other symbols. |
| Conditional. The customer’s valid email address. Required only when using a European payment processor. If you enable Email Receipts in the Merchant Interface, and if the email address format is valid, the customer will receive an Authorize.net generated email receipt. | String, up to 255 characters. | |
| billTo | This element contains billing address information. If EVO is your payment processor and you submit any of the following
| |
| firstName | Conditional. First name associated with customer’s billing address. Required only when using a European payment processor. | String, up to 50 characters. |
| lastName | Conditional. Last name associated with customer’s billing address. Required only when using a European payment processor. | String, up to 50 characters. |
| company | Company associated with customer’s billing address. | String, up to 50 characters. |
| address | Conditional. Customer’s billing address. Required if merchant would like to use the Address Verification Service security feature. Required when using GPN Canada or Worldpay Streamline Processing Platform. | String, up to 60 characters. |
| city | Conditional. City of customer’s billing address. Required only when using a European payment processor. | String, up to 40 characters. |
| state | Conditional. State of customer’s billing address. Required only when using a European payment processor. | String, up to 40 characters. For US states, use the USPS two-character abbreviation for the state. |
| zip | Conditional. The postal code of customer’s billing address. Required if merchant would like to use the Address Verification Service security feature. Required when using GPN Canada or Worldpay Streamline Processing Platform. | String, up to 20 characters. |
| country | Country of customer’s billing address. | String, up to 60 characters. Use the ISO 3166 alpha-2 code for the country. |
| phoneNumber | Phone number associated with customer’s billing address. | String, up to 25 characters. |
| faxNumber | Fax number associated with customer’s billing address. | String, up to 25 characters. |
| shipTo | This element contains shipping information. If EVO is your payment processor and you submit any of the following
| |
| firstName | First name associated with customer’s shipping address. | String, up to 50 characters. |
| lastName | Last name associated with customer’s shipping address. | String, up to 50 characters. |
| company | Company associated with customer’s shipping address. | String, up to 50 characters. |
| address | Customer’s shipping address. | String, up to 60 characters. |
| city | City of customer’s shipping address. | String, up to 40 characters. |
| state | State of customer’s shipping address. | String, up to 40 characters. For US states, use the USPS two-character abbreviation for the state. |
| zip | The postal code of customer’s shipping address. | String, up to 20 characters. |
| country | Country of customer’s shipping address. | String, up to 60 characters. |
| customerIP | Conditional. The IPv4 address of the customer initiating the transaction. Defaults to 255.255.255.255 if not included in your request. Required only when the merchant is using customer IP based AFDS filters. | String, up to 15 characters. Use dot-decimal formatting. |
| cardholderAuthentication | Important: This field is deprecated and should not be used. Merchants using a third party cardholder authentication solution can submit the following authentication values with Visa and Mastercard transactions. Invalid combinations of card type, | |
| authenticationIndicator | Conditional. Important: This field is deprecated and should not be used. The Electronic Commerce Indicator (ECI) value for a Visa transaction, or the Universal Cardholder Authentication Field indicator (UCAF) for a Mastercard transaction. The cardholder authentication process generates the ECI or UCAF value prior to submitting the transaction. Required only for Invalid values of This field is currently supported through Chase Paymentech, FDMS Nashville, Global Payments and TSYS. | String. |
| cardholderAuthenticationValue | Conditional. Important: This field is deprecated and should not be used. The Cardholder Authentication Verification Value (CAVV) for a Visa transaction, or Accountholder Authentication Value (AVV)/ Universal Cardholder Authentication Field indicator (UCAF) for a Mastercard transaction. The cardholder authentication process generates the CAVV, AAV, or UCAF value prior to submitting the transaction. Required only for Invalid values of This field is currently supported through Chase Paymentech, FDMS Nashville, Global Payments and TSYS. | String. |
| retail | The retail element contains two elements: marketType and deviceType. If you submit the retail element, the marketType and deviceType elements are required. | |
| marketType | The market type for the transaction. This element is required if you submit the | Numeric string. Either |
| deviceType | The type of device submitting the retail transaction. This element is required if you submit the | Numeric string. One of the following:
|
| employeeId | Merchant-assigned employee ID. This field is required for the EVO processor, and is supported on the TSYS processor. | Numeric string, 4 digits. Defaults to |
| transactionSettings | This element contains one or more setting elements. | |
| setting | Contains settingName and settingValue. | |
| settingName | Name of a specific setting to be modified for this transaction. For a list of valid | String. One of the following: |
| settingValue | Indicates whether the specified setting is enabled or disabled. For a list of permitted | String. Permitted values depend on the value of |
| userFields | These elements may be used to pass through information, such as session IDs and order details. The merchant will receive these elements in the response, exactly as it was submitted in the request. Authorize.net will not store these values. Do not use these fields to pass through sensitive details as doing so may be a violation of the PCI Data Security Standard. Worldpay RAFT 610 merchants can view the first two userField elements in the Worldpay Reporting Portal. | |
| userField | The element for individual user-defined fields. Contains the name and value child elements.Up to 20 | String. |
| name | Name of the user-defined field. User reference field provided for the merchant’s use. The merchant will receive this field in the response, exactly as it was submitted in the request. Authorize.net will not store this value. | String. |
| value | Value of the user-defined field. User reference field provided for the merchant’s use. The merchant will receive this field in the response, exactly as it was submitted in the request. Authorize.net will not store this value. | String. |
| surcharge | Used to record payment card surcharges that are passed along to customers. Contains an amount and a description child element.Currently supported for TSYS merchants. For details on surcharge rules, please see Visa's merchant regulations and fees. | |
| amount | Amount of the surcharge. Currently supported for TSYS merchants. For details on surcharge rules, please see Visa's merchant regulations and fees. | Decimal, up to 15 digits with a decimal point. Do not use currency symbols. |
| description | Describes the reason or details for the surcharge. Currently supported for TSYS merchants. For details on surcharge rules, please see Visa's merchant regulations and fees. | String, up to 255 characters. |
| tip | The amount of the tip authorized by the cardholder. The total transaction amount must include this value. | Decimal, up to 15 digits with a decimal point. Do not use currency symbols. |
| processingOptions | Contains details for additional transaction processing. Required if the merchant stores card-on-file payment information. | |
| isFirstRecurringPayment | Indicates the initial zero-dollar authorization or the first recurring payment in a series of charges. Required if the merchant stores card-on-file payment information. Set | Boolean. |
| isFirstSubsequentAuth | Indicates the initial zero-dollar authorization or the first payment in a series of charges. Required if the merchant stores card-on-file payment information. | Boolean. |
| isSubsequentAuth | Indicates that the transaction is a follow-on transaction for an established customer. Use in these situations:
Required if the merchant stores card-on-file payment information. | Boolean. |
| isStoredCredentials | Indicates that the transaction was initiated by the customer using card-on-file payment information. Required if the merchant stores card-on-file payment information. | Boolean. |
| subsequentAuthInformation | Contains details for subsequent authorizations using stored payment information. Required if the merchant stores card-on-file payment information. | |
| originalNetworkTransId | Required. The network transaction ID returned in response to the original card-on-file transaction. Store the | String, up to 255 characters. |
| reason | Required. Describes the reason for the subsequent card-on-file transaction. Use Use Use Use | String. Either |
| originalAuthAmount | Required. The original authorization amount. Store the amount of the original card-on-file transaction response. Set the | Decimal, up to 15 digits with a decimal point. Required for Discover, Diners Club, JCB, and China Union Pay transactions. Do not use currency symbols. |
| authorizationIndicator | Indicates whether the authorization was a pre-authorization or final authorization. Applicable to Mastercard only. Use | String. Either |
FAQs
Is Authorize.net an API? ›
The Authorize.net API provides robust features for processing payment transactions through the Authorize.net gateway. The API supports XML and JSON variants. For detailed API reference information, see the API Reference. If you are new to the Authorize.net API, start with the Credit Card Payment Tutorial.
How do I get an Authorize.net API? ›- For sandbox API requests, log into the sandbox Merchant Interface at https://sandbox.authorize.net. ...
- Navigate to Account > Settings > API Credentials & Keys.
- Click New Transaction Key.
- Click Submit.
- Request and verify a PIN in order to see the transaction key.
Authorize.Net has been accredited by the BBB since 2009 and has an A+ rating.
Is Authorize.net owned by Visa? ›Authorize.net is a wholly owned subsidiary of Visa (NYSE: V). Authorize.net services are sold through a network of reseller partners including Independent Sales Organizations (ISOs), Merchant Service Providers (MSPs) and financial institutions that offer Authorize.net payment services to their merchant customers.
How do I Authorize a REST API? ›- Basic authentication. ...
- API keys. ...
- HMAC encryption. ...
- OAuth 2.0. ...
- OpenID Connect. ...
- Choosing a REST API authentication approach.
The ASP.NET Web API Framework provides a built-in authorization filter attribute i.e. AuthorizeAttribute and you can use this built-in filter attribute to checks whether the user is authenticated or not. If not, then it simply returns the HTTP status code 401 Unauthorized, without invoking the controller action method.
Is Authorize.Net a CRM? ›CRM with Authorize.Net| CRM Payment gateway integration. Complete CRM tools to centralize your data. Send personalised bulk emails to your audience. Built-in billing software with invoicing features.
Is Authorize.Net the same as stripe? ›Stripe is a full-fledged payment service provider, which means it comes with everything you need to accept and process online payments. Stripe includes a payment gateway, payment processing service and merchant account. In contrast, Authorize.net solely offers a payment gateway.
Is Authorize.Net Expensive? ›Both have a $25 monthly fee, and transaction fees with the combined plan are on par with competitors. Businesses that use Authorize.net can accept all major credit and debit cards, Apple Pay, PayPal and electronic checks. The company offers 24/7 customer support. Transparent, flat-rate pricing.
Is authorize net high-risk? ›Authorize.Net – high-risk payment gateways and merchant account recommendations. A+ rated and BBB accredited, Tasker Payment Gateways LLC helps website owners sell regulated products online using high-risk Authorize.Net accounts catered to their exact products and services.
Is PayPal better than authorize net? ›
Easy to integrate with other applications, both are great choices for small businesses. However, PayPal offers more for in-person and international sales, while Authorize.net provides more stability, offers Level 2 and 3 processing for business-to-business (B2B) transactions, and is less expensive.
How does Authorize.net make money? ›Once a day, Authorize.net takes all your transactions from the previous 24-hours and aggregates them into a “batch” which is then sent off to the processing networks. The Daily Batch Fee is the fee assessed for this process.
Is Authorize.net cheaper than stripe? ›Pricing, fees, and transaction costs
Stripe and Authorize.net offer similar pricing: 2.9 percent + $0.30 per transaction. Authorize.net also has a secondary tier of pricing if you're using only its payment gateway service: $0.10 per transaction, with a daily batch fee of $0.10.
Bankcard USA. BankCard USA (BUSA) offers a complete one-step process for accepting credit card payments for all types of businesses. Along with years of Authorize.Net experience, BUSA has been servicing merchants since 1993 and is powered by First Data and Harris Trust & Savings Bank.
What is difference between OAuth and JWT? ›JWT is mainly used for APIs while OAuth can be used for web, browser, API, and various apps or resources. JWT token vs oauth token: JWT defines a token format while OAuth deals in defining authorization protocols. JWT is simple and easy to learn from the initial stage while OAuth is complex.
What is API authentication vs authorization? ›Authentication verifies the identity of a user or service, and authorization determines their access rights. Although the two terms sound alike, they play separate but equally essential roles in securing applications and data. Understanding the difference is crucial. Combined, they determine the security of a system.
How does authorization work in API? ›The API authentication process validates the identity of the client attempting to make a connection by using an authentication protocol. The protocol sends the credentials from the remote client requesting the connection to the remote access server in either plain text or encrypted form.
What are 3 ways to authenticate a user? ›There are three common factors used for authentication: Something you know (such as a password) Something you have (such as a smart card) Something you are (such as a fingerprint or other biometric method)
What is OAuth in REST API? ›OAuth is an authorization framework that enables an application or service to obtain limited access to a protected HTTP resource. To use REST APIs with OAuth in Oracle Integration, you need to register your Oracle Integration instance as a trusted application in Oracle Identity Cloud Service.
How do I authenticate an HTTP request? ›A client that wants to authenticate itself with the server can then do so by including an Authorization request header with the credentials. Usually a client will present a password prompt to the user and will then issue the request including the correct Authorization header.
Is Authorize.Net a software? ›
Authorize.Net is a cloud-based payment processing software that helps streamline the submission of customer transactions to the payment processing networks.
Is Authorize.Net a virtual terminal? ›Submit manual orders quickly and securely with our Virtual Terminal. Get easy-to-use tools for managing your ongoing billing needs. Accept electronic check payments from your customers. Turn your phone or tablet into a fast and secure mobile point of sale (mPOS).
Does Authorize.Net have Level 3 data? ›There are two levels when it comes to enhanced data: level 2 and level 3. Some processing companies only support level two data. Authorize.Net supports both level 2 and level 3.
Does Authorize.Net have invoicing? ›Invoicing is a free part of Authorize.Net, so there is no development or customisation required. Easily offer custom discounts on any invoice. Plus, your customers will enjoy the flexibility of multiple payment methods, including credit cards and e-checks.
Is Authorize.Net a merchant processor? ›However, it's important to note that Authorize.net is not a merchant account or payment processor. It is a payment gateway that can facilitate virtual terminal, phone, recurring, mobile, e-check, and virtual point-of-sale (POS) payments.
How does Authorize.Net work? ›Authorize.net How Payments Work - YouTube
What percentage does Authorize.Net take? ›The Authorize.net payment gateway does not have a contract or early termination fees. E-check processing is 0.75% of the transaction price.
Does Authorize.Net require billing address? ›The billing address is strongly recommended for the purposes of address verification when processing a credit card. The address is not validated for all payment types and not every field is validated even for credit cards, but it is a best practice to capture the full address.
Does Authorize.Net need SSN? ›Social Security Number: Primary owner must be a US Citizen with a Social Security Number. Complete information on all owners with 25% or greater equity ownership in the company listed below must be disclosed on your application per U.S. Treasury Customer Due Diligence Requirements.
Does Authorize.Net require CVV? ›...
| File | Size |
|---|---|
| cvv.png | 19.11 KB |
Is Authorize.Net Hipaa compliant? ›
All mobile numbers are validated, and payments are verified through Everyware's PCI & HIPAA compliant safe and user-friendly platform.
Does Authorize.Net handle PCI compliance? ›Authorize.Net is not directly involved with establishing, evaluating or validating merchant PCI compliance requirements. For general information about the Payment Card Industry Security Standards Council and their Data Security Standard, please visit PCI Security Standards.
What is the best payment gateway for website? ›- PayPal: Best for doing everything in one place.
- Square: Best if you also have a storefront.
- Braintree: Best for accepting a variety of payment types.
- Chase Payment Solutions: Best for a built-in banking partner.
- Authorize.net: Best if your business has more complex payment needs.
- Affiliate marketing. ...
- Use Skimlinks. ...
- Add banner adverts. ...
- Use text link advertising. ...
- Sell to email subscribers. ...
- Publish sponsored posts. ...
- Review products. ...
- Sell digital products.
Authorize.net and PayPal are payment service providers, or PSPs, that help small businesses take payments in person and online.
What countries does Authorize.net support? ›Answer. Authorize.net can accept transactions from merchants located in the United States, Australia and Canada.
Does Authorize.net allow PayPal? ›Yes, as announced by Authorize.Net, they now accept PayPal payments. You can use PayPal Express Checkout feature which allows you to view your PayPal transactions made in Authorize.net in the Merchant Interface.
Does Authorize.Net allow debit cards? ›You can accept signature debit cards with your Authorize.Net account as long as the cards have a logo of one of the card types you accept (such as Visa or MasterCard).
Does Authorize.Net support Google Pay? ›Digital Acceptance
Use Authorize.Net to accept Google Pay and Apple Pay transactions. Accept PayPal transactions with an Authorize.Net account.
Gateways are payment services — typically provided for an additional fee — that process credit cards online through an e-commerce site or in-person through a credit card terminal.
› website-ecommerce-software ›
Authorize.Net Pricing, Features, Reviews & Alternatives
Authorize.Net Review for 2021: Features, Pricing, Reviews
2022 Authorize.net Payment Gateway Review: Pricing & Features
APIs use authorization to ensure that client requests access data securely. This can involve authenticating the sender of a request and confirming that they have permission to access or manipulate the relevant data. If you're building an API, you can choose from a variety of auth models.
Which API deals with authorization? ›OAuth 2.0 is the best choice for identifying personal user accounts and granting proper permissions. In this method, the user logs into a system. That system will then request authentication, usually in the form of a token.
What is Authorize.Net used for? ›Authorize.net is a type of payment gateway, or gateway for short. A payment gateway is the online-equivalent of a credit card terminal. The payment gateways' job is to encrypt, and then securely authorize a credit card transaction.
Is Authorize.Net a software? ›Authorize.Net is a cloud-based payment processing software that helps streamline the submission of customer transactions to the payment processing networks.
How many types of authorization are there in API? ›There are four types of Authorization – API keys, Basic Auth, HMAC, and OAuth.
What are the three levels of authorization? ›The first phase is identification, where a user asserts his identity. The second phase is authentication, where the user proves his identity. The third phase is authorization, where the server allows or disallows particular actions based on permissions assigned to the authenticated user.
What is OAuth in API? ›OAuth is a delegated authorization framework for REST/APIs. It enables apps to obtain limited access (scopes) to a user's data without giving away a user's password. It decouples authentication from authorization and supports multiple use cases addressing different device capabilities.
Why is authorization required in API? ›Why do APIs even need authentication? For read-only APIs, sometimes users don't need keys. But most commercial APIs do require authorization in the form of API keys or other methods. If you didn't have any security with your API, users could make unlimited amounts of API calls without any kind of registration.
How do I test API authorization? ›To set up your test, go to the request in Postman that you need to authenticate and click on the Authorization tab. On that tab there is a Type dropdown where you can select the type of authorization your API uses. Select Basic Auth from there. This header is how your username and password are given to the server.
Is Authorize.net a CRM? ›
CRM with Authorize.Net| CRM Payment gateway integration. Complete CRM tools to centralize your data. Send personalised bulk emails to your audience. Built-in billing software with invoicing features.
Is Authorize.net a high risk? ›Authorize.Net – high-risk payment gateways and merchant account recommendations. A+ rated and BBB accredited, Tasker Payment Gateways LLC helps website owners sell regulated products online using high-risk Authorize.Net accounts catered to their exact products and services.
Is Authorize.net a virtual terminal? ›Submit manual orders quickly and securely with our Virtual Terminal. Get easy-to-use tools for managing your ongoing billing needs. Accept electronic check payments from your customers. Turn your phone or tablet into a fast and secure mobile point of sale (mPOS).
Is Authorize.net the same as stripe? ›Stripe is a full-fledged payment service provider, which means it comes with everything you need to accept and process online payments. Stripe includes a payment gateway, payment processing service and merchant account. In contrast, Authorize.net solely offers a payment gateway.
Is Authorize.net like PayPal? ›Authorize.Net and PayPal are actually two very different services. Authorize.Net is a payment gateway that is used to connect eCommerce transactions with payment processors. PayPal is a full-stack payment processing service that includes both payment processing and a payment gateway.
Is Authorize.net Expensive? ›Both have a $25 monthly fee, and transaction fees with the combined plan are on par with competitors. Businesses that use Authorize.net can accept all major credit and debit cards, Apple Pay, PayPal and electronic checks. The company offers 24/7 customer support. Transparent, flat-rate pricing.