...

If it meets these criteria, a field and a button are added to the top of the page. By default, the value entered is the total of the order. You can enter a partial refund (therefore a lower amount) if necessary. On validation, a call to the axepta.capture service is made, and a transaction line is added. It will be either “PARTIAL REFUND” or “REFUND” depending on the amount.

Capture

As indicated previously, 3 capture modes are available :

• Auto

This capture mode does not require any action. The order is marked as “PAID”, and the various Axepta attributes relating to the capture are fulfilled. On the Axepta side, the transaction is automatically captured as soon as it is validated.

• With delay

This capture mode also has no action on the Axepta side (the order is captured by itself after the time period specified in the Site Preferences). However, for it to be up to date and marked as captured on SFCC, it is necessary to activate the Job Axepta - Update Delayed Captures . The job will run on orders with a capture date with an “expired” delay. On these, a call is made to verify the status of the payment, via the service axepta.inquire . Following the return, it performs actions similar to “Auto” mode (so flags the command as captured).

• Manual

This capture mode requires a call to the capture endpoint. These calls are managed by the Axepta - Capture Orders job. This job runs on Axepta orders having a “SHIPPED” status, and not being captured.

Testing

Unit tests

Integration tests

...