Configuring and Using Acumatica Payments

You can use the functionality of Acumatica payments to provide more payment flexibility to users and the customers they serve. A user can do any of the following:

Process credit cards or electronic funds transfer (EFT) payments.
Create payment links that customer representatives can click to review a list of their documents that are pending payment.
Pay any number of invoices, prepayment invoices, or sales orders by using a credit card or EFT in several clicks. The user will not need to provide the company’s card data or account data to operators so that this data is entered into Acumatica ERP.
Collect customer bank payments directly through the Acumatica mobile app by using EMV (Europay, Mastercard, and Visa) card readers.

The payment links functionality is available in the system if the Acumatica Payments feature is enabled on the Enable/Disable Features (CS100000) form.

Payment links can be used in any of the following cases:

An AR clerk prints an invoice, and then a customer representative scans a QR code with a smart phone, opens a payment link, and pays the invoice or multiple open invoices via a credit card or EFT.
An AR clerk sends a payment link for an invoice to the customer. A customer representative opens the link and pays the invoice by using a credit card. The system automatically creates the payment and applies the payment to the invoice; the invoice is closed.
An AR clerk creates and releases an invoice and sends a payment link to the customer by email. A customer representative opens the link and pays the invoice or multiple open invoices. The payment is automatically created in Acumatica ERP and applied to the invoice or invoices. Each invoice is closed if it is fully paid or stays open if it is partially paid. If the customer representative pays the invoice with another means of payment without using the payment link, the payment link is closed automatically.
An AR clerk voids a credit memo or reverses a payment application to an invoice and runs synchronization between the payment link and the document. The customer representative opens the old payment link and sees new invoice details and an updated amount to be paid.
An AR clerk needs to check if any payments have been made for a particular invoice. The AR clerk opens the invoice and synchronizes the payment link with the document. If the invoice is paid, the system checks whether the respective payment has been created in Acumatica ERP. If it has not, the system creates the payment and applies to the invoice; the payment link is automatically updated with any changes made to the invoice (due date or other applied payments).
Multiple AR invoices are created for customers. In one click, an AR clerk releases all created invoices and creates and sends payment links to all customers.
Incoming payments received by using a webhook trigger automatic payment creation in Acumatica ERP for all payments made by customer representatives via payment links. Each payment is applied to the respective AR invoice, sales invoice, or sales order.
A salesperson creates a sales order, creates a payment link for it, and sends the link to the customer. The customer representative pays the full amount via the payment link, and the payment is automatically created in Acumatica ERP and applied to the respective sales order.
A salesperson creates a sales order, partially ships the order, and creates a sales invoice for the shipped part. The salesperson creates a payment link for the sales order and sends the link to the customer. A customer representative pays the full sales order amount, and the payment is automatically created in Acumatica ERP; they payment is applied to the sales invoice first, the remaining amount is applied to the respective sales order.

Currently, Acumatica Payments works for merchants located in the US and Canada only.

In this chapter, you will read about how to configure the processing of POS payments and Acumatica ERP payment links.

Back to TopIn This Chapter

Authorized Remainder After Partial Payment Capture

To simplify the processing of partially shipped orders, you can turn on smarter handling of pre-authorized payments. When a payment is partially captured for a sales invoice, the system will keep the remaining sales order amount pre-authorized—eliminating the need to manually create a new authorization. The system automatically creates a new payment for the remainder and pre-authorizes it.

To Configure Acumatica Payments

This topic describes the configuration steps that you need to perform in the system to set up Acumatica payments.

Accepting Payments by Using Mobile Card Readers

Your employees can seamlessly collect customer bank payments directly through the Acumatica mobile app. Whether they’re in the field or on the sales floor, employees can initiate secure EMV (Europay, Mastercard, and Visa) card payments by using a compact Bluetooth® Low Energy (LE) card reader. This simple, mobile-friendly solution empowers sales representatives and technicians to complete transactions quickly and confidently on the go.

To Set Up the EMV Card Reader Functionality

This topic describes the configuration steps that you need to perform in the system to set up the support of EMV card readers.

Processing of Payment Links

In Acumatica ERP, webhooks have been used to implement the receipt of payments that were made in the processing center by using payment links. The system receives information about all created payments from the processing center and processes those payments that were created by using payment links.

Support of POS Payments

Acumatica ERP provides support for point-of-sale (POS) payments. Users can now do the following:

Level 2 Data Transmission During Card Payments

All businesses accepting credit cards payments fall into a certain level of data processing. Each level is defined by the amount of information that is required or passed to complete the payment. Level 1 processing is the default one and is the basic level because the merchant does not add any extra data except the basic payment data to a transaction.

Level 3 Data Transmission During Card Payments

Visa and Mastercard charge a higher interchange rate to process payments created with corporate or government issued credit cards. They offer a special program under which it is possible to reduce this interchange rate called Level 3. Under the level 3 program, the merchant must submit the transactional data along with the payment data to the card networks. This data is used to identify the purchase in more detail to prevent fraud and charge backs. In return, the card networks lower the interchange rate.

Configuring and Using Acumatica Payments

