Processing Centers

Form ID: (CA205000)

You can use this form to configure a processing center for processing inbound payments—such as a card processing center to which your company is subscribed.

Note:

This form appears in the system if the Integrated Card Processing feature has been enabled on the Enable/Disable Features (CS100000) form.

Form Toolbar

The form toolbar includes standard and form-specific buttons and commands. For the list of standard buttons, see Form Toolbar and More Menu. The form-specific commands are listed in the following table.


Button	Description
Test Credentials	Performs a test transaction to validate the credentials you have entered for the particular processing center.
Update Expiration Dates	Redirects you to the Update Expiration Dates (CA208000) hidden processing form, which displays the list of customer payment methods that do not have expiration dates. On this form, you click Process to retrieve expiration dates from Authorize.Net records for the customer payment methods or Process All to retrieve expiration dates for all records. This button is displayed if the selected processing center supports unmasked expiration dates and if there are customer payment methods based on a payment method associated with the selected processing center that have no expiration date recorded in the system.
Create/Update Webhook	Checks whether webhooks have been created in both MYOB Acumatica and the merchant account linked to the selected processing center. If no webhook exists in either location, the system creates a webhook. If a webhook has been created in only one of these places, the system updates the processing center webhook with the URL, username, and password of the MYOB Acumatica webhook. Once the system has created or updated webhooks, it populates the Webhook ID box on the Payment Links tab with the ID of the MYOB Acumatica webhook, and marks the created webhook as predefined in the database. Predefined webhooks cannot be deleted on the Webhooks (SM304000) form. Note: Currently, only one webhook can be active for each location in the merchant account. Thus, you can set up multiple processing centers in MYOB Acumatica to work with a single location in your merchant account, but only one processing center will receive webhook notifications from this location.

Summary Area

This area displays the settings used for the processing center to which your company is subscribed.


Element	Description
Proc. Center ID	The unique identifier of the processing center.
Name	A detailed description of the processing center. You use an alphanumeric string of up to 30 characters.
Cash Account	The cash account associated with the processing center. This cash account defines the currency in which the transaction amounts will be processed. For Authorize.Net plug-in, the currency of the transactions is defined when you subscribe to the Authorize.Net services. The system will use the identifier of the currency to validate that the transaction is posted to a cash account with the same currency identifier.
Currency	The currency used for the selected account. The box is filled in automatically by the system as follows: If the Multicurrency Accounting feature is not enabled on the Enable/Disable Features (CS100000) form, the system uses the base currency. If the Multicurrency Accounting feature is enabled on the Enable/Disable Features (CS100000) form, the system uses the currency of the account, as specified on the chart of accounts to which the cash account is linked.
Active	A check box that indicates (if selected) that the processing center is active in the system.
Payment Plug-In (Type)	The built-in plug-in developed for the particular processing center based on the protocol used by the center and other processing requirements. One of the following options can be selected: Authorize.Net API Plug-In: This plug-in uses an API supported by Authorize.Net. It provides PCI DSS–compliant integration with Authorize.Net; sensitive credit card information is not stored in the MYOB Acumatica database. This option is available if the Authorize.Net Payment Plug-In feature is enabled on the Enable/Disable Features (CS100000) form. If you have payment methods that have been configured with processing centers that are no longer supported (Authorize.Net AIM and Authorize.Net CIM), you should replace these payment methods with a new payment method by using the Payment Method Converter (CA207000) form. For more details, see To Replace a Processing Center that Uses a Discontinued Plug-In. Shopify Payments API Plug-In: This plug-in uses an API supported by Shopify. Stripe Plug-In: This plug-in makes it possible to integrate the processing center with the Stripe processing center. This option is available if the Stripe Payment Plug-In feature is enabled on the Enable/Disable Features (CS100000) form. Acumatica Payments Plug-In: This plug-in makes it possible to use MYOB payments. This option is available if the MYOB Payments feature is enabled on the Enable/Disable Features (CS100000) form.
Allow Direct Input	A check box that indicates (if selected) that users can enter credit card information by using MYOB Acumatica forms, and then the system transfers this data to the Authorize.Net server on which it is stored. This check box is displayed if Authorize.Net API is selected in the Payment Plug-In (Type) box. Important: The direct input mode for entering credit card information has been discontinued. If this check box was selected for a particular processing center, the check box remains on the form and is still selected, but a warning is displayed. For a newly created processing center or an existing processing center for which this check box was cleared, the check box does not appear on this form. To enter credit card data when customer payment methods are created for payment methods based on credit cards, you should use the hosted form provided by the applicable processing center.
Allow Saving Payment Profiles	A check box that indicates (if selected) that when a user enters a card payment, the system allows the saving of a payment profile by extracting the payment profile ID from the processing center and creating a customer payment method associated with the credit card. If the check box is cleared, when the user enters a card payment, the system will associate the payment with the credit card transaction, but will not allow the user to create a customer payment method. This check box is available only if the plug-in used for the processing center supports the creation of customer profiles. Note: If this check box is selected and the Save Payment Profiles box is set to Never on the General tab of the Customer Classes (AR201000) form for the customer class of the customer, the system will never save customer payment profiles for customers of this class, even though the settings of the processing center allow it.
Synchronize Deletion	A check box that indicates (if selected) that when a user deletes a customer payment method that is registered with Authorize.Net or Stripe, the payment method information is automatically deleted from the Authorize.Net or Stripe server. This check box is displayed if Authorize.Net API Plug-In or Stripe plug-in is selected in the Payment Plug-In (Type) box.
Accept Payments from New Cards	A check box that indicates (if selected) that when a user is processing a payment for a particular payment method, the system will accept a payment from a new credit card. This check box is cleared and unavailable if Shopify Payments API Plug-In is selected in the Payment Plug-In (Type) box.
Allow Unlinked Refunds	This check box indicates (if selected) that it is possible to process unlinked refunds for card payment methods associated with the processing center. This check box is cleared and unavailable if Shopify Payments API is selected in the Payment Plug-In (Type) box.
Allow Payment Links	A check box that indicates (if selected) that the payment methods of the selected processing center will support the processing of payment links. If this check box is selected, the Payment Links tab appears on the form. The check box appears on the form if the plug-in selected in the Payment Plug-In (Type) box supports payment links.
Accept Payments from POS Terminals	A check box that indicates (if selected) that the processing center supports payments made via POS terminals. The check box appears on the form if the MYOB Payments feature is enabled on the Enable/Disable Features (CS100000) form and Acumatica Payments plug-in is selected in the Payment Plug-In (Type) box on the current form. When this check box is selected, the POS Terminals tab appears on the form.

