Payment Settings Configuration

Configuring the Payment Settings Record

Creating the Payment Settings Record

By generating and configuring the Payology Lite App's Payment Setting, the Salesforce Administrator can determine when and how check transactions will be transmitted to the Check21.com Payment Gateway. By creating the record, a user can also automate the creation of Client Accounts, transferring account data from the Check21.com Payment Gateway directly to the Payology Lite App in Salesforce.

Generating a Custom Settings Record

To begin the Payment Settings record creation process, the Salesforce Administrator must first navigate to the Payment Settings navigation item. To do so, please follow these steps:

  1. Click the Apps menu on the top left-side corner of the screen.
  2. In the search field type and click on "Payology Settings".
  3. Click the "New" button on the top right-hand side of the object window.
  • Users who prefer a walk-thru of this process at no cost, can call or email their Payology Account Manager to schedule a date/time. * Users who prefer to create the record themselves can look for a description of each field below.

Field Label

Type

Description

Active

Checkbox

Indicates the Active Payment Record being used. Only one record can be set to Active.

Allow Special Validation Exceptions

Checkbox

Allows Salesforce Administrators to toggle between a variety of Batch and Check Statuses. This field is most commonly enabled only when migrating between legacy solutions and Payology. It is also used in the rare occasions errors occur between Salesforce and the Check21.com Payment Gateway.

Auto Transmit Check Items

Checkbox

If enabled, Payology Check Scanning batches which are closed within the Check Scanning interface will be automatically transmitted to the Check21.com Payment Gateway, transitioning the Batch status from "Closed" to "Transmitting" and subsequently "Transmitted". If disabled, the Batch will remain "Closed" until a user clicks the "Transmit Batch" button on the record.

Close Batch Validation

Checkbox

By default, this field will be set to "True". The field will toggle between "True" and "False" each time a batch is "Closed" within the Check Scanning UI. Its purpose is to ensure a user cannot close a batch from the "Batch" record and only from the UI where batches are validated.

Conflict on Account

Checkbox

When enabled, checks whose Account Number captured by the OCR differs from the Account Number entered by the user in the Check Scanning or Check Capture UI's will result in a Transaction Status of "Pending Check Review" in the Check21.com Payment Gateway. A Check21.com Agent will review the check for accuracy before submitting the item to the bank. If disabled, no validation will occur. * Please note, there may be a cost associated with enabling this function. Must be used in combination with "Send Check Validation Exceptions to C21", marked "True".

Conflict on Amount

Checkbox

When enabled, checks whose Amount captured by the OCR differs from the Amount entered by the user in the Check Scanning or Check Capture UI's will result in a Transaction Status of "Pending Check Review" in the Check21.com Payment Gateway. A Check21.com Agent will review the check for accuracy before submitting the item to the bank. If disabled, no validation will occur. * Please note, there may be a cost associated with enabling this function. Must be used in combination with "Send Check Validation Exceptions to C21", marked "True".

Conflict on Check Number

Checkbox

When enabled, checks whose Check Number captured by the OCR differs from the Check Number entered by the user in the Check Scanning or Check Capture UI's will result in a Transaction Status of "Pending Check Review" in the Check21.com Payment Gateway. A Check21.com Agent will review the check for accuracy before submitting the item to the bank. If disabled, no validation will occur. * Please note, there may be a cost associated with enabling this function. Must be used in combination with "Send Check Validation Exceptions to C21", marked "True".

Conflict on Routing

Checkbox

When enabled, checks whose Routing Number captured by the OCR differs from the Routing Number entered by the user in the Check Scanning or Check Capture UI's will result in a Transaction Status of "Pending Check Review" in the Check21.com Payment Gateway. A Check21.com Agent will review the check for accuracy before submitting the item to the bank. If disabled, no validation will occur. * Please note, there may be a cost associated with enabling this function. Must be used in combination with "Send Check Validation Exceptions to C21", marked "True".

Content Access

Text (Encrypted)

Credentials provided in the utilization of the Check21.com Payment Gateway.

Content Key

Text (Encrypted)

Credentials provided in the utilization of the Check21.com Payment Gateway.

Created By

Lookup(User)

Salesforce User who created the Payment Settings record.

Default Account

Lookup(Account)

Salesforce Account which will be utilized if Check record is not associated with an Account.

Last Modified By

Lookup(User)

Salesforce User who last modified the Payment Settings record.

Owner

Lookup(User,Group)

Salesforce User who "owns" the Payment Settings record.

Payment Queue Submission Count

Text (5)

This field is used to determine the number of Checks that will be submitted to the Check21.com Payment Gateway within each thread/group. Unless specifically told to change this value by a Check21.com Account Manager, please leave this field unfilled.

Payology Settings Name

Text (80)

Used to identify the Payment Setting Record. Please use "Default".

Send Check Validation Exceptions to C21

Checkbox

If enabled, this field in combination with any of the 4 different Conflict validations will ensure checks are sent for review by a Check21.com agent when necessary.

Use Fully Tokenized System

Checkbox

Although not yet available for use, this field, when enabled, will ensure that all sensitive data (i.e. account number, MICR, etc) will be stored solely in the Check21.com Payment Gateway and not within the Salesforce instance.

Next Steps

To continue the configuration process, Salesforce Administrators must generate/create Client Account (Bank Account) records. For detailed information on the Client Account creation process, please see the next section, labeled Client Account Configuration.