Payment types can be conditions for promotion. For example, “Use your American Express card and get 10% off.” When a merchandising user creates a promotion in the BCC, he or she can select as many payment types as necessary from the Tender Type menu.
Payment types that can be displayed when creating a promotion, such as creditCard, can also specify a variation, such as creditCard:Visa.
You can configure the payment types and the variations that are listed to the merchandising user using the DCS/config/atg/commerce/payment/PaymentTypeStringEnumProvider. The PaymentTypesStringEnumProvider uses the getResources and getCodes methods to return a list of strings of all supported payment types. The result is a generic type for each payment group, as well as a payment type for each variation of the group. By default, the system displays only generic types for selection when there are no variations available, but this can be configured differently.
Use thePaymenTypePresentationSetting property to configure the payment types that are displayed to the user:
genericAndVariations: Indicates that no payment types will be removed. Both ‘Any Credit Card’ and ‘Visa’ will be displayed.genericOnlyIfNoVariations: Default. The generic types will be included if no variation exists. For example, ‘Any Credit Card’ will be displayed only if there are no variations, such as ‘Visa.’genericOnly: This removes everything that is a variation. For example, the system will display ‘Any Credit Card’, but not ‘Visa.’
Important: If you add new payment types to your system, tender-based promotions must be updated by the merchandising user to include these new payment types.
For detailed information on tender-based promotions, refer to the Core Commerce Programming Guide.