Plug-In Parameters Tab

On this tab, you specify your company's settings used by the plug-in to access the processing center. The required keys can be imported from the plug-in, while you should enter the values manually.

The specific parameters listed on this tab depend on the option selected in the Payment Plug-In (Type) box in the Summary area. For details on specific settings, see the procedures dedicated to a particular plug-in configuration in the Configuring Payment Processing chapter.

The table toolbar includes only standard buttons. For the list of standard buttons, see Table Toolbar.

Table 1. Plug-In Parameters Tab (Authorize.Net API)If *Authorize.Net API Plug-In* is selected as the plug-in type in the Summary area, the tab consists of the following columns and the noted plug-in parameters.
Column	Description
ID	The identifier of the key required by the plug-in developed for the processing center.
Description	A description of the key.
Value	The value of the key to be used by your company to access the services provided by the processing center. For Authorize.Net, you specify the values for the following parameters: HIDEBANKAC: A value that indicates that the option to enter bank account details should not be displayed on the hosted form. You select one of the following values: 0 (default): The option to specify bank account details is hidden. 1: The option to specify bank account details is displayed. MERCHNAME: The API login that you have created in the Authorize.Net Merchant Interface. SIGNKEY: The signature key used by webhooks. MYOB Acumatica uses the signature key to get a response from the processing center. TESTMODE: A value that indicates whether you are using the production account or a sandbox account. You select one of the following values: 0 (default): The production URL is used for connection. 1: The sandbox merchant account is used for connection. TRANKEY: The transaction key you have created in the Authorize.Net Merchant Interface. USEWEBHOOK: A check box that indicates (if selected) that webhooks can be created for the processing center. If this check box is selected, the SIGNKEY parameter must be specified. This check box is cleared by default. VALIDATION: The processing mode for the request. You select one of the following options: Test Mode (default): The credit card data will be sent to the processing center without it being validated there; a test transaction will not be generated. This option is recommended for use in a test environment. Live Mode: The credit card data will be sent to the processing center for generating a test transaction to validate the customer profile. The processing center will generate a test transaction with the 0.00 amount and then void it automatically. You must select this option if you are setting up a production environment.

