|
qgrobler
|
June 22, 2021 at 6:38 am
We have been experiencing a huge increase in PAID registrations, showing up as incomplete. When checking our payment gateway the funds are paid, on EE it shows as incomplete?
|
|
Tony
|
June 22, 2021 at 7:36 am
Hi there,
The payment method itself is responsible for updating the payment within a transaction, which then updates the transaction and triggers various updates from there.
Looking at your site it looks like you are using PayFast, which is a payment method developed by PayFast themselves:
https://www.payfast.co.za/integration/shopping-carts/event_espresso
Whilst I’m happy to take a quick look over the payment logs to see if anything stands out here, we don’t actually provide support for payment methods we didn’t create so you will likely need to contact PayFast support and have them investigate this further.
|
|
qgrobler
|
June 23, 2021 at 3:57 am
Thank you, what do you need to have a look at the payment logs?
|
|
Tony
|
June 23, 2021 at 6:02 am
Temp login details for the site, you can send those using this form:
https://eventespresso.com/send-login-details/
|
|
qgrobler
|
June 23, 2021 at 6:23 am
Details sent
|
|
Tony
|
June 23, 2021 at 7:57 am
The logs show that the correct functions are being called but something within the PayFast payment method doesn’t like the details passed.
This is something Payfast will need to investigate further, unfortunately, I don’t know enough about their platform to give any further details on this.
|
|
qgrobler
|
June 23, 2021 at 8:06 am
Thank you, I will pass the information on.
|
|
qgrobler
|
June 24, 2021 at 3:24 am
We received this response from Payfast:
“Please note that the core repo for Event Espresso was modified 7 days ago, which correlates with the date of your client’s issue. https://github.com/eventespresso/event-espresso-core
Kindly investigate how this change may have reflected on your integration. We suggest rolling back any changes outlined in this update if possible.
“
|
|
Tony
|
June 24, 2021 at 5:59 am
Your site is not using our github repo (which is correct, it should not be using it) but using our release versions.
The latest version is currently 4.10.11.p which was released on April 27th, 2021.
Looking over the activation history on your own site, it shows you have version 4.10.11.p and you have had that version activated since 2021-04-30 12:35:29, which means the changes in our repo have nothing to do with this issue.
|
