- Payment Processing must be installed, activated, and configured to use a Paya merchant account.
- Sage Exchange must be installed and running on the workstation you will use to enter the credit card information.
- You must have an active Internet connection.
For information about Payment Processing, Sage Exchange, and Paya, see the Payment Processing help.
Select this option if the customer has given you formal approval to charge the credit card automatically (without contacting the customer) when invoices are due.
Note: To use a credit card on the Process Credit Card Payments screen, both the Approved for Automatic Payments option and the Use This as Default Card option must be selected for the card.
This field displays the bank code for the bank associated with the selected processing code.
Enter a short code to identify the credit card. For example, you might use VISA for a customer's Visa card.
You can also use the Finder 
to select and open an existing credit card record.
Enter optional comments for the credit card.
Do not record any card details in the Comments field, including card number, expiration date, and CVV number. Storing details in this way can compromise credit card security and may constitute a violation of the Payment Card Industry Data Security Standard (PCI DSS).
If a security breach occurs, merchants that do not comply with PCI DSS may be subject to fines, card replacement costs, forensic audits, and other penalties.
This field displays the currency code for the currency associated with the selected processing code.
Enter a description of the card, such as Bank of America Visa.
This description appears beside the card ID in screens, tables, and lists, and makes it easier to identify and select a card for future transactions and inquiries.
Select this option to make the credit card unavailable for use.
This field displays the date of the last change made to the customer record. You do not make an entry in this field.
A processing code specifies the bank, currency, and merchant account that will be used to process transactions for a credit card.
If you use multiple processing codes, type or select a processing code in the Processing Code field. If you use a single processing code, this field is set to read-only and displays the processing code.
The bank and currency for the processing code you select appear in the Bank and Currency fields, and also on the Credit Card tab of the A/R Customers screen (in the table with the other details for the card).
Note: When you are processing a transaction for this credit card, if you select a bank or currency other than the one that was specified for this processing code, an error message informs you that the bank or currency does not match the one specified for the processing code.
Select this option to set the current card as the default credit card for the customer.
When you process a credit card transaction for the customer, this card is selected by default on the A/R Process Credit Card screen.
- If you use multicurrency accounting, the card will be used as the default only for transactions that are processed in the currency specified for the card.
- To use quick processing buttons to process credit card transactions for a customer, the customer must have a default credit card.
- To use a credit card on the Process Credit Card Payments screen, both the Approved for Automatic Payments option and the Use This as Default Card option must be selected for the card.
Enter the cardholder's address. When you process the transaction, Address Verification Service (AVS) checks the information in these fields against the information on record for the cardholder.
Enter the name of the person to whom the card was issued, as it appears on the card. If the cardholder has authorized an additional person to use the card, you can use that person's name.
When you process the transaction, Address Verification Service (AVS) checks the information in this field against the information on record for the cardholder.
Enter the name of the city. When you process the transaction, Address Verification Service (AVS) checks the information in this field against the information on record for the cardholder.
Enter the name of the country. When you process the transaction, Address Verification Service (AVS) checks the information in this field against the information on record for the cardholder.
Enter the name of the state or province. When you process the transaction, Address Verification Service (AVS) checks the information in this field against the information on record for the cardholder.
Select this option to fill in Billing Details fields with name and address information from the customer record. If necessary, you can change this information.
If you clear this option after selecting it, customer name and address information is cleared from Billing Details fields.
Enter the zip or postal code. When you process the transaction, Address Verification Service (AVS) checks the information in this field against the information on record for the cardholder.
This field displays the last four digits of the credit card used for the transaction, with the remaining digits replaced by Xs.
The card number is stored securely in Paya, and can be edited only in the Paya browser form (not in Sage 300).
Do not record any card details in the Comments field, including card number, expiration date, and CVV number. Storing details in this way can compromise credit card security and may constitute a violation of the Payment Card Industry Data Security Standard (PCI DSS).
If a security breach occurs, merchants that do not comply with PCI DSS may be subject to fines, card replacement costs, forensic audits, and other penalties.
This field displays the card type (for example, Visa), and cannot be edited in Sage 300.
The card type is set by Paya, and is determined by an automatic check performed against the card number.
This field displays the expiration date of the credit card used for the transaction, in the format MM/YY.
You specify the expiration date in the Paya browser form. You cannot edit this field in Sage 300.
Do not record any card details in the Comments field, including card number, expiration date, and CVV number. Storing details in this way can compromise credit card security and may constitute a violation of the Payment Card Industry Data Security Standard (PCI DSS).
If a security breach occurs, merchants that do not comply with PCI DSS may be subject to fines, card replacement costs, forensic audits, and other penalties.
Overview
If you use Payment Processing, you use this screen to add, edit, and delete general credit card information for a customer, including the card ID, description, currency, billing information, comments, and whether or not the card is the default for the customer. You do not record the card number or expiration date in the customer record.
Do not record any card details in the Comments field, including card number, expiration date, and CVV number. Storing details in this way can compromise credit card security and may constitute a violation of the Payment Card Industry Data Security Standard (PCI DSS).
If a security breach occurs, merchants that do not comply with PCI DSS may be subject to fines, card replacement costs, forensic audits, and other penalties.
For important information about how Accounts Receivable stores credit card information, see About Customer Credit Cards.