Table 2. Plug-In Parameters Tab (Shopify Payments API)If *Shopify Payments API Plug-In* is selected as the plug-in type in the Summary area, the tab consists of the following columns and the noted plug-in parameter.
Column	Description
ID	The identifier of the key required by the plug-in developed for the processing center.
Description	A description of the key.
Value	The value of the key to be used by your company to access the services provided by the processing center. For the Shopify Payments plug-in, you specify the value of the STORENAME parameter, which is the name of the Shopify store defined on the Shopify Stores (BC201010) form.

Table 3. Plug-In Parameters Tab (Stripe Payments)If *Stripe Plug-In* is selected as the plug-in type in the Summary area, the tab consists of the following columns and the noted plug-in parameters.
Column	Description
ID	The identifier of the key required by the plug-in developed for the processing center.
Description	A description of the key.
Value	The value of the key to be used by your company to access the services provided by the processing center. For Stripe, you specify the values for the following parameters: ADDRVERIF: A check box that indicates (if selected) that address verification is enabled in the processing center. If the check box is selected, you will need to enter the postal code and address line in the Create New Card dialog box, which opens on the Customer Payment Methods (AR303010) form when you are creating a new card. MODE: The processing mode for the request. One of the following values can be selected: Live Mode: To process live transactions Test Mode: To test the setup MOTO: A check box that indicates (if selected) that processing of Mail Order/Telephone Order (MOTO) transactions is turned on. If this check box is selected, 3DSecure for transactions is turned off. This parameter and the ADDRVERIF parameter must be turned on in the merchant's Stripe profile. PUBLICKEY: The API publishable key that is used for client-side requests. SECRETKEY: The API secret key that is used for server-side requests.

Table 4. Plug-In Parameters Tab (MYOB Payments)If *Acumatica Payments Plug-In* is selected as the plug-in type in the Summary area, the tab consists of the following columns and the noted plug-in parameters.
Column	Description
ID	The identifier of the key required by the plug-in.
Description	A description of the key.
Value	The value of the key to be used by your company to access the services provided by the processing center. For MYOB payments, you specify the values of the following parameters: APIKEY: The API secret key. This value should be copied from the merchant account in the MYOB Payments Partner Gateway. HASHKEY: The API user hash key. This value should be copied from the merchant account in the MYOB Payments Partner Gateway. LOCATIONID: The location ID. This value should be copied from the merchant account in the MYOB Payments Partner Gateway. RFNDUNSTTL: A check box that indicates (if selected) that refunds for unsettled transactions are allowed for the processing center. TESTMODE: The processing mode for the request. One of the following values can be selected: Live Mode: To process live transactions Test Mode: To test the setup USERID: The ID of the API user. This value should be copied from the merchant account in the MYOB Payments Partner Gateway. WEBHOOKPWD: The password for webhook authorization. This value is generated by the system and is filled in automatically when you select MYOB Payments Plug-In in the Payment Plug-In (Type) box. When you click Create/Update Webhook on the form toolbar to create a webhook, this value is sent to the merchant account in the MYOB Payments Partner Gateway. WEBHOOKUSR: The username for webhook authorization. This value is generated by the system and is filled in automatically when you select MYOB Payments Plug-In in the Payment Plug-In (Type) box. When you click Create/Update Webhook on the form toolbar to create a webhook, this value is sent to the merchant account in the MYOB Payments Partner Gateway. Tip: You can manually change the values for the WEBHOOKPWD and WEBHOOKUSR parameters. If you do, you should click Create/Update Webhook on the form toolbar to send the updated settings to the merchant account in the MYOB Payments Partner Gateway.

Payment Methods Tab

This tab lists (in a tabular format) the payment methods that use the processing center.

The table toolbar includes only standard buttons. For the list of standard buttons, see Table Toolbar.


Column	Description
Payment Method	The payment method that uses the processing center.
Active	A check box that indicates (if selected) that this processing center can be used with the selected payment method in documents.
Default	A check box that indicates (if selected) that this processing center is set by default in a document when the payment method is selected in the document.
Funds Hold Period (Days)	A read-only column that shows the number of days the card processing system holds funds on a customer's card.
Reauthorization Delay (Hours)	A read-only column that shows the number of hours that should pass between voiding an expired authorization request and reauthorization.

