An Adobe Commerce developer is asked to create a new payment method for their project. This project has administrators who use the backend to manage customer information and occasionally place…

Question

Options

• AIn the module di.xml, there were no default 3DS verification types configured as a VirtualType.
• BIn the module config.xmi, the boolean value for can_capture was set to false.
• CIn the module config.xmi, the node can_use_internal was not set to true.

• A
  7% (2)
• B
  17% (5)
• C
  76% (22)

Explanation

Option C is correct because in Adobe Commerce, the can_use_internal node in config.xml specifically controls whether a payment method is available in the admin panel for internally-placed orders. Since it defaults to false when omitted, the method will appear on the frontend checkout but remain invisible to administrators - exactly the symptom described.

Option B is wrong because can_capture determines whether the payment method supports capturing funds (e.g., after authorization), not where the method appears in the UI; setting it to false would affect capture functionality, not admin visibility.

Option A is wrong because 3DS verification VirtualTypes in di.xml relate to strong customer authentication configuration, which has no bearing on which sales contexts (frontend vs. admin) a payment method is displayed in.

Memory tip: Think of can_use_internal as "can be used internally by staff." Frontend customers are external, admins are internal - if you want your payment method available to internal admin users, you must explicitly enable can_use_internal.

No community discussion yet for this question.