Order Synchronization: Card Payments

In MYOB Acumatica Retail Connectors, users can import and, if necessary, process debit and credit card payments from external e-commerce systems through integration with payment gateways. The ability to use card-processing features, such as authorization, capture, voiding, and refunding card transactions, is available if the Integrated Card Processing feature is enabled on the Enable/Disable Features (CS100000) form. This topic explains how to configure the Authorize.Net payment provider for processing of payments made in the BigCommerce store after they are imported to MYOB Acumatica.

Configuration of Authorize.Net Payment Method for Integrated Card Processing

Authorize.Net is a processing center that accepts transactions through an application programming interface and processes payments online. Before credit card payments can be imported from a BigCommerce store, you need to configure payment processing via Authorize.Net as follows:

1. Sign up for an Authorize.Net account.

   For testing purposes, you can create a sandbox account. You will use the API login, transaction, and optionally signature key generated during the account creation to connect the processing center to the Authorize.Net server.

2. Activate integrated card processing.

   You enable integrated card processing (that is, the ability to use additional card processing steps for AR payments) by selecting the Enable Integrated CC Processing check box on the Accounts Receivable Preferences (AR101000) form.

3. Configure an Authorize.Net processing center.

   You set up the processing center on the Processing Centers (CA205000) form. Before you proceed with the configuration, you need to obtain the API login, signature key, and transaction key that you will use to connect to the Authorize.Net server. For instructions on setting up a processing center in MYOB Acumatica, see Integration with Authorize.Net Through the API Plug-in and To Configure the Authorize.Net Processing Center with the API Plug-in.

4. Configure a card-based payment method in MYOB Acumatica.

   After you have configured the processing center, on the Payment Methods (CA204000) form, you need to create a payment method that will be associated with the processing center. For information about setting up payment methods in MYOB Acumatica, see Cash Management: Payment Methods.

5. Configure the Authorize.Net payment gateway in the BigCommerce store.

   You set up the Authorize.Net payment provider in the BigCommerce store using the same API login, signature key, and transaction key that you have used to configure the processing center in MYOB Acumatica. For information about configuring payment providers in the external system, refer to the BigCommerce documentation.

6. Map the card-based payment method with the payment method defined in the BigCommerce store.

   You map payment methods between MYOB Acumatica and the BigCommerce store on the BigCommerce Stores (BC201000) form. When a payment is imported from the BigCommerce store to MYOB Acumatica, a prepayment is created on the Payments and Applications (AR302000) form based on the payment method from MYOB Acumatica that was mapped to the payment method used for payment in the BigCommerce store.

For step-by-step instructions on configuring and importing payments based on the Authorize.Net payment method, see Order Synchronization: To Configure and Import Authorize.Net Payments.

Mapping of Card-Based Payment Methods

During the configuration of a connection to the BigCommerce store, one of the steps you perform is the mapping of payment methods configured in MYOB Acumatica with payment methods configured in the BigCommerce store. You define payment method mapping in the table on the Payment Settings tab of the BigCommerce Stores (BC201000) form.

For the Authorize.Net store payment method, you specify the following:

• ERP Payment Method: The identifier of the payment method in MYOB Acumatica that was configured to use the same processing center as was used for setting up the payment provider in the online store.
• Cash Account: A cash account that was specified for the payment method on the Allowed Cash Accounts tab on the Payment Methods (CA204000) form.
• Proc. Center ID: The identifier of the processing center configured for the payment method on the Processing Centers tab of the Processing Centers (CA205000) form.
• Active: A check box that you select for a payment method to indicate that payments made in the e-commerce system that are based on should be imported to MYOB Acumatica.
• Release Payments and Refunds: A check box that you select to indicate that the payment should be immediately released after it is imported to MYOB Acumatica. If this check box is selected for a card-based payment method associated with a credit card processing center in MYOB Acumatica (that is, for the payment method for which a processing center is selected in the Proc. Center ID column), only payments that have been captured in the store will be automatically released on import. Payments that have been authorized but not captured in the store need to be processed after import and then released manually or by using the Release AR Documents (AR501000) form.
• Process Refunds: A check box that indicates (if selected) that refunds made to the payment method should be imported to MYOB Acumatica. This check box is selected and unavailable for card payment methods for which a processing center is specified, which indicates that all refunds made to such payment methods must be imported to MYOB Acumatica.

Import of Payments Based on Credit Cards (Authorize.Net)

A customer who has signed in to the BigCommerce store can save credit card details during checkout. When this customer selects the Authorize.Net payment method, enters the details of a new card, selects the Save this card for future transactions check box, and then places an order, the details of the credit card are saved in the processing center configured in the BigCommerce store.

When the payment is imported from BigCommerce to MYOB Acumatica (as part of the synchronization of the Sales Order entity or the Payment entity), on the Payments and Applications (AR302000) form, the system creates a document of the Prepayment type with the Pending Processing status. In the Summary area of the created document, the system inserts the following information:

• Payment Method: The payment method that has been mapped to the store payment method on the Payment Settings tab of the BigCommerce Stores (BC201000) form
• Cash Account: The cash account selected for the mapped payment method
• Payment Ref.: The number of the related credit card transaction in the processing center
• Processing Status: The processing status of the credit card transaction. Depending on the last successful operation with the transaction, the processing status can be one of the following:
  • Pre-Authorized: The payment has been authorized but the funds have not been captured. The last successful operation was Authorize Only.
  • Captured: The funds have been captured. The last successful operation with the credit card transaction was either Authorize and Capture or Capture Authorized.
  • Pre-Auth./Capture Pending Validation: The last successful operation with the credit card transaction is unknown. To get the correct processing status of the credit card transaction, you can use the Validate Card Payment action on the Payments and Applications form.

On the Card Processing tab on the Payments and Applications form, the system creates a row for the last successful operation with the credit card transaction. In the Proc. Center Response Reason box, Imported External Transaction indicates that the information about the credit card transaction operation has been imported from the external e-commerce system.

In the Tran. Type box, the transaction operation can have one of the following types:

• Authorize Only: The payment was authorized when the order was placed but has not yet been captured.
• Authorize and Capture: The payment was captured when the order was placed.
• Capture Authorized: The payment was authorized when the order was placed, and then the funds were captured in the control panel of the store.
• Unknown: The status of the operation with the credit card transaction is unknown.

The following diagram illustrates the workflow of importing a sales order to MYOB Acumatica from a BigCommerce store where it was placed and paid by a card based on a payment method for which integrated card processing has been configured in MYOB Acumatica.

Deferred Processing of Imported Credit Card Payments

External credit card transactions that require validation are displayed on the Deferred Processing Required tab of the Validate Card Payments (AR513000) form and have the Load Payment Profile check box selected.

When the validation process is started, the system performs the following actions:

1. On the Customer Payment Methods (AR303010) form, creates a customer payment method based on the payment profile from the processing center.
2. Links the customer payment method to the credit card transaction.
3. Links the customer payment method to the imported payment.
4. Requests the status of the credit card transaction, and updates the processing status of the transaction and the status of the prepayment, if necessary.

   If the updated processing status of the transaction is Captured, the status of the prepayment changes to Balanced. If on the General tab of the Accounts Receivable Preferences (AR101000) form, the Enable Integrated CC Processing check box is selected, the system releases the prepayment.

Customizations may support forced validation of all imported credit card transactions. In this case, all credit card transactions imported from external systems will be displayed on the Deferred Processing Required tab of the Validate Card Payments form and will need to be validated.