|
Createful
|
March 29, 2018 at 5:00 am
Getting this error every time I try to make a payment. Using (fully up-to-date) Payments Methods Pro and the SagePay addon.
I’m using the staging version of our website, the IP address of which is successfully connected to the SagePay account. I’ve tried test amounts of £0.01, £0.02 and £1.00 but I get this same error message each time.
Tried with caching plugin tuned on and off. (had already carried out your recommended changes to the caching configuration).
Under the Transactions panel in the admin area, these are showing as “TXN in progress…” with “Abandoned” underneath.
There’s no gateway response, TXN ID or P.O. details logged with this transaction either.
What should I try next?
|
|
Tony
|
March 29, 2018 at 6:05 am
Hi there,
So, to get that error your EE_Payment object passed through single page checkout (SPCO for short) is no longer an EE_Payment object which is very strange.
Do you have an offline payment activate at all? If not temporarily enable the Invoice payment method and use that to finalize a registration, does that work?
Any customizations at all?
|
|
Createful
|
March 29, 2018 at 7:06 am
I’ve got SagePay and Invoice as my two payment options. SagePay is showing the error above, but the Invoice option works fine – the transaction goes through and shows as “Pending Payment”.
There are no major customisations to the system, the only thing I’ve done is change the event slug via the Events > Templates screen.
|
|
Tony
|
March 29, 2018 at 7:10 am
I’ve got SagePay and Invoice as my two payment options. SagePay is showing the error above, but the Invoice option works fine – the transaction goes through and shows as “Pending Payment”.
Thank you for checking.
If you go to Event Espresso -> Payment methods -> logs
Can you log entries from Sagepay there or not? I’m guessing not but if you do, do any of those show any errors?
There are no major customisations to the system
That’s a scary sentence as one person’s major is another’s minor 😉 but…
the only thing I’ve done is change the event slug via the Events > Templates screen
That’s fine, I meant more on the lines of code changes or custom functions.
|
|
Createful
|
March 29, 2018 at 7:25 am
Looking in the payment method logs, I can see the SagePay transactions. Under Registration Step Progress I see:
Attendee Information : Completed
Payment Options : Initiated 29th March 2018 11:48 am
Finalize Registration : Never Initiated
Under Payment Details, the Gateway Response, TXN ID/CHQ #, P.O./S.O. # and Notes fields are all empty – no errors visible.
I know what you’re saying about minor/major customisations, but the most I’m doing in the functions file is adding custom taxonomies to the body class, adding menu options ordering for custom post types, and a related events section. Other than that, nothing.
|
|
Tony
|
March 29, 2018 at 7:32 am
Looking in the payment method logs, I can see the SagePay transactions. Under Registration Step Progress I see:
Click the ID number on the left, rather than the TXN ID on the right, you’ll see the log itself rather than the transaction it’s associated with.
|
|
Createful
|
March 29, 2018 at 7:53 am
Click the ID number on the left, rather than the TXN ID on the right, you’ll see the log itself rather than the transaction it’s associated with.
Ok, so clicking the ID shows me this for the last (failed) transaction:
VPSProtocol: 3.00
Status: 3DAUTH
StatusDetail: 2007 : Please redirect your customer to the ACSURL, passing the MD and PaReq.
3DSecureStatus: OK
I’ve not included the other bits, in case they’re sensitive.
|
|
Josh
|
March 29, 2018 at 8:13 am
The Sage Pay gateway’s billing form is included on your site (as opposed to redirecting the customer to Sage Pay’s site, where they input billing information there). If I remember correctly, the 3DSecure option is only available if the customer is redirected to Sage Pay’s site which means you’ll need to deactivate the 3DSecure option in your Sage Pay account.
|
|
Createful
|
March 29, 2018 at 8:35 am
which means you’ll need to deactivate the 3DSecure option in your Sage Pay account.
So EventEspresso cannot handle SagePay’s 3DSecure system, is that right?
|
|
Josh
|
March 29, 2018 at 8:54 am
Kind of correct. Technically speaking, it’s Sage Pay that handles 3Dsecure because 3dSecure support happens on their website. The Event Espresso Sage Pay gateway was built as an on-site gateway, so the user isn’t redirected to a 3rd party site during the payment step.
|
|
Createful
|
April 9, 2018 at 3:14 am
Thanks for the clarification @josh. So how do I get this working? Is it the case that the 3DSecure feature needs to be deactivated? Is EventEspresso incompatible with SagePay when 3DSecure is active? Have other users got the SagePay payments module working with 3DSecure?
|
|
Josh
|
April 11, 2018 at 4:06 pm
Currently the Event Espresso 4 SagePay gateway does not support 3DSecure. So if you have 3DSecure activated in your SagePay account, you’ll need to deactivate that feature to accept payments via SagePay.
|
