Announcement

Collapse
No announcement yet.

Display Payment Method on Confirmation Email Not Working Anymore

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Display Payment Method on Confirmation Email Not Working Anymore

    I used to display the payment method in the merchant and customer confirmation email using the below token


    Code:
    <mvt:foreach iterator="payment" array="order:payments">
    <strong>&mvt:payment:desc;</strong>
    </mvt:foreach>


    Since upgrading to Miva 10 it no longer displays the payment method. Displaying the type of payment method is important to us as we use Purchase Orders for our Wholesale Customers and we need to see it in the confirmation emails.

    Any advice is appreciated.

    Thanks
    Keyboard Not Found..... Press F1 to continue

    #2
    What Purchase Order module is the store using?

    When using the Version 10 built in Purchase Order/Terms module the variable you are looking for is still available and reads 'Purchase Order' when an order is using the payment method.

    Nicholas Adkins
    Technical Training Specialist / Miva, Inc.
    [email protected]
    https://www.miva.com/mivalearn

    Comment


      #3
      Hi Nick,

      Thanks for replying, we have been using https://apps.miva.com/purchase-order-plus.html for a very long time and works perfectly for us. We are not only looking to display just "Purchase Order" payment method but also display the type of card used like Visa, Mastercard etc.

      Using the above token I have listed in the initial post we were able to say Payment Method : Visa or Purchase Order.

      Is this still possible in Miva 10.

      Thanks again
      Keyboard Not Found..... Press F1 to continue

      Comment


        #4
        That variable is still available in the order:payments array for Version 10. I installed the purchase order plus module on my development store to test if the variable was available and the output was Purchase Order.

        Could there be something that is overwriting the variable?
        Nicholas Adkins
        Technical Training Specialist / Miva, Inc.
        [email protected]
        https://www.miva.com/mivalearn

        Comment


          #5
          I am having a similar problem. Is
          Code:
          &mvt:payment:desc;
          still valid? I don't see it in the variable list.
          Highly caffeinated
          http://www.coffeehouseexpress.com

          Comment


            #6
            This happened to us also using Chase Paymentech. I don.'t know if it the same for you. Support says;

            The payment module name showing up on the INVC page and the order confirmation emails is a bug that is set to be fixed in version 10.02 (no known ETA).
            For now, the only solution is to comment out the payment description which I have done for the INVC page and both order confirmation emails.


            Comment


              #7
              Originally posted by greggc View Post
              This happened to us also using Chase Paymentech. I don.'t know if it the same for you. Support says;

              The payment module name showing up on the INVC page and the order confirmation emails is a bug that is set to be fixed in version 10.02 (no known ETA).
              For now, the only solution is to comment out the payment description which I have done for the INVC page and both order confirmation emails.

              Thanks for the info!
              Highly caffeinated
              http://www.coffeehouseexpress.com

              Comment


                #8
                Can anyone confirm if this is also the case for the Braintree and Amazon Pay payment modules?

                Haven't installed the Miva update yet and may wait until 10.01.02 is available.
                Last edited by SidFeyDesigns; 07-21-21, 11:27 AM.

                Comment


                  #9
                  Let me add my voice to the choir. I had a little bit of code finally sorted to show payment method but seems to have broken with the update today. Old code that worked.

                  Code:
                  <mvt:item name="ry_toolbelt" param="availgroup|Customer_Find|g.terms_customer|' OnAccount'" />
                  Payment Method:&nbsp;
                  <mvt:foreach iterator="payment" array="order:payments">
                  <mvt:if expr="NOT('COD' CIN l.settings:payment:desc)">
                  &mvt:payment:desc;
                  <mvt:elseif expr="g.terms_customer">
                  On Account
                  <mvt:elseif expr="'quote' CIN l.settings:order:pay_data">Quote
                  </mvt:if>
                  </mvt:foreach>
                  The l.settings:payment:desc just comes back with CHASE Paymentech Orbital Gateway and looks like I'm not getting anything from l.settings:order:pay_data.

                  Comment


                    #10
                    And support says no ETA on the fix. Fix it now I say.

                    Comment


                      #11
                      That's because of two things:

                      First it's not really a bug (I know I sound pedantic) but we moved where data is stored and this was an unintended outcome, but technologically it's still working exactly the same. So there is no way to "fix" the bug since for security and other reasons we can't revert to how we stored the data before.

                      Thus now we have to add a feature (a small one overall) which is slightly more work than undoing something.

                      Second, we don't ever give ETA's so you could ask support anything and the answer should universally be no ETA (since that is corporate policy).

                      I can assure you we're aware and working on a solution.
                      Thanks,

                      Rick Wilson
                      CEO
                      Miva, Inc.
                      [email protected]
                      https://www.miva.com

                      Comment


                        #12
                        Just upgraded Miva and this does not appear to be an issue with the Braintree payment module.

                        Just thought I would share.

                        Comment


                          #13
                          It only impacted a couple modules, Auth.net being the "big one"
                          Thanks,

                          Rick Wilson
                          CEO
                          Miva, Inc.
                          [email protected]
                          https://www.miva.com

                          Comment


                            #14
                            Our client has found the same issue with the Authorize.net text appearing in place of the credit card type. I have commented out the description code for now and we're looking forward to the update.

                            Comment


                              #15
                              Does this update in 10.02 mean that the payment methods can now be made available on the confirmation emails? If so can anyone share the variables that worked?

                              "Authorize.net & Chase Paymentech modules now correctly display the card type used on Invoice and in confirmation emails"

                              Comment

                              Working...
                              X