- Issue created by @zaporylie
Payments can be reusable in different contexts. Two major contexts that are very well documented are Merchant Initiated Transation (MIT) and Customer Initiated Transaction (CIT). Some gateways do not distinguish between the two but some others do. An example of a payment gateway that does care about that is Stripe - one can set up intent to be used for off-session (MIT) or on-session (CIT) type of transactions.
In 📌 Add checkout settings for payment method behavior Needs review we are discussing the ability of customers and merchants to set a reusability context per payment method but we don't really have a mechanism for storing reusability context. Therefore other modules, such as commerce recurring, don't know whether the payment method is valid for their use-case. In the mentioned example of Commerce Recurring the payment method will have to be categorized as off-session/MIT so that the recurring framework can initiate payments without customer's attention.
It is important that the list of available payment options, including these options that feature payment methods to be created, should be limited only to feature payment options with the correct reusability context.
Currently, none of this is possible as:
- we don't know if the newly created payment method will be reusable
- we have no way of specifying the payment method's reusability context
- we may however introduce on-demand change to the context as part of
📌
Add checkout settings for payment method behavior
Needs review
Active
3.0
Payment