Error from DPS PxPay request: Check User Access Error:

The error is coming from payment express and tells you that the user id and key are not correct. You should check with DPS to ensure that you get the correct credentials. I’ve heard several instances where the had to issue new keys.

Once you have that sorted out, your browser will be redirected to the payment express site where you can enter credit card details before returning to your website.

cheers,
Ross

Hi Ross. So, I contacted DPS and it turned out that they had actually set us up with a PxFusion account. After I explained to them exactly what your plugin was, they have gone and set us up with a new PxPay 2.0 account. Is the plugin compatible with this?
They specified in their e-mail to me that XML requests need to be sent to https://uat.paymentexpress.com/pxaccess/pxpay.aspx. I have sifted through your plugin code, and it does appear that that is what you have set up.
I have carefully checked the User ID and Key character by character ensuring that there is no leading or trailing whitespace and DPS have also double-checked that they have given me the correct credentials.
I am still getting the exact same error:
PxPay payment request error
Error from DPS PxPay request: Check User Access Error:

Perhaps you could e-mail me privately at [email protected] and I could then give you the WordPress login details for the site I’m working on and you could check that everything is as it should be?

G’day kebbie,

I just checked in my testbed environment, and using incorrect details gives this error: Invalid Access Info

Please ask Payment Express to check your account again, and make sure that they know what error you are getting from PxPay. It still sounds like an account configuration problem (and most likely at their end, not yours).

cheers,
Ross

Ok, thanks. I will do that.

Can I just double check with you though; your plugin definitely supports PxPay 2.0? I saw another thread in this forum where you said it didn’t and that you were going to look into updating it to support 2.0, but it was posted 2 years ago, so I’m hoping / assuming that you did actually make the upgrade to PxPay 2.0?

Yup, added in November 2014. In fact, DPS have migrated any PxPay 1.0 API calls so that you always get v2.0 now anyway. I removed support for v1.0 API calls in September last year and only use v2.0 API calls now.

cheers,
Ross

Hi Ross. Ok, I wonder if this might tell us something. I have found DPS’s demo sandbox page: https://www.dpsdemo.com/Sandbox.aspx

So, if I enter the UserID and Key that they’ve given me, I’m getting a successful result if I have the “Web Service Address” field set to either “UATPxPay” or “UATPxPay2”. Every other option gives me the “Check User Access Error” message.

Does this give you any clues as to where the problem might be?

G’day kebbie,

OK, now we’re getting somewhere! Thanks for the investigation effort. It looks like DPS have finally created a separate testing environment for PxPay. I didn’t know that (nobody told me, certainly not DPS).

Curiously, my test account works on SECPxPay2 and fails with “Check User Access Error” on UATPxPay2. I’ve had that test account since 2012, so maybe old accounts have been grandfathered in, but not added to the UAT environment.

I’ve sent a query to DPS, and hopefully they’ll respond by next week sometime. In the meantime, I’ll cut a test version for you to try sometime today that will use the UAT environment when you select Use Sandbox.

cheers,
Ross

Mate, that would be awesome! Thanks!
Let me know when it’s ready and where to download it from. ??

G’day kebbie,

Please give this one a burl:

https://www.dropbox.com/s/dx7i9nlnxod3r0f/gravity-forms-dps-pxpay-1.5.2-dev.zip

cheers,
Ross

YES YES YES YES YES!!!!!! THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!!!!!!

That has totally worked! You are awesome!! ??

Oh good. Thanks, especially for picking this up because I totally missed it! Sometime between when I last checked the doco and now, they introduced the UAT environment.

I just need to get a response from DPS support to confirm a few things, and I’ll release this as an official version (with a couple of other fixes). With any luck, they’ll get back to me within the week-or-so they usually take.

cheers ??
Ross

For completion: DPS developer support responded today (yay! record time…) and it seems that some people get their test account created in SEC and some in UAT. I’ll be changing the add-on to accommodate that.

What this means for you is that you’ll need to check your settings after updating to the next version. There will be a setting for selecting which environment your sandbox account uses, and it will default to SEC for existing add-on users (because of backwards compatibility) and UAT for new add-on users. You’ll need to change the setting to UAT.

cheers,
Ross