Paypal Pro Quantities not showing correctly on PayPal Site

  • Profile Image
    kengreene
    Asked on February 12, 2018 at 01:09 PM

    Hello - 

    I see a forum post about this from 4 or 5 years ago but didn't see a solution.


    I am currently using PayPal pro integration to pay meal and registration fees for a conference. When someone selects a quantity of an item in PayPal pro, the quantity correctly posts to the jotform submission but in Paypal's web site - it shows as "quantity: 1" with the total amount charged instead of itemizing it.


    This is making book-keeping a little bit of a nightmare. Is there a way to fix this? 

  • Profile Image
    BDAVID
    Answered on February 12, 2018 at 01:47 PM

    Can you share a screenshot of what you are referring to? https://www.jotform.com/help/438-How-to-Post-Screenshots-to-Our-Support-Forum 

    Are you saying that if the user selects a quantity of 4, it displays as "quantity 1" anyways? 

    Also, if by "itemizing it" you mean that you would like to display the name of the product multiple times based on the quantity that was selected, that's not possible. It will simply show you the product name, and the quantity selected for that product.

  • Profile Image
    kengreene
    Answered on February 12, 2018 at 03:47 PM

    Sure thing. On Jotform - it shows the quantity as 3 meal cards and gives me a total. On Paypal, it only says quantity of 1 and doesn't specify what kind of meal card they got - just a total amount. 1518468380Jotform_01.png1518468447PayPal_01.png

  • Profile Image
    BDAVID
    Answered on February 12, 2018 at 04:09 PM

    Thanks for sharing the screenshot, I have reported this issue to our back-end team. You will be updated via this thread.

  • Profile Image
    kengreene
    Answered on February 21, 2018 at 02:44 PM

    Thank you. Has there been any update to this? 

  • Profile Image
    EltonCris
    Answered on February 21, 2018 at 03:29 PM

    Apologies but there is still no update about this. Rest assured you will be notified here once this is fixed.