You can use the functionality of Acumatica payments to provide more payment flexibility to users and the customers they serve. A user can do any of the following:[anchor|#ul_lpr_b1h_5yb]
*Process credit cards or electronic funds transfer (EFT) payments.
*Create payment links that customer representatives can click to review a list of their documents that are pending payment.
*Pay any number of invoices, prepayment invoices, or sales orders by using a credit card or EFT in several clicks. The user will not need to provide the company&rsquo;s card data or account data to operators so that this data is entered into Acumatica ERP.
*Collect customer bank payments directly through the Acumatica mobile app by using EMV (Europay, Mastercard, and Visa) card readers.

The payment links functionality is available in the system if the ''Acumatica Payments'' feature is enabled on the [HelpRoot_FormReference\CS_10_00_00|Enable/Disable Features] ([~/?ScreenId=CS100000|CS100000]) form.{br}

Payment links can be used in any of the following cases:[anchor|#_f7e424f5-66e7-4447-9d16-91a68e7c0006]
*An AR clerk prints an invoice, and then a customer representative scans a QR code with a smart phone, opens a payment link, and pays the invoice or multiple open invoices via a credit card or EFT.
*An AR clerk sends a payment link for an invoice to the customer. A customer representative opens the link and pays the invoice by using a credit card. The system automatically creates the payment and applies the payment to the invoice; the invoice is closed.
*An AR clerk creates and releases an invoice and sends a payment link to the customer by email. A customer representative opens the link and pays the invoice or multiple open invoices. The payment is automatically created in Acumatica ERP and applied to the invoice or invoices. Each invoice is closed if it is fully paid or stays open if it is partially paid. If the customer representative pays the invoice with another means of payment without using the payment link, the payment link is closed automatically.
*An AR clerk voids a credit memo or reverses a payment application to an invoice and runs synchronization between the payment link and the document. The customer representative opens the old payment link and sees new invoice details and an updated amount to be paid.
*An AR clerk needs to check if any payments have been made for a particular invoice. The AR clerk opens the invoice and synchronizes the payment link with the document. If the invoice is paid, the system checks whether the respective payment has been created in Acumatica ERP. If it has not, the system creates the payment and applies to the invoice; the payment link is automatically updated with any changes made to the invoice (due date or other applied payments).
*Multiple AR invoices are created for customers. In one click, an AR clerk releases all created invoices and creates and sends payment links to all customers.
*Incoming payments received by using a webhook trigger automatic payment creation in Acumatica ERP for all payments made by customer representatives via payment links. Each payment is applied to the respective AR invoice, sales invoice, or sales order.
*A salesperson creates a sales order, creates a payment link for it, and sends the link to the customer. The customer representative pays the full amount via the payment link, and the payment is automatically created in Acumatica ERP and applied to the respective sales order.
*A salesperson creates a sales order, partially ships the order, and creates a sales invoice for the shipped part. The salesperson creates a payment link for the sales order and sends the link to the customer. A customer representative pays the full sales order amount, and the payment is automatically created in Acumatica ERP; they payment is applied to the sales invoice first, the remaining amount is applied to the respective sales order.
((({S:Danger}Currently, Acumatica Payments works for merchants located in the US and Canada only.
)))
In this chapter, you will read about how to configure the processing of POS payments and Acumatica ERP payment links.
==In This Chapter{nestedtopics}==
*[HelpRoot_Integration\AR__con_Authorized_Remainder_after_Capture|Authorized Remainder After Partial Payment Capture]
*:To simplify the processing of partially shipped orders, you can turn on smarter handling of pre-authorized payments. When a payment is partially captured for a sales invoice, the system will keep the remaining sales order amount pre-authorized—eliminating the need to manually create a new authorization. The system automatically creates a new payment for the remainder and pre-authorizes it.
*[HelpRoot_Integration\AR__HOW_To_Configure_Acumatica_Payments|To Configure Acumatica Payments]
*:This topic describes the configuration steps that you need to perform in the system to set up Acumatica payments.
*[HelpRoot_Integration\AR__con_Mobile_Terminals|Accepting Payments by Using Mobile Card Readers]
*:Your employees can seamlessly collect customer bank payments directly through the Acumatica mobile app. Whether they’re in the field or on the sales floor, employees can initiate secure EMV (Europay, Mastercard, and Visa) card payments by using a compact Bluetooth® Low Energy (LE) card reader. This simple, mobile-friendly solution empowers sales representatives and technicians to complete transactions quickly and confidently on the go.
*[HelpRoot_Integration\AR__HOW_To_Set_Up_Mobile_Card_Readers|To Set Up the EMV Card Reader Functionality]
*:This topic describes the configuration steps that you need to perform in the system to set up the support of EMV card readers.
*[HelpRoot_Integration\AR__con_Processing_Payment_Links|Processing of Payment Links]
*:In Acumatica ERP, webhooks have been used to implement the receipt of payments that were made in the processing center by using payment links. The system receives information about all created payments from the processing center and processes those payments that were created by using payment links.
*[HelpRoot_Integration\AR__con_POS_Payments|Support of POS Payments]
*:Acumatica ERP provides support for point-of-sale (POS) payments. Users can now do the following:
*[HelpRoot_Integration\AR__con_Data_Transmission_Acumatica_Payments|Level 2 Data Transmission During Card Payments]
*:All businesses accepting credit cards payments fall into a certain level of data processing. Each level is defined by the amount of information that is required or passed to complete the payment. Level 1 processing is the default one and is the basic level because the merchant does not add any extra data except the basic payment data to a transaction.
*[HelpRoot_Integration\AR__con_Level3_Data_Transmission|Level 3 Data Transmission During Card Payments]
*:Visa and Mastercard charge a higher interchange rate to process payments created with corporate or government issued credit cards. They offer a special program under which it is possible to reduce this interchange rate called Level 3. Under the level 3 program, the merchant must submit the transactional data along with the payment data to the card networks. This data is used to identify the purchase in more detail to prevent fraud and charge backs. In return, the card networks lower the interchange rate.