Here is some reason, why using one PaymentInput control is more comfortable for me (Of course it depends on situation and client):

1. Situation where I would like implement funkcionality based on special workflow - generation all PaymentMethodFields controls depended on (customerAirline) workflow settings and transforming by one XSLT file seems as prefferable solution for me.
(If will be time I would like write some little post about creating Customer Workflow settings with real experiences)

2. There will be only one Post back event delegate, and during post back I have all information at once. I don’t need implement special cross control field validation, if customer preffer one payment before another (and my customer is very demanding).

Thanks again for this post. I am looking forward for next.