...

6. The merchant can verify the information in the Axepta Extranet Platform

Limitations, Constraints

• The merchant needs a configured Axepta account

• The following features are out of scope:

                      -  Multi-authorization

                      -  Multi-capture

                      -  Void

                      - N-times payment

                      - Direct Link payments

Axepta cartridge is developed based on en_US locale but it can be configured in any locale needed. Also, the cartridge doesn’t perform any request of PCI sensitive information

Compatibility

Axepta integration cartridge was certified with the version of Salesforce Commerce Cloud : currently API version 22.10, Site Genesis version 104.1.3 and SFRA version 5.3.0. It is typically backward compatible with older versions since it uses common and stable methods accessing the Customer, Order and Payment system objects. Currently, SFRA version 6.x and above are not supported.

Image Added

FLOA PAY : General Information

FLOA Pay allows a merchant to offer 3X, 4X, 1XD or 3XD installment plans for customers during checkout. During the first step FLOA Pay checks the customer for eligibility for chosen installment. Then, in case of positive result, FLOA Pay redirects the customer to FLOA Pay Hosted Payment page. A merchant can be configured on FLOA Pay side for AUTO Capture or for MANUAL Capture. In case of AUTO Capture, FLOA Pay does not expect capture from the merchant. FLOA Pay does capture automatically based on the authorization. In case of MANUAL Capture, the merchant needs to call Capture API. After a credit check, FLOA Pay assumes the entire customer's payment default risk for each transaction. The merchant receives full amount of the installment from FLOA Pay after capture.

Configuration

Axepta Floa 1

...