Answers.Body: <p>The error messages are returned to the template as flash messages.</p>
  
  <p>Handling those is documented here:
  <a href="https://craftcms.com/docs/templating/craft.session" rel="noreferrer">https://craftcms.com/docs/templating/craft.session</a></p>
  
  <p>One thing to watch out for is that flash messages are only available once, and are by default 'consumed' when you retrieve them:</p>
  
  <pre><code>{{ craft.session.getFlashes() }}
  ...some other template code here....
  {{ craft.session.getFlashes() }}
  </code></pre>
  
  <p>...if there is a message, the first tag will output it, but the second one won't as it has been consumed.  So best to set the message to a variable if you want to save it, or you can call <code>craft.session.getFlashes(false)</code> to stop the message from being consumed if you'll want to use it later in your template.</p>
  
  <p>During development it is worth having some code to always display the flash messages at the top or bottom of your main layout template, so you can see them as they are occurring, and thus anticipate what you might need to handle.  I use something like this:</p>
  
  <pre><code>    {% if craft.config.devMode and (craft.session.hasFlash('notice') or craft.session.hasFlash('error')) %}
  
      {% set noticeFlash = craft.session.getFlash('notice')|join('|') %}
      {% set errorFlash = craft.session.getFlash('error')|join('|') %}
  
      Notice: [{{  noticeFlash }}]
      Error: [{{  errorFlash }}]
  
      {% endif %}
  </code></pre>
  
  <p>Now, if you're doing your payment operations via ajax, things are a little different...that case you'll get back results in json.  If there is an error, it will look something like:</p>
  
  <pre><code>{"error":["Credit Card Invalid"]}
  </code></pre>
  
  <p>So in your js you would check for the lack of <code>response.success</code> and then look for this error message.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-09-03T06:09:59.003Z
Answers.LastActivityDate: 2016-09-03T06:09:59.003Z
Answers.UserDisplayName: Jeremy Daalder
Body: <p>When a payment is made and something is incorrect e.g. card number is invalid, expiry date is in the past etc. The form just refreshes with no warning / notification of what's happened.</p>
  
  <p>I've noticed that this message is stored in the CMS on each order, under the "Message" column (e.g. Card Has Expired)</p>
  
  <p>Is there a way to output this message in to the template when the error occurs? Even on the example templates it does this issue.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-09-05T04:46:16.417Z
Comments.Text: It's really just the "card has expired" message that's not bubbling up to the template here, correct?  Every other validation message I tried on the stock Commerce templates seems to be working O.K.
Comments.UserDisplayName: Brad Bell
Tags: <plugin-craftcommerce><payment-methods>
Title: Transaction Error Message in Template
ThreadText: # Transaction Error Message in Template
  
  (Asked by: username_0 on 2016-09-02)
  
  When a payment is made and something is incorrect e.g. card number is invalid, expiry date is in the past etc. The form just refreshes with no warning / notification of what's happened.
  
  I've noticed that this message is stored in the CMS on each order, under the "Message" column (e.g. Card Has Expired)
  
  Is there a way to output this message in to the template when the error occurs? Even on the example templates it does this issue.
  
  **Tags:** plugin-craftcommerce, payment-methods
  
  > **Comments:**
  > **username_1**: It's really just the "card has expired" message that's not bubbling up to the template here, correct?  Every other validation message I tried on the stock Commerce templates seems to be working O.K.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2016-09-03. Score: 6 | Accepted answer
  
  The error messages are returned to the template as flash messages.
  
  Handling those is documented here:
  <https://craftcms.com/docs/templating/craft.session>
  
  One thing to watch out for is that flash messages are only available once, and are by default 'consumed' when you retrieve them:
  
  ```
  {{ craft.session.getFlashes() }}
  ...some other template code here....
  {{ craft.session.getFlashes() }}
  
  ```
  
  ...if there is a message, the first tag will output it, but the second one won't as it has been consumed. So best to set the message to a variable if you want to save it, or you can call `craft.session.getFlashes(false)` to stop the message from being consumed if you'll want to use it later in your template.
  
  During development it is worth having some code to always display the flash messages at the top or bottom of your main layout template, so you can see them as they are occurring, and thus anticipate what you might need to handle. I use something like this:
  
  ```
      {% if craft.config.devMode and (craft.session.hasFlash('notice') or craft.session.hasFlash('error')) %}
  
      {% set noticeFlash = craft.session.getFlash('notice')|join('|') %}
      {% set errorFlash = craft.session.getFlash('error')|join('|') %}
  
      Notice: [{{  noticeFlash }}]
      Error: [{{  errorFlash }}]
  
      {% endif %}
  
  ```
  
  Now, if you're doing your payment operations via ajax, things are a little different...that case you'll get back results in json. If there is an error, it will look something like:
  
  ```
  {"error":["Credit Card Invalid"]}
  
  ```
  
  So in your js you would check for the lack of `response.success` and then look for this error message.
  
  
  ---
  
  