Which solution should the Architect implement?

An Adobe Commerce Architect needs to customize the workflow of a monthly installments payment extension. The extension is from a partner that is contracted with the default website PSR which has its own legacy extension (a module using deprecated payment method).

The installment payment partner manages only initializing a payment, and then hands the capture to be executed by the PSP. Once the amount is successfully captured, the PSP notifies the website through an IPN. The goal of the IPN is only to create an "invoice" and save the ‘capture information’ to be used later for refund requests through the PSP itself.

The Architect needs the most simple solution to capture the requested behavior without side effects.

Which solution should the Architect implement?
A . Add a plugin before the $invoice-> () and changes its input to prevent the call of the $payment-> capture()
B. Change the can_ capture attribute for the payment method under config.xml to be <can_capture>0</can_capture>
C. Declare a capture command with type
MagentopaymentGatewayCommandNullCommand for the payment method CommandPool in di.zm1

View Answer

Answer: C

Explanation:

The best solution for the Adobe Commerce Architect to implement in order to capture the requested behavior without side effects is to declare a capture command with type MagentopaymentGatewayCommandNullCommand for the payment method CommandPool in di.xml. This will allow the partner to initialize the payment and then hand the capture over to the PSP, while also preventing the website from calling the $payment->capture() method. It will also allow the PSP to notify the website through an IPN, which will create an "invoice" and save the ‘capture information’ to be used later for refund requests through the PSP itself.