Payment Request Combination Edit on Classic page vs. Fluid page

My client wants to use the Classic Payment Request page rather than Fluid because of the page layout and drop down boxes.  We have been testing and a combination edit is popping up on the Classic page that does not happen on the Fluid page.  The Combination Edit is valid and should pass on both the Classic and Fluid pages.  I ran a Trace file and comparing the steps and see Combination Edits being invoked on the Fluid page but not the Classic.  The Payment Request template requires Edit Combinations.  I have run the Voucher Build for the Fluid Payment