Preferences Tab

On this tab, you specify the settings that the system uses while connecting to processing center servers.

Table 5. Connection Section
Element	Description
Transaction Timeout (s)	The time interval (in seconds) after which a user may perform another attempt to process a transaction (for example, authorize or capture) if the processing center has not returned any result for the previous attempt because of a loss of connection or some other reason.
Number of Additional Synchronization Attempts	The number of additional attempts to establish a connection that the system should perform once it has received an incorrect response from the processing server. You can specify a value from 0 to 10. If you specify 0, the system performs only one synchronization attempt.
Delay Between Synchronization Attempts (ms)	The time interval (in milliseconds) between the synchronization attempts. You can specify a value from 0 to 1000.

Table 6. Profile Creation Section
This section is displayed if *Authorize.Net API Plug-In* or *Stripe Plug-In* is selected in the Payment Plug-In (Type) box.
Element	Description
Create Additional Customer Profiles	A check box that indicates (if selected) that an additional customer profile will be created for a customer account on the Authorize.Net or Stripe side if the number of payment profiles created for the customer account exceeds the value specified in the Maximum Credit Cards per Profile box. This check box is displayed if Authorize.Net API Plug-In or Stripe Plug-In is selected in the Payment Plug-In (Type) box.
Maximum Credit Cards per Profile	The number of payment methods allowed for each customer account. The default value is 10 according to the internal restrictions of Authorize.Net, and we strongly recommend that you not increase the value. The check box is displayed if the Create Additional Customer Profiles check box is selected in this section.

Table 7. Reauthorization SectionThe settings in this section are related to the system's processing of a reauthorization API request.
Element	Description
Number of Reauthorization Retries	The maximum number of attempts to resend the same reauthorization API request. It can be performed by a user or the system if reauthorization is run by the scheduler. The default value is 3.
Reauthorization Retry Delay (Hours)	The delay between a failed attempt to send a reauthorization request and the next attempt. The default value is 3.

Table 8. Settlement Section
Element	Description
Import Settlement Batches	A check box that indicates (if selected) that settlement batches can be imported for the processing center. For payments for this processing center, the Cleared check box will be selected on the Financial tab of the Payments and Applications (AR302000) form after the import of the settlement batch.
Import Start Date	The date on which the import of settlement batches can start. This check box becomes available and required if the Import Settlement Batches check box is selected. Note: If the import of settlement batches was turned off for some time (that is, if the Import Settlement Batches check box was cleared) and then restarted, a new import start date can be specified.
Last Settlement Date	The date on which the most recent settlement batch for the processing center was successfully settled. This box is read-only.
Deposit Account	The cash account in which the settlement batch will be deposited. This box is available and required only if the Import Settlement Batches check box is selected. You can select only non-clearing accounts, that is, accounts for which the Clearing Account check box is cleared on the Cash Accounts (CA202000) form.
Automatically Create Bank Deposits	A check box that indicates (if selected) that the system will automatically create bank deposits after importing the settlement batch.

Fees Tab

If a settlement report includes fees, these fees are displayed by the system on the Settlement Batches (CA307000) form and are added to bank deposits as charges. On this tab you have to specify the bank deposit charge and entry type for each fee type.

The table toolbar includes only standard buttons. For the list of standard buttons, see Table Toolbar.


Column	Description
Fee Type	The type of fee used by the processing center. Only one line for each fee type can be added.
Entry Type	The entry type that should be specified in the charge in a bank deposit for the corresponding fee type. You can select an entry type for which CA is specified in the Module column on the Entry Types (CA203000) form.

Payment Links Tab

On this tab, you specify the branches that will use the current processing center as the default one for the creation of payment links. For each branch, you can specify the payment method and cash account that should be used for creating payments via the payment links.

This tab appears on the form if MYOB Payments Plug-In is selected in the Payment Plug-In (Type) box of the Summary area and the Allow Payment Links check box is selected.

Table 9. Payment Links ElementsThese settings (described below) apply to the payment links in the branches listed in the table.
Element	Description
Allow Partial Payment	A check box that indicates (if selected) that a document can be paid partially. That is, a customer can reduce the amount to pay before making the payment.
Webhook ID	Read-only. The ID of the webhook created in the system. If this box is empty, no webhook has been created. To create a webhook, you should click Create/Update Webhook on the form toolbar. The created webhook is marked in the database as predefined and users will not be able to delete it on the Webhooks (SM304000) form.

