Instructions at http://www.e-junkie.com/ej/paypal-payments-advanced-shopping-cart.htm indicate that the Merchant Login for PayPal Payment Advanced accounts cannot be more than 20 characters yet when I created my account I was able to enter in more than 20 characters. When I attempt to enter in my Merchant Login under my eJunkie profile it truncates the login after 20 characters. The result is an authentication error when I attempt to process transactions. I cannot shorten my Merchant Login and thus I can't use the feature in eJunkie.



Any thoughts?



I'm guessing that the Merchant Login field in the profile area needs to be more than 20 characters but I'm hoping there may be another option because right now I'm dead in the water.



Josh

  • created

    Nov '15
  • last reply

    Nov '15
  • 1

    reply

  • 1.4k

    views

  • 2

    users

  • 1

    link

While you get this sorted out, you can disable the card-based checkout option in your cart by going to Seller Admin > Edit Profile, under Accept Credit Cards select "My payment processor will charge cards for me", then click Submit to apply changes.



It appears that PayPal has recently expanded the limits for those PayPal Manager credential fields at their end, but the corresponding fields at our end still have the original limits. The most expedient solution would be changing your Merchant Login to be 20 characters or less. If you need assistance to accomplish this, we would recommend contacting PayPal support at 888-221-1161; that number should get you to an elevated tier of tech support better acquainted with E-junkie than their regular front-line customer service agents.



Expanding any field sizes in our database is a major operation that locks up the database while the change is being applied, so it's not a simple change and must be planned for a time that would minimize the impact to our service. Development has been planning to upgrade our DB servers to SSDs (solid state drives) very soon, which are much faster than traditional hard disks, so completion of that upgrade is probably a prerequisite for any DB structural changes.