The PR of @Vogeslu make me rethink how the Api/Key class have to be used and maybe have to be renamed. I'm thinking about getting dedicated Api classes for each gateway factories like this :
StripeCheckoutSession :
FluxSE\PayumStripe\Api\StripeCheckoutSessionApi
using traits :
FluxSE\PayumStripe\Api\KeysAwareTrait
FluxSE\PayumStripe\Api\AuthorizeApiAwareTrait
Finally add getter/setter for payment_method_types or a dedicated trait
StripeJs :
FluxSE\PayumStripe\Api\StripeJsApi extends FluxSE\PayumStripe\Api\AbstractStripeKeys
using trait FluxSE\PayumStripe\Api\AuthorizeApiAwareTrait
The PR of @Vogeslu make me rethink how the
Api/Key
class have to be used and maybe have to be renamed. I'm thinking about getting dedicatedApi
classes for each gateway factories like this :FluxSE\PayumStripe\Api\StripeCheckoutSessionApi
using traits :FluxSE\PayumStripe\Api\KeysAwareTrait
FluxSE\PayumStripe\Api\AuthorizeApiAwareTrait
Finally add getter/setter forpayment_method_types
or a dedicated traitFluxSE\PayumStripe\Api\StripeJsApi
extendsFluxSE\PayumStripe\Api\AbstractStripeKeys
using traitFluxSE\PayumStripe\Api\AuthorizeApiAwareTrait