Paying with Authorize.net
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.
There are three basic steps to paying with Authorize.net:
Authorization: The payment gateway checks to make sure the customer has sufficient funds in their account—and then authorizes the purchase.
Capture: As soon as the purchase is authorized, a hold is placed on the money. At this point, the merchant can confidently ship goods to your customer.
Settlement: Money is transferred from the customer’s bank or credit card account to the merchant account. This typically takes a couple of days.
Customers can save their credit card details as a Payment profile from Cin7 Core and make payments without re-entering card details. Editing and deleting customer profiles can also take place from Cin7 Core.
Adding an Authorize.net pay link to a document
Insert a pay link into a sale quote or sale invoice document template so your customers can pay with ease. See Managing document templates for more information about adding mail merge fields to standard documents.
Note: Authorize.net must be connected and configured for pay links to show on the payment document. Simple text hyperlinks are not supported.
In Settings → Document & Email templates, download the quote and/or invoice template.
Copy an existing field to the location on the template where you want your pay link to appear.
Show the field code either by right-clicking the field and selecting Toggle Field Code or pressing Alt + F9 (on Windows) or Option + F9 (on Mac).
Replace the copied field with the mail merge field { MERGEFIELD AuthorizeNetPay} and the field will be replaced with the Authorize.net Pay Link image.
Toggle off the field codes by pressing Alt + F9 (on Windows) or Option + F9 (on Macs) again.
Save the edited template and upload.
Paying via a pay link
When a customer clicks on the pay link on an invoice, they are taken to a page displaying the quote/invoice and payment options, of which there are two options:
Pay the full outstanding value of the quote/invoice
Pay less – this will open a pop-up window where the customer can enter a different value (for prepayments, partial payments, etc.)
Clicking either of the pay options will take the customer to a secure payment gateway. From here, the customer can edit their credit card details and billing information (if required). The payment is processed by Authorize.net and if successful, the customer is returned to the sale screen where they can view the payment confirmation.
Paying via Cin7 Core B2B Portal
When going through the checkout of a Cin7 Core B2B sale, the customer can select Authorize.net as a payment method. After confirming the order, the customer can select Pay with card to be taken to the secure payment gateway powered by Authorize.net.
From here, the customer can edit their credit card details and billing information (if required). Customers can also save their credit card details as a Payment profile from Cin7 Core and select existing payment profiles to make payments without re-entering card details. Editing and deleting customer profiles can also take place from Cin7 Core.
The payment is processed by Authorize.net and if successful, the customer is returned to the sale screen where they can view the payment confirmation. No card data is stored in Cin7 Core, all card data is stored on the Authorize.net side.
Refunds
The process for issuing a refund for an invoice payment is the same process for issuing a refund for a non-invoice transaction. The steps you take will be slightly different based on whether it was a credit card or eCheck transaction. Refer more info:
Refunds in Authorize.net are not automatically synchronized with Cin7 Core. Refunds must be made through Authorize.net, once completed users needs to manually enter the refund entries in Cin7 Core in order to reconcile transactions.
- 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.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