Table 10. Table
The table toolbar includes only standard buttons. For the list of standard buttons, see Table Toolbar.

For each row in the table, one of the following combinations of columns must be filled in:

Credit Card Payment Method and Credit Card Cash Account

EFT Payment Method and EFT Cash Account
Column	Description
Branch	The branch specified on the Financial tab of the Invoices and Memos (AR301000), Invoices (SO303000), or Sales Orders (SO301000) form for an invoice, sales invoice, or sales order to which the payment link settings in the row will apply.
Use by Default	A check box that indicates (if selected) that the currently selected processing center should appear by default for the creation of payment links. A user can override this setting for a particular document. Only one default processing center can be selected for each combination of a branch and a currency.
Credit Card Payment Method	The payment method (along with its description) that will be used in a created payment if a card payment for the payment link is received from the current processing center and if the related invoice or sales order originated in the branch defined for the row. The lookup table in this box displays payment methods that meet both of the following criteria: On the Payment Methods (CA204000) form, Credit Card is selected in the Means of Payment box. The current processing center is specified and active on the Processing Centers tab of the Payment Methods (CA204000) form. If this column is filled in, Credit Card Cash Account must also be filled in.
Credit Card Cash Account	The cash account (along with its description) that will be used along with the credit card payment method. The lookup table in this box displays cash accounts that meet both of the following criteria: The cash account is specified for the payment method on the Allowed Cash Accounts tab of the Payment Methods (CA204000) form. The cash account is visible for the branch defined in the row—that is, this branch is selected for the cash account in the Branch column on the Allowed Cash Accounts tab. If this column is filled in, Credit Card Payment Method must also be filled in.
EFT Payment Method	The payment method (along with its description) that will be used for payment creation if an EFT payment for the payment link is received from the current processing center and if the related invoice or sales order originated in the branch defined for the row. The lookup table in this box displays cash accounts that meet both of the following criteria: On the Payment Methods (CA204000) form, EFT is selected in the Means of Payment box for the payment method. The current processing center is specified and active for the payment method on the Processing Centers tab of the Payment Methods (CA204000) form. If this column is filled in, EFT Cash Account must also be filled in.
EFT Cash Account	The cash account (along with its description that will be used along with the EFT payment method. The lookup table in this box displays cash accounts that meet both of the following criteria: The cash account is specified for the payment method on the Allowed Cash Accounts tab of the Payment Methods (CA204000) form. The cash account is visible for the branch defined in the row—that is, this branch is selected for the cash account in the Branch column on the Allowed Cash Accounts tab. If this column is filled in, EFT Payment Method must also be filled in.

POS Terminals Tab

On this tab, you can import the available POS terminals from the processing center and review their settings. The active POS terminals that are listed on this tab (that is, those for which the Active check box is selected) will be available for selection on the Payments and Applications (AR302000), Cash Sales (AR304000), Sales Orders (SO301000), and Invoices(SO303000) forms.

The tab appears on the form if the Accept Payments from POS Terminals check box is selected for the processing center.

Table 11. Table Toolbar
The table toolbar includes standard buttons and buttons that are specific to this table. For the list of standard buttons, see Table Toolbar. The table-specific buttons are listed below.
Button	Description
Import Terminals	Imports the settings of available POS terminals into the system. The system makes an API call to the payment processor, fetches all the IDs (Terminal ID) and names (Terminal Name) of the terminals, and displays them in the table.

Table 12. Table Columns
Column	Description
Terminal ID	Read-only. The ID of the terminal.
Terminal Name	Read-only. The terminal name.
Display Name	The terminal name to be displayed in the system, which must be unique. A system administrator can give the terminal a user-friendly name for easy identification of the terminal in use. If the terminal settings are imported from the payment processor, the system inserts the terminal name in this column by default.
Active	A check box that indicates, if selected, that the terminal is activated in MYOB Acumatica. If the check box is cleared, the system considers the terminal to be deactivated, and it will not appear in the Terminal lookup box on data entry forms. When you import terminals for the first time (that is, when you click the Import Terminals button on the table toolbar), this check box is selected by default for each imported terminal.