Shopp Support » Setting Up Shopp

Setting Up Shopp

PayPal Pro & Express together

  1. jpack

    Hi,
    I seem to be having some trouble getting PayPal Express Checkout working in conjunction with PayPal Pro.

    Individually I can use PayPal Pro with credit cards or PayPal Express with a paypal account no problem, but when I have both payment methods active together Pro works fine, but Express gives me trouble when I return back to my site from PayPal. It acts as if it's trying to use the Pro module even though I've just done the offsite Express checkout.

    When I come back from PayPal (sandbox) to a URL like:
    mysite.com/shop/checkout?shopp_xco=PayPal/PayPalExpress&token=EC-79W04195YC3321024&PayerID=W68VZ358U5V2G

    I get this error:
    PayPalPro: CreditCardType : Required parameter missing [Flow.php, line 544]

    Any ideas? Am I missing something obvious here?

    Thanks,
    Jason

    Posted 8 months ago — #

  2. Support Team
    Adam

    We'll have to do some testing with this. Theoretically, this should be possible.

    Posted 8 months ago — #

  3. tderuelle

    I have almost the same problem, the paypal pro works fine, it's the express that doesn't... which in my case is a big thing since I sell tunes at 99 cents.

    I tested it alone and it still don't work. Anyone?

    http://www.dztd.ca

    Posted 7 months ago — #

  4. Support Team
    Adam

    I don't see the PayPalExpress button on your cart, but I do believe there is an issue selling items through PayPalExpress for less than 1.00. This needs to be verified before I can create a ticket.

    Posted 7 months ago — #

  5. Courtney Bostdorff

    I just recently tested in live mode and sold a product using PayPal Express for 10 cents and everything worked perfectly, so I don't believe it's an issue with the price being under $1.

    Posted 6 months ago — #

  6. Morgan Benton

    I'm getting the following error:

    PayPalPro: CreditCardType : Required parameter missing

    I am ONLY using the PayPalPro (1.0.7) gateway. All others are deactivated. I'm using Shopp version 1.0.12. I've tried with multiple credit cards. I've examined the HTTP headers and I'm sure that the billing[cardtype] parameter is being passed (at least to the order confirmation page). WP is 2.8.4. PHP version 5.2.10.

    Any debugging suggestions?

    When I first installed the PayPalPro gateway I uploaded the PayPalPro.php file into the PayPal folder with the other two that were already there. Later I created a separate PayPalPro folder and moved the PayPalPro.php file into that. Is it possible that this could somehow be causing the problem? Also at one point both Pro and Express were activated at the same time, similar to @jpack.

    Not sure where to look for the error or how to do a "reset" that might fix this. My guess is that the problem may come from some residual settings in the database, but not sure what they might be...

    Thx.

    Posted 4 months ago — #

  7. James Morrison

    I'm also having the same issue as @MorganBenton - I opened a Help Desk ticket but have heard nothing back...

    Trying to use PayPal Pro (1.0.7) with Shopp (1.0.12) and get stuck in a loop at the 'confirm order' page (sent back to checkout).

    The error message is:

    An error has occured:
    PayPalPro: CreditCardType : Required parameter missing

    Another weird error - I tried leaving the Card Type field blank (no card type selected) and the JS popup asked me to enter a valid phone number (there was a phone number present and once selecting a card the error stopped).

    Technical details (my experience with 'support' is they take 3 days asking for one bit of information at a time...):

    WordPress Version: 2.8.4
    PHP Version: 5.2.9
    MySQL Version: 5.0.81

    Shopp Version: 1.0.12
    PayPro Payments: 1.0.7

    The log error is:

    2009-10-13 16:50:27 - PayPalPro: CreditCardType : Required parameter missing [Flow.php, line 443]

    Please fix this ASAP this is a major problem as nothing can be sold at the moment!!

    Posted 3 months ago — #

  8. James Morrison

    Turns out your *update* to 1.0.12 caused the problem.

    Fixed in 1.0.13.

    Posted 3 months ago — #

Reply

You must log in to post.