Open olia-bn opened 6 months ago
MethodsAction controller expects provided ID to be that of a GatewayConfig, but the template used that of the active resource (PaymentMethod ID)
There's no guarantee that PaymentMethod will always have the same ID as it's GatewayConfig
Hello @olia-bn,
Thank you for your suggestion, our team has reviewed your code and added it to our integration.
Please note that the changes will be live once we release a new module version.
Kind regards.
MethodsAction controller expects provided ID to be that of a GatewayConfig, but the template used that of the active resource (PaymentMethod ID)
There's no guarantee that PaymentMethod will always have the same ID as it's GatewayConfig