BAM package is not calling the right plugin class
Problem: In this case, the customer observed a discrepancy between production and sandbox where different plugin classes being triggered when they click on the "Add Payment Method" button part of BAM (Billing Account Manager) package.
In the sandbox, for the BAM HPM payment page, the component name is given as PaymentPage instead of bam_paymentpage which is the correct one configured for BAM.
For using BAM you need to provide the component name registered for the payment page which is bam_paymentpage then only the classes mentioned here will get triggered.
After updating the component name field on Payment pages to bam_paymentpage the correct plugin class triggered.
If you found my answer helpful, please give me a kudo ↑
Help others find answers faster by accepting my post as a solution √