Body: <p>This may be specific to some payment processors. i am observing it with authorize.net.</p>
  
  <p>Contribution page has 'credit card' and 'pay later' available as option, therefore the two payment methods are available as radio buttons. </p>
  
  <p>When the page is opened, no Credit Card / Billing fields are displayed.</p>
  
  <p>But, once an amount is selected, the Credit Card / Billing fields are displayed which results in users jumping down to fill those in, then getting an error telling them that 'payment method' needs to be chosen.</p>
  
  <p>IF a default value of 'amount' is set, then the Credit Card and Billing field show immediately. Which does not seem correct to me.</p>
  
  <p>UPDATE - this is an issue when using Dummy processor which ships with civi.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-07T14:29:04.117Z
Comments.Text: I've seen this too in our iATS testing - which payment processor is set to default - also plays a role; I think there may be a JIRA issue on it
Comments.UserDisplayName: KarinG - Semper IT
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-07T19:04:58.913Z
Comments.Text: Yes I concur that this relates to whether a payment processor is set to default, but i am not sure I agree if this is civi's way of saying 'credit card will always be set on the page' and therefore treats 'pay later' as the second choice. IMO 'payment method' should be able to be left with no default, and without seeing credit card fields.
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2017-08-07T20:43:15.800Z
Comments.Text: Agreed - it's completely non-intuitive. It has been on my radar - but focus has been more on getting monies, transactions, financial details right - all scenarios - so I've not been able to pay to much attention to this not so great GUI experience yet.
Comments.UserDisplayName: KarinG - Semper IT
Tags: <contribution-page><authorize.net>
Title: Why do Credit Card fields (and Billing fields) display before the PAYMENT METHOD is selected?
ThreadText: # Why do Credit Card fields (and Billing fields) display before the PAYMENT METHOD is selected?
  
  (Asked by: username_0 on 2017-07-16)
  
  This may be specific to some payment processors. i am observing it with authorize.net.
  
  Contribution page has 'credit card' and 'pay later' available as option, therefore the two payment methods are available as radio buttons.
  
  When the page is opened, no Credit Card / Billing fields are displayed.
  
  But, once an amount is selected, the Credit Card / Billing fields are displayed which results in users jumping down to fill those in, then getting an error telling them that 'payment method' needs to be chosen.
  
  IF a default value of 'amount' is set, then the Credit Card and Billing field show immediately. Which does not seem correct to me.
  
  UPDATE - this is an issue when using Dummy processor which ships with civi.
  
  **Tags:** contribution-page, authorize.net
  
  > **Comments:**
  > **username_1**: I've seen this too in our iATS testing - which payment processor is set to default - also plays a role; I think there may be a JIRA issue on it  
  > **username_0**: Yes I concur that this relates to whether a payment processor is set to default, but i am not sure I agree if this is civi's way of saying 'credit card will always be set on the page' and therefore treats 'pay later' as the second choice. IMO 'payment method' should be able to be left with no default, and without seeing credit card fields.  
  > **username_1**: Agreed - it's completely non-intuitive. It has been on my radar - but focus has been more on getting monies, transactions, financial details right - all scenarios - so I've not been able to pay to much attention to this not so great GUI experience yet.  
  
  ---
  
  ## 0 answers
  
  