When the system administrator enables the Integrated Card Processing feature, all the UI elements and forms related to credit card processing are displayed in the system.

If the Integrated Card Processing feature has been disabled, the system behavior will change as follows:

• If there are unreleased documents that have credit card transactions, these documents will not be shown on the Release AR Documents (AR501000) form, so an AR clerk should review each document manually by voiding or releasing the documents without processing a transaction in the system. In this case, the transactions will be processed in an external system, such as an ecommerce solution.

You will not be able to delete documents that have credit card transactions associated with them. On the Payments and Applications (AR302000) form, the system will display an error message if you try to delete such a document.

• The Validate Card Payments (AR513000) form will not be available in the system, so the documents that require validation can no longer be validated. These documents can be voided, released, or deleted, even if they required validation when the feature was in use.
• If a process runs an action that includes credit card processing, the system will display a warning message to inform you that the action could not be completed because the Integrated Card Processing feature is disabled.

With the Integrated Card Processing feature disabled, you can create documents with payment methods that have Credit Card selected in the Means of Payment box on the Payment Methods (CA204000) form. Documents associated with credit card payment methods will not require integrated processing.

If the Integrated Card Processing feature is disabled after is was formerly used, the following actions related to processing of documents that have the Pending Processing status are recommended:

• If you are going to close financial periods that may have documents in the Pending Processing status, to review the documents, you should run the Unreleased AR Documents report on the Close Financial Periods (AR509000) form by clicking Unreleased Documents on the form toolbar.
• On the Sales Orders (SO301000) form, the sales orders that have the Pending Processing status should be further processed by sales managers as if the order payments had the Balanced status.

If the Integrated Card Processing feature is disabled, you should stop automation schedules, if any, for the following forms:

• Generate Payments (AR511000)
• Capture Payments (AR511500)
• Card Payments Pending Review (CA403000)
• Deactivate Expired Cards (AR512500)
• Notify About Expiring Cards (AR512000)
• Payment Method Transaction History (AR406000)
• Payment Processing Log (AR406500)
• Processing Centers (CA205000)
• Synchronize Cards (CA206000)
• Validate Card Payments (AR513000)
• Import Settlement Batches
• Settlement Batches (CA507000) (CA307000)
• Credit Card Processing for Sales (SO507000)
• Credit Card Payments With Multiple Applications (SO401000)

For each type of credit card (such as Visa or MasterCard) that can be processed by the processing centers whose services your company is subscribed to, you use the Payment Methods (CA204000) form to configure a payment method specific to the type of credit cards. Acumatica ERP provides built-in elements for configuring payment methods based on various types of credit cards.

For each payment method based on a specific credit card type, you can specify which elements are used and which are not. For the elements to be used, you can specify which should be used as the card identifier, which elements should be encrypted and masked on display, and how each of these elements should be masked.

For additional details, see Payment Methods for Customers.

For each customer that will use credit cards to cover its payments automatically, users can enter information about the customer’s cards on the Customer Payment Methods (AR303010) form. One of the cards should be selected as the default customer payment method on the Payment Settings tab of the Customers (AR303000) form.

Acumatica ERP stores card numbers and other information encrypted in the database and masks this information when it is displayed on the forms. Sensitive data, such as the card’s security code, is stored encrypted prior to the first successful authorization. After that, this data is deleted from the database, and subsequent transactions require no verification of the security code with the processing center.

Automatic payment collection can be initiated from the Capture Payments (AR511500) form, which allows the users to perform mass-processing of customer payments for invoices that have the specific credit terms assigned. For more details on processing payments, see Card Payments.

On the Validate Card Payments (AR513000) form, you can use a predefined synchronization schedule for validating card payments, which runs once a day. You can review the Validate Card Payments schedule on the Automation Schedules (SM205020) form.

The Validate Card Payments schedule has the following default settings on the Automation Schedules form:

• Active: Cleared
• Executions to Keep in History: 5
• Next Execution: <Date> 12:00 AM

This setting is read-only but can be overridden on the Schedule tab.

This schedule can be configured by a user to which the Administrator, AR Admin, or AR Clerk role is assigned on the Users (SM201010).

On the Validate Card Payments form, to set up the predefined automation schedule, a system administrator should perform the following general instructions:

1. On the form toolbar, click Schedules.
2. In the Automation Schedules dialog box, which is opened, select Validate Card Payments in the Screen ID box.
3. Select the Active check box.
4. Specify the required settings for the schedule, and save the new schedule.

The Validate Card Payments schedule will run for all active processing centers to which it has been added. For details, see To Schedule Validation of Card Payments.

If your company has automatic payment collection configured, credit card expiration dates must be monitored closely. Use the following forms to manage expired cards and those that will expire soon:

• On the Notify About Expiring Cards (AR512000) form, users can view the cards that will expire soon and send notifications to customers about approaching expiration dates on their cards.
• By using the Deactivate Expired Cards (AR512500) form, users can deactivate selected cards that have expired or all expired cards.