Can we not create dynamic button headers on payment screen using entity data?
Apparently not 
Entity Screen Automation Command Buttons support that type of dynamic Caption, but I doubt an Automation Command Header supports that, as you can see is the case.
That sucks 
Should be entity aware for payment buttons for account etc and shows entities on order list header.
I don’t think it has anything to do with the Payment Screen at all. It is the Automation Command Header field that does not support Tags.
It does though, look at second screenshot on menu/ticket screen… its the same button mapped to ticket & payment screen positions.
Also my last 3 tutorials heavily used the tags in automation command headings.
I stand corrected! 
Guess it is and oversight/omission on the Payment Screen then?
@emre know your busy but am I missing something here?
Will check pauline’s crazy setup as he must have hit this… maybe, but couldn’t see when searching.
Ah Yes… I implemented a ACM button like a “Fast Payment Cash” button but used the button to convert POINTS to ACCOUNT. Once they are on the Customers Account then they can use them at the Payments Screen by selected Account.
What you trying to do probably could be simulated using my processed in 1 step - i.e. instead of converting if they press USE POINTS from the Ticket screen you automatically convert it onto their Account then it just shows as a higher available credit. Downside of course is not pulling out…