Authorize.net
Authorize.net is a payment gateway service provider, allowing merchants to accept credit card and electronic check payments through their website and over an Internet Protocol (IP) connection. Cin7 Core supports Authorize.net, Stripe and PayPal as payment processors. To allow your customers to pay for their transactions using their preferred processor, you can define multiple payment documents containing links to these payment processors.
Cin7 Core generates electronic documents (PDF, email content) to enable your customers to seamlessly pay quotes and invoices. Payment documents can contain Pay Links, allowing customers to pay directly using these documents. Users of the Cin7 Core B2B Portal can also use Authorize.net to process these transactions.
Use Authorize.net Cin7 Core integration to:
Deliver a secure payment experience that is quick and easy for customers to complete.
Easily embed responsive payment forms for mobile devices.
Securely transmit and store payment information on Authorize.Net servers to support PCI DSS compliance standards
Payment processing platforms do not require a subscription add-on in Cin7 Core.
Prerequisites
You will need to log in as an Account Owner or Account Administrator in order to authorize the connection.
An active Cin7 Core account created in a currency supported by Authorize.net. Please refer "Countries supported by Authorize.net" section for additional details.
Enable Customer Information Manager (CIM) in Authorize.net – When an invoice is created, it will create a customer profile automatically giving you the opportunity to be able to store that customers information. If you do not have CIM enabled, you will be presented with a link allowing you to enable the service before you create an Invoice.
You will need to generate an API Login ID and Transaction Key in Authorize.net before you can integrate the application with Cin7 Core. Please follow these instructions for detailed information.
Complete Account mapping
Users will need the Integration: Authorize.netpayments permission in order to use this feature.
Important Information
Authorize.net also supports direct integration with QuickBooks Online. In this case Cin7 Core originated Authorize.net payments will be pushed to QuickBooks Online directly through Cin7 Core. Therefore, the merchant user has to decide which ways the payment related transactions are synced to QuickBooks Online as Cin7 Core does not have control over managing it.
With integration to Cin7 Core, Cin7 Core will support processing card payments via Authorize.net. The following card payments are supported:
Visa
MasterCard
Discover
American Express
JCB
PayPal
Visa SRC
Apple Pay
Chase Pay
E-check
International payments are accepted for businesses that are based in the United States, Canada, United Kingdom, Europe or Australia.
Supported countries and currencies
Authorize.Net can accept transactions from merchants located in the United States, Canada, United Kingdom, Europe or Australia, in multiple currencies.
Business Locations |
Supported Currencies |
United States, Canada |
USD, CAD |
United Kingdom, Europe |
CHF, DKK, EUR, GBP, NOK, PLN, SEK, USD |
Australia |
AUD, NZD, USD |
Invoices will be sent in the currency in which the Authorize.Net gateway account is set up for. Invoices will be sent in the currency in which the Authorize.Net gateway account is set up for.
Authorize.net Integration Setup
You will need to generate an API Login ID and Transaction Key in Authorize.net before you can integrate the application with Cin7 Core. Please follow these instructions for detailed information.
Connecting Cin7 Core to Authorize.net
After generating your API credentials, you can then connect Cin7 Core and Authorize.net.
-
In Cin7 Core, go to Integrations → Authorize.net. Click the Connect to Authorize.netbutton to establish a connection between Cin7 Core and Authorize.net This will redirect you to Authorize.net, and if you are not already logged in, ask you for your login details.
Note: You will need to log in as an Account Owner or Account Administrator in order to authorize the connection.
Once logged in, you will be redirected to a page where you can allow or deny the request for permissions for shared data.
Allow the permissions to be redirected back to Cin7 Core and complete the connection.
Integration Setup
Once you have connected Cin7 Core and Authorize.net you will be taken back to the Authorize.net integration page in Cin7 Core, where on the Setup tab, you can:
Change the payment account associated with Authorize.net payments. The account must be able to receive payments.
View the time zone. Time zone cannot be edited from this page, this field will reflect the time zone selected in your General Settings. Time zone in Cin7 Core does not need to match time zone in Authorize.net and time zone settings do not affect one another.
Ask for billing information. When this setting is enabled, the customer will be prompted to enter billing address information at the payment screen. When the setting is disabled, the customer will not need to entire billing address on the payment screen.
Disconnect Cin7 Core and Authorize.net, if necessary. This process will revoke Cin7 Core's access to the Authorize.net account.
Click Save Settings. Your Authorize.net account can now send and receive payments through Cin7 Core.
Transaction History
You can view payments processed with Authorize.net from the Overview or Log tab.
Transaction Overview
The Overview tab gives a transaction summary of all completed transactions made through Authorize.net integration. This tab contains the following elements:
Refresh: Refreshes the data displayed on the dashboard with the most recent data.
Transactions: Shows the transaction count for the current day, week, month, and total transactions between the date Authorize.net was connected and the current date.
Payment details are listed for all transactions, showing payment date, related sale invoice, and sale amount. Payments can be searched by sale invoice number from the provided search box. The Gear icon can be used to customise the visible/hidden columns of the table – by default all are visible.
Overview tab should give a transaction summary of transactions made through Authorize.net integration.
Transaction Log
The Log tab displays history of all payment transactions done through Authorize.net. This tab shows additional details that are not displayed on the Overview tab. Payments can be searched by sale invoice number from the provided search box. The Gear icon can be used to customise the visible/hidden columns of the table – by default all are visible.
The log tab shows payment transactions with:
Payment Date: Date and timestamp of the transaction.
Sale Invoice: Sale invoice ID. This hyperlink can be clicked to view the related sale order invoice.
Amount: Transaction amount in Cin7 Core base currency.
Account: Bank account where payment is received (specified in Setup tab).
Authorize.net Payment ID: Reference # returned through Authorize,net application to Cin7 Core on completion of the payment transaction. This hyperlink can be clicked to view the transaction record in Authorize.net.
Payment Status: Displays if payment was successfully completed or not.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB