Working with Pay Types (WPAY)

Purpose: Use this option to configure payment methods for External Payment Service Credit Card and Stored Value Cards, Customer Engagement Stored Value Cards, PayPal, Cash/Check and Generic payments used for processes like retail pickup and delivery orders. The following processes are available:

add or maintain these payment methods and their descriptions
specify an alternate refund pay type if your company allows you to change the method by which you refund the customer
indicate the minimum dollar value and the maximum dollar amounts for which your company will produce a refund
specify the characteristics of credit cards that your company accepts as a method of payment including the limits, if any, for reauthorizing a credit card order and the authorization and deposit services
specify the financial conditions under which an order will go on hold (for example, dollar amount limits, balance due)
specify the cross-reference for a ChannelAdvisor marketplace, so that orders originating in that marketplace are assigned the matching payment method, and specify whether to calculate tax and shipping at the item level or the order level.

Important:

Use the Payment Configurations option in Modern View to configure or work with any payment processing through EFTConnect. You would use Work with Pay Types in Classic View only for other authorization services, such as for stored value cards (gift cards). You cannot create, change, or delete a pay type that uses EFTConnect through the Work with Pay Type option in Classic View.

Pay type versus pay category: A pay type defines a specific method of payment such as check, cash, Visa, Mastercard, American Express, etc. Each pay type is assigned to a pay category.

Valid pay categories are:

Cash/Check
Credit Card (including stored value card, debit card and wallet)

Charging against pay types: When billing each pay type on a multi-paytype order, the system automatically assigns charge sequences to different payment categories as follows:

Payment Method	Pay Category	Default Charge Sequence
Cash or check	Cash/Check	1
Online Banking	Credit Card	2
Stored Value Card (non-catchall)	Credit Card	3
Credit Card (any Card type besides a stored value card and Online Banking) (non-catchall)	Credit Card	4
Stored Value Card (Catchall)	Credit Card	5
Credit Card (Catchall)	Credit Card	6

In addition, the system assigns the charge sequence for the “catch-all” payment method the highest charge sequence. For example, if the charge sequence for a check is 10, the system updates the charge sequence for the credit card on the order to 11 (provided the credit card is the “catch-all”).

In this topic:

Work with Pay Types Screen

How to display this screen: Enter WPAY in the Fast path field at the top of any menu or select Work with Pay Types from a menu.

The pay types listed may not all be available when adding a new payment method through Modern View Add Payment screens. An EFTConnect payment method can be restricted through the Payment Configuration option in Modern View. Also, PayPal and Wallets are not available to be added as a new form of payment on an order.

Field	Description
Type	A code that represents the pay type. Numeric, 2 positions; optional.
Description	The description of the pay type. Alphanumeric, 30 positions; optional.
Category	A code for a category of pay type. Valid values: Cash/Check Credit Card (including stored value card, debit card and wallet) Optional.

Field

Description

Type

A code that represents the pay type.

Numeric, 2 positions; optional.

Description

The description of the pay type.

Alphanumeric, 30 positions; optional.

Category

A code for a category of pay type.

Valid values:

Cash/Check
Credit Card (including stored value card, debit card and wallet)

Optional.

Screen Option	Procedure
Create a pay type code	Select Create to advance to the Create Pay Type Screen. You can create only cash/check, stored value card or credit cards through this screen when not connected to an EFTConnect merchant account. Use the Payment Configurations option in Modern View to create credit card, debit card, or wallet pay types for EFTConnect payment processing.
Change pay type information	Select Change for a pay type to advance to the Change Pay Type screen. At this screen you can change any information except the pay type code. See the Create Pay Type Screen for field descriptions. You can change only cash/check, stored value card or credit cards through this screen when not connected to an EFTConnect merchant account. Use the Payment Configurations option in Modern View to change credit card, debit card, or wallet pay types for EFTConnect payment processing.
Delete pay type information	Select Delete for a pay type to delete it. You can delete only cash/check, stored value card or credit cards through this screen when not connected to an EFTConnect merchant account. Use the Payment Configurations option in Modern View to delete credit card, debit card, or wallet pay types for EFTConnect payment processing.
Display pay type information	Select Display for a pay type to advance to the Display Pay Type screen. You can display any pay type; however, you cannot update any information on this screen. See Create Pay Type Screen for field descriptions. Settings configured through the Payment Configurations option in Modern View for credit card, debit card, or wallet pay types for EFTConnect payment processing will be displayed here.
Work with credit card number format	Select Card Number Format for a Credit Card pay category pay type to advance to the Card Number Format. An error message indicates if the pay type is not a Credit Card pay category pay type: `Not available for this pay type.`
Work with user defined fields	Select User Field for a pay type to advance to the Work with User Fields Screen.

Create Pay Type Screen

Purpose: Use this screen to create a cash/check, stored value card (gift card) and credit card pay types that are not connected to an EFTConnect merchant account.

Create EFTConnect payment methods only through the Payment Configuration option in Modern View. Details about the payment method will be available for display only in the display screen.

How to display this screen: At the Work with Pay Types Screen, select Create.

Field	Description
Pay type	A code that represents a pay type, such as a check, credit card, online banking, or stored value card. Numeric, 2 positions. Create screen: required. Change screen: display-only.
Desc (Description)	The description of the pay type. Alphanumeric, 30 positions; required.
Category	The category of the pay type. Valid values are: Cash/Check Credit Card (including stored value card, debit card and wallet) Required.
Alt refund type (Alternate refund type)	The pay type to use for refunds to this pay type. Complete this field only if the pay type for refunds is different from the pay type used on the order. The system checks the appropriate values defined for the alternate refund pay type, not the original pay type, when generating refunds. The alternate refund type must be a pay category of Cash/Check or Stored Value Card for Card type Stored Value. The system displays an error message if you enter an invalid alternate refund type: `Only SVC pay type OR alt pay category of Cash/Check allowed.` Numeric, 2 positions; optional.
Alt refund category (Alternate refund category)	The pay category to which the system-generated refund can be charged during refund maintenance. Valid values are: Cash/Check Credit Card (stored value card) When you define an alternate refund category for a pay type, you give yourself the option of changing the refund to the type that corresponds to this category. The alternate refund category must be a pay category of Cash/Check. Optional.
Authorization service	A code for the service bureau that authorizes or declines credit card charges. Defined through the Work with Authorization Services (WASV) screen. Only PayPal (PPL), Customer Engagement (RLT) or External Payment Service records should be entered here. EFTConnect payment methods should only be configured through the Payment Configuration option in Modern View. Alphanumeric, 3 positions; optional.
Credit card length	The required length of the stored value card number or any credit card pay type without an authorization or deposit service defined. You can require any length up to 20 positions. If the card entered does not match this length, you will receive an error message when trying to use this form of payment. Note: The system does not validate the credit card length if you enter a 0 in this field. Numeric, 2 positions; optional.
Deposit service	A code for the service bureau that performs stored value card deposits for this pay type. Defined through the Work with Authorization Services (WASV) screen. Only PayPal (PPL), Customer Engagement (RLT) or External Payment Service records should be entered here. EFTConnect payment methods should only be configured through the Payment Configuration option in Modern View. Alphanumeric, 3 positions; optional.
Leading digits	The first digits of a valid stored value card number or any credit card pay type without an authorization or deposit service defined. You can enter up to 4 leading digits. If the card entered does not match these leading digits, you will receive an error message when trying to use this form of payment. Numeric, 4 positions; optional.
Reauthorization days	The number of days before an authorization expires. Note: If online authorization is enabled, you should specify this number of days for a payment method in order to prevent repeated, unnecessary authorization requests. If this field is blank for a stored value card or credit card pay type, the authorization expires immediately. Also, if the order is submitted to Order Orchestration for fulfillment, there will be unsuccessful authorization attempts. The REAUTH periodic function uses this date to determine when to attempt to reauthorize an expired authorization. Only pay types that have this field set to a number greater than 0 are eligible for reauthorization attempts. Numeric, 3 positions; optional.
Modulus check	This setting indicates if the system performs a calculation against the digits of the stored card number, or any credit card pay type without an authorization or deposit service defined, to ensure that the card is valid. Valid values are: Modulus 10 = for a modulus 10 check Modulus 11 = for a modulus 11 check Modulus User Defined = Not implemented blank = no modulus check is performed Note: The system cannot perform a modulus check against the number if the number includes spaces; for example: 4111 1111 1111 1111. To perform a modulus check, you must enter the number without any spaces between the numbers; for example: 4111111111111111. Optional.
Require start date	Indicates whether to require a start date when the customer uses this stored value card pay type, or any credit card pay type without an authorization or deposit service defined. For example, you might use a start date for a stored value card to indicate the first date when the card is effective. Select this flag if you want to require a start date for this pay type in Modern View Add Payment screens. This is a valid selection only if the pay type is a stored value card. Do not select this field if you do not want to require a start date for the pay type. Note: Even if you require a start date for a pay type, the system does not validate the card based on whether the start date is before or after the current date. Typically, if your authorization service requires a start date for this pay type, the service would validate the start date provided against the current date.
Card type	Indicates the type of card — Credit Card, Debit Card, Stored Value or Wallet. See Stored Value Card Overview and Setup. You cannot enter a card type for a cash/check pay type. Wallet is not available through create or change, only display.
Require expiration date	Indicates whether to require an expiration date when the customer uses this stored value card pay type. If an expiration date is required but not entered, the system displays an error message in order entry or maintenance: `Credit card expiration date (0) is not valid.` The expiration date is a four-position date in MMYY format. Select this flag if you want to require an expiration date for this stored value card pay type. Leave this field blank if you do not want to require an expiration date for the pay type.
Require issue #	Indicates whether to require an issue number when the customer uses this stored value card pay type or any credit card pay type without an authorization or deposit service defined. Some banks assign an incremental issue number when they replace a card because it is lost or stolen. Select this flag if you want to require an issue number for this pay type. Do not select this flag if you do not want to require an issue number for the pay type. If an issue number is required but not entered in order entry or order maintenance, the system displays an error message: `Credit card issue# () is not valid.` Note: Debit cards might require a start date, an issue number, both, or neither. Even if a start date or an issue date are not required, you can still enter this information in order entry if it is available.
Notify of installments	CyberSource: Indicates whether to send a `commerceIndicator` set to `install` in the subsequent authorization and deposit request to CyberSource for an order using a deferred or installment pay plan, or to have the information passed in the `ccAuthService` element similar to other subsequent authorizations, such as a split shipment. Important: To determine how to set this flag if you offer deferred or installment billing and use CyberSource, you need to confirm the information that the end processor requires for deferred or installment payment plans for each payment type. Possible settings are: Selected = The `commerceIndicator` is set to `install` in the authorization and deposit request, and no `subsequentAuthReason, subsequentAuthStoredCredential`, or `subsequentAuthOriginalAmount` is passed. Unselected (default) = The authorization and deposit request includes the `commerceIndicator` set to either `moto` or `internet`, based on where the order originated, and also includes the `subsequentAuthReason, subsequentAuthStoredCredential`, and `subsequentAuthOriginalAmount`, similar to the request for a split shipment. External Payment Service: Indicates whether to send a `subsequentAuthReason` of INSTALLMENT in the subsequent authorization request for an order using a deferred or installment pay plan. For External Payment Service: Selected = The `subsequentAuthReason` is set to `INSTALLMENT` in the authorization request. Unselected (default) = The `subsequentAuthReason` is set to either `REAUTH`, similar to the request for a split shipment. For more information: See: Subsequent Authorization Requests to CyberSource Subsequent Authorization Requests through the External Payment Service Deferred/Installment Billing Overview Note: You need to verify that the end processor supports the selected option.
Bal due $ limit (Balance due dollar limit)	If a customer short pays an order by an amount equal to or greater than this amount, the system places the order automatically on BD (Balance Due) hold. Note: Orders are evaluated for Bal due $ limit (Balance due dollar limit) and Bal due % limit (Balance due percentage limit). Balance due % limit takes precedence over balance due $ limit, so the system puts the order on hold when it is underpaid by the percentage even if it not underpaid by the dollar amount. When you apply a cash/check payment method: If there is a Bal due % limit specified, and the order is underpaid by this percentage, put the order on hold; otherwise, If there is a Bal due $ limit specified, and the order is underpaid by this amount, put the order on hold; otherwise, Do not put the order on hold for an underpayment. Example: A customer underpays a $1,250.00 order by $25.00. The Balance due $ limit is $5.00; however, the Balance due % limit is 5%. Five percent of this order is $62.50. This order will not go on hold. The customer has underpaid by more than the Balance due $ limit but less than the Balance due % limit. Note: If the underpaid amount is less than the amount specified here (and there is no Bal due % limit specified), the order does not go on hold. The system creates a balance due record (negative refund record) and puts this record into a write-off pending status. Numeric, 13 positions with a 2-place decimal; optional.
Order $ limit (Order dollar limit)	If the order total meets or exceeds this dollar amount, the system places the order on dollar hold, regardless of the pay category (cash/check or credit card). Multi-pay orders: If there is more than one payment method on the order, the system places the order on hold if the order total meets or exceeds the Order $ limit for any pay type. Example: The order total is $200.00, and the customer sends a $50.00 check and puts the balance on a credit card. The Order $ limit for the check pay type is $150.00, and the Order $ limit for the credit card is $250.00. The system places the order on hold, because the order total of $200.00 meets or exceeds the Order $ limit of $150.00 for the check pay type (even though the check payment amount is less than the Order $ limit). Cash/check orders: The system evaluates both Order $ limit and Hold days. Order $ limit takes priority over Hold days. Example: The order total is $350.00 and the customer pays by check. Order $ limit is $225.00; Hold days is 5. Six days pass; this order will still be on hold. This customer order meets the value specified in Hold days but still exceeds the Order $ limit specified in this table. The system does not check this setting if the order is already on any type of system hold. Numeric, 13 positions with a 2-place decimal; optional.
Bal due % limit (Balance due percentage limit)	If a customer underpays on an order by a percentage equal to or greater than this amount, the system places the order on hold. Note: Orders are evaluated for both Bal due $ limit (Balance due dollar limit) and Balance due % limit. Balance due % limit takes priority over balance due $ limit. See the Bal due $ limit (Balance due dollar limit) for a discussion. Numeric, 13 positions with a 2-place decimal; optional.
Hold days	The number of days to hold an order while waiting for a check to clear the bank. The system releases the order from hold automatically through Daily Periodic Processing once the number specified here has passed. Note: Cash/check orders are evaluated for both Order $ limit (Order dollar limit) and Hold days. Order $ limit takes priority over Hold days. Numeric, 3 positions; optional.
Ref chk min (Refund check minimum)	The minimum dollar amount for which you issue a refund. Refunds less than this amount are put in a write-off pending status. These write-off amounts accumulate in the Customer Sold-to table and can be used as an order credit on a subsequent order. If a pay type has an alternate refund type, the system checks the refund check minimum for the alternate refund type. Numeric, 13 positions with a 2-place decimal; optional.
Ref chk max (Refund check maximum)	The maximum dollar amount for automatic refund creation. Any refund exceeding this dollar amount is put on hold. For example, if you leave this field blank for a credit card alternate refund type, all refunds will go on hold because they exceed the blank (zero) amount. If a pay type has an alternate refund type, the system checks the refund check minimum for the alternate refund type. Numeric, 13 positions with a 2-place decimal; optional.
Release days	The number of days to hold a refund from processing. The system changes the status of the refund to “open” when you process the refund if the release days have passed. This feature ensures that the customer's check for the order clears before you print a refund check for the overpayment. If a pay type has an alternate refund type, the system checks the refund check minimum for the alternate refund type. Numeric, 3 positions; optional.
Store tender	A cross-reference to the corresponding tender code in a point-of-sale system. This field is available only if you specify a Default Location for ORCE Integration (K69). This code is passed in the POSLog integration to Customer Engagement as the tender ID, which can be used as a loyalty qualifier. Alphanumeric, 4 positions; optional.
CA cross reference #	A cross-reference to a ChannelAdvisor marketplace, set up through Work with ChannelAdvisor Offers Screen, from which you receive orders: If the CAORDUP periodic function creates an order from ChannelAdvisor, and the `ItemSaleSource` passed for the order matches this cross-reference, the periodic function assigns this payment method to the order. Your marketplace needs to match a ChannelAdvisor Site Token value. If an order has a payment method whose cross-reference matches a ChannelAdvisor marketplace and also matches the ChannelAdvisor Order Type (L90), the Processing Refunds (MREF) option submits any pending refunds for the order to ChannelAdvisor, and does not actually generate the refund. If more than one pay type has the same matching cross-reference, the periodic function selects the pay type with the highest pay type code. Cash/check category: If a CA cross reference # is specified, the pay type Category must be Cash/Check. See ChannelAdvisor Integration Overview and ChannelAdvisor Setup. This field is available only if the ChannelAdvisor Order Type (L90) system control value specifies an order type. If you enter a value in this field, then the CA type field is required. Alphanumeric, 40 positions; optional.
CA type	Controls how the CAORDUP periodic function calculates shipping and tax, and how refund amounts are passed when Submitting Refunds for ChannelAdvisor Orders. If this field is set to: Item Level or blank = Consistent with the Amazon and eBay with premium tax marketplaces: the CAORDUP periodic function calculates shipping and tax based on the amounts in the OrderLineItemItem element refund processing calculates tax and shipping at the item level and passes these amounts in the RefundItem level in the SubmitOrderRefund message Order Level = Consistent with the eBay marketplace (without premium tax): the CAORDUP periodic function uses the tax and shipping amounts from the OrderLineItemInvoice element and prorates them across the lines on the order the SubmitOrderRefund message specifies amounts at the order level This field is available only if the ChannelAdvisor Order Type (L90) system control value specifies an order type. If a CA cross reference # is specified for the pay type, then this field is required.

Card Number Format

Card Number Format is not currently implemented.