paypal payer information + address data in separate fields / excel row

  • Profile Image
    Heeschen
    Asked on March 11, 2011 at 01:22 AM

    Hi Jotform team,

    it is great to have paypal payer information available now.

    As it is valuable infomation which i have to use e.g. for shipment

    it would be nice to have this information ( e.g. name, zip, town and the others)

    available as an own excel row / field

    and not only all of the information in the "paypal-field" like it is now.

    Please make this information available as separate fields.

    That would make my life much easier!

    Thank you 

    Marc

  • Profile Image
    mliz
    Answered on March 11, 2011 at 08:00 PM

    Hello,

    Thank you for the suggestion I have added this to our feature list.

  • Profile Image
    Heeschen
    Answered on March 19, 2011 at 06:04 AM

    Mliz,

    this is very important to me and i guess for all paypal sellers.

    Because then we can send the payer data to our database automatically! 

    Do you have am idea when it will be available ?

    Hope it will come soon

    Thank you so much

    Marc

  • Profile Image
    liyam
    Answered on March 20, 2011 at 12:34 AM

    Hello,

    What we can do for now is let the developers know of this request.  We don't have a definite timeframe when this can be done.

    What I can suggest for now is use parsing. generate your RSS reports in the reports option. and parse the xml value in it and dump it to your database.

    Hope this helps.

    Thanks

  • Profile Image
    lbmh
    Answered on December 07, 2011 at 11:04 AM

    I made a similar request/sugestion six month ago

    " Is there a way to not include PayPal Payer Information in autoresponder emails?

    Asked by lbmh on June 07, 2011"

     

    and also got an "added to our feature request list" answer

     

    So far no action.

     

    This is  annoying

  • Profile Image
    dmichaels
    Answered on December 23, 2011 at 11:28 AM

    It's discouraging.

    An otherwise fine application pretty much ruined by something so obviously wrong; apparently no idea of how much of a problem it is to anyone who is using PayPal together with JotForm.

    We can't send professional looking e-mails, and any report that includes payment information looks just awful.

    Sad.

  • Profile Image
    lbmh
    Answered on December 23, 2011 at 11:34 AM

    Hi David,

    Hope everything  is fine with you, nevertheless....

    I totaly agree with you and do not understand why Jotform is so slow to correct this most annoying issue.

    All the best.

    LB

  • Profile Image
    liyam
    Answered on December 23, 2011 at 01:27 PM

    Hello,

    Sorry about this.

    Our developers are quite busy working on other more important features that's why this is still on the pending list.  For now, I have increased the urgency of this feature so to have better priority.  But as just the same, I cannot provide a definite time frame to when this feature will be implemented, but as soon as it is available, we'll let you know.

    Thanks.

  • Profile Image
    lbmh
    Answered on March 19, 2012 at 06:52 PM

    Up !

  • Profile Image
    lbmh
    Answered on May 02, 2012 at 07:03 AM

    UP, again !  

     

    This annoyance verging on a bug is realy a turn off !

    It has been communicated to you more than a year ago, and still it has not been corrected.

    Shame

  • Profile Image
    jeanettebmz
    Answered on May 02, 2012 at 02:08 PM

    @Ibmh

    The priority of this request is now set to important I have also sent a message to 2nd level

    Like my colleague Lyam has stated, unfortunately, we cannot provide with a timeframe. However, since this request has been done not only by Heeschen and you, but also dmichaels, I am sure the developers team will do their best in order to improve the Paypal feature.


    Jeanette

  • Profile Image
    lbmh
    Answered on June 19, 2012 at 02:25 PM

    A month and a half more, and nothing new ...

  • Profile Image
    Mike_T
    Answered on June 19, 2012 at 04:51 PM

    We deeply apologies for the delay on this. Mentioned feature request ticket is still in Developers' queue. We see your updates, and as soon as we have any news we will let you know.

    Thank you for your patience in this matter.

  • Profile Image
    davidator
    Answered on August 18, 2012 at 04:21 AM

    Hello!

    i Need hide paypal infos too !

    last e mail you said TY for your patitience is june 19 ! we are August 18 !

  • Profile Image
    liyam
    Answered on August 18, 2012 at 04:28 AM

    We apologize for this, davidator.

    The development team is pretty busy working on other things that are already in the pipeline.  Rest assured we'll inform you of the progress as soon as we receive information from them.

    Thanks.

  • Profile Image
    davidator
    Answered on August 18, 2012 at 04:58 AM

    ok! Thank you for your reply!

    except this detail, your website is awesome!

  • Profile Image
    jeanettebmz
    Answered on August 19, 2012 at 06:06 PM

    @davidator

    Thank you for understanding and for your kind words towards our product

    Cheers!

  • Profile Image
    lbmh
    Answered on October 31, 2012 at 10:23 AM

    Tomorrow is Nov 1st and nothing has been done yet !

     

    To quote  dmichaels on December 23, 2011

    It's discouraging.

    An otherwise fine application pretty much ruined by something so obviously wrong; apparently no idea of how much of a problem it is to anyone who is using PayPal together with JotForm.

    We can't send professional looking e-mails, and any report that includes payment information looks just awful.

    Sad.

  • Profile Image
    Deygus
    Answered on October 31, 2012 at 11:14 AM

    On behalf of JotForm we would like to extend our apologies on this again, however, this is something that cannot be rushed due to the fact that as previously mentioned all we can do for you is notify the Developers about your request per features.

    It is then up to the Developers to prioritize and release these updates which are often done on a weekly basis usually containing hotfixes, updates, and sometimes brand new features or integrations.

    Also, all of this is dependant on the demand, programming required, and the urgency of other higher priorities involving more complex features, errors and such from our development team. 

    Our developers will usually respond when there is an update about this pertaining feature and again we apologize about the lengthy wait.

  • Profile Image
    lbmh
    Answered on November 03, 2012 at 10:18 AM

    Attention developpers !

    The only thing to do is as dmichaels said on June 15, 2011

    "If it will make the developement effort any easier, I think we'd all be happy if instead of adding the "extra" info

    ==Payer Info==
    First Name ******
    Last Name ******
    E-Mail ***********

     into the amount field, just make the amount, and ONLY THE AMOUNT,  available to us SOMEWHERE."

    That should not represent a hudge amount of work, just "limit" the output of the query related to the {"amount9"} field to a number , actualy the "amount" that has been input by the user, instead of the above "payer info" garbage.

    If, for compatibilitiy reasons you want to retain the actual &@!?§ output, just create a new subfield,  for example {"amount9":price}(as existing with the {fullname2:first}. You might also want to create the other related subfields...

  • Profile Image
    liyam
    Answered on November 03, 2012 at 10:23 AM

    We understand your concern, lbmh.  Rest assured this is to be relayed to our next level support so to have them informed.

    Thank you for your patience and support.

  • Profile Image
    lbmh
    Answered on December 10, 2012 at 10:06 AM

    jeanettebmz said on May 02, 2012

    "The priority of this request is now set to important I have also sent a message to 2nd level"

    That was over seven month ago.

     

    When I got your promotion e-mail today,

    i was almost ready to get a paying subscription,

    but untill you correct that annoyance,

    your " otherwise fine application is pretty much ruined"

    and unfit for our use, so no subscription for the time beeing

  • Profile Image
    moonzkie
    Answered on December 10, 2012 at 10:42 AM

    An update has been made for your request, we are again sorry about this.

    Thank you for your patience. 

  • Profile Image
    lbmh
    Answered on March 19, 2013 at 04:19 PM

    All ends Well ! Eventually we now have a full set of "tags" to customize e-mail alerts.

    Please refer to the summary at http://www.jotform.com/answers/29183-Is-there-a-way-to-not-include-PayPal-Payer-Information-in-autoresponder-emails

  • Profile Image
    NeilVicente
    Answered on March 20, 2013 at 09:58 PM

    Everyone,

    We have just recently implemented this change. Payment data is now separated into three columns when exported to Excel or CSV format.

    Please do test it out and let us know your thoughts.

    Best regards

  • Profile Image
    dmichaels
    Answered on March 20, 2013 at 10:33 PM
    After adding a new email to an existing, working form, using the new PayPal
    tags, when I click submit I get this error. I then arrive at the PayPal
    payment page. The correct amount is shown on that page. I then aborted the
    transaction pending hearing from you. These new PayPal tags are quite
    exciting; I'm sure they will be working perfectly soon.

    Thanks,
    David

    The form is the Dues Payment Form
    My Username is dmichaels

    Warning: Unknown: Unable to allocate memory for pool. in Unknown on line 0
    Warning: include_once(): Unable to allocate memory for pool. in
    /etc/jotform/preLoader.php on line 22 Warning: Unknown: Unable to allocate
    memory for pool. in Unknown on line 0 Warning: include_once(): Unable to
    allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/index.php on line 2
    Warning: require_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    76 Warning: require_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    76 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    180 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/classes/AWSSDK/s
    dk.class.php on line 38 Warning: include_once(): Unable to allocate memory
    for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    187 Warning: require_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    63 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    190 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    193 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    196 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    199 Warning: include_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    202 Warning: require_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    63 Warning: require_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/classes/LibraryL
    oader.php on line 61 Warning: require_once(): Unable to allocate memory for
    pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/classes/LibraryL
    oader.php on line 61 Warning: require_once(): Unable to allocate memory for
    pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/classes/LibraryL
    oader.php on line 61 Warning: require_once(): Unable to allocate memory for
    pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/classes/LibraryL
    oader.php on line 61 Warning: require_once(): Unable to allocate memory for
    pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/classes/LibraryL
    oader.php on line 61 Warning: include(): Unable to allocate memory for pool.
    in /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on
    line 238 Warning: require_once(): Unable to allocate memory for pool. in
    /www/v3/builds/faaa1687b4ec410dc44a413fdab15775d46d2b73/lib/init.php on line
    63

    Please wait while redirecting...


    _____
  • Profile Image
    EltonCris
    Answered on March 20, 2013 at 11:45 PM

    Hi David,

    The error message on the thank you page should now be fixed. It was just a temporary glitch on the system but everything should now be fine and submissions will remain unaffected.

    Our apologies for the inconveiences caused.