Payment returns
This is done in via the payment add-ons.
Payment returns will be implemented in the existing payment provider add-ons.
Refunds
It is possible to refund part of a captured amount. When an SRO is created, the payment will initially be in Paidstate. It has to be changed to Returned, either by API action or via the UI. The exact refund amount will be limited by the amount captured for a transaction, and other limitations imposed by specific payment providers. If a refund fails, the payment will be in ReturnFailedstate, and StateLogwill contain the necessary information about the failure. (See entity model below)
Capture and cancel
It is possible to capture part of the amount and cancel the remaining amount of a reservation. This facilitates B2B scenarios, where the capture may be performed after customer acceptance of the delivery. This allows the return of orders that have not yet been captured, which means that payment has not yet been charged to the customer’s account. When an SRO is created, the payment will initially be created in Reservedstatus. This status should be set to Cancelled, either by API action or via the UI.
Multiple payments and gift cards
In case a given order has been fulfilled by multiple payments, the refund can only be processed up to the actual captured amount from each payment transaction.
Gift card payments have not yet been implemented in Litium. Custom implementations should be done in the same way as for an ordinary payment provider. Then it will be possible to treat gift cards in the same way as other payments.