Feedback

  • Contents
 

Add Credit Card Payments Permission

Use the Add Credit Card Payments permission to specify whether users can add credit card information and credit card payments.

Location

In the Latitude Permissions and Policies Editor window, expand the Credit Cards folder and then click Add Credit Card Payments.

Scope

This permission is available for all scopes.

Policy

This policy allows your organization to specify the business rules to enforce when a user adds credit card payments. Enable the permission for a scope and then specify the settings.

Note: If using the Override Rules option, the supervisor's rules are in effect for the current promise instead of the user's rules. 

  • User is not required to observe customer business rules: If selected, credit card settings applied to a user, role, or desk scope take precedence over settings applied for a customer or customer group scope (system doesn't enforce customer policies).

The following settings apply for the first PDC item in a series.

  • Minimum Payment Amount and Minimum Balance Percent: Minimum amount for the credit card payment. This value is a specific monetary amount or a percentage of the current balance of the account. The system requires the higher of the two values for the first item. If the current balance of the account is less than this amount, the current payment equals the balance.

  • Maximum Days to Payment: Number of days into the future that a user can post-date the first credit card payment.

  • The following settings apply to other items in a series.

  • Maximum Payments: Maximum number of credit card payments (up to 250) that a user can include in the series.

Note: If you are upgrading to Latitude 10.0 SU 8, ensure that this value is greater than 0 (zero) or you cannot create a payment arrangement.

  • Minimum Subsequent Payment Amount: Minimum dollar amount for subsequent payments. This value is a specific monetary amount. If the current balance of the account minus the value of the other items is less than this amount, the payment equals the minimum amount.

  • Maximum Days Between Payments: Maximum number of days between payments in the series.

  • Maximum Days to Last Payment: Maximum number of days into the future from the current date that the user can create the last payment in the series.

  • Allow user to enter settlement arrangement for less than the customer blanket settlement: If selected, the user does not need to meet blanket settlement percentage requirements when creating a settlement promise amount.

  • Only Debit Cards Accepted: If selected, your organization accepts debit cards for payments but not credit cards. If cleared, your organization accepts debit and credit cards. For more information, see Bank Identification Number.

  • Accepted Credit Cards: Credit cards available for selection when creating payments.

  • Validate card number using Luhn 10 formula: If selected, the system validates credit card numbers to meet the correct check-digit format; otherwise, the system doesn't allow payment entry.

  • Require credit card security code: If selected, the system requires the credit card security code to save a credit card post-dated transaction.