|
Devaraj
|
August 27, 2015 at 3:36 am
Our organization is using EE3 linked to EPDQ via the Sellxed Plugin…
We host a variety of groups with different prices…
When a payment reaches our Epdq Transactions in the back office, there is no way to compile the income for a specific group (or event). Just a “Merch ref” column. The only way we can identify a group of payments from a single event is to find the 2 digit prefix in the Merch Ref and trace it back manually to the relevant event.
Why is there no provision to send the event name to the Epdq plugin so it shows up in the final Epdq transactions where we can filter out the specific event details per event.
Perhaps this is a SellXed issue in their plugin?
Epdq has a blank column in the transactions page with the title of “GroupID”.. this currently only shows as blank, perhaps this field can be utilized in some way?
Any feedback appreciated, our account is going crazy trying to sort this out, if no solution is found, we need to find a solution that makes accounting easier.
Thanks
|
|
Devaraj
|
August 27, 2015 at 4:02 am
The title is supposed to read “EPDQ”
|
|
Josh
|
August 27, 2015 at 8:54 am
I can advise contacting sellXed for support. They should be able to answer your questions and possibly make improvements to their plugin based on your feedback.
|
|
Devaraj
|
September 1, 2015 at 11:24 am
SellXed have informed me that it originates with EE3….. which makes sense in a way…
Regardless, my issue is still unresolved… I am curious as to how EE3 assigns certain information from an event when the user registers and pays…
|
|
Dean
|
September 2, 2015 at 6:11 am
Hi,
The SellXed integration is not supported by Event Espresso. What I can advise though, is that with normal payment gateways, take PayPal for instance, we do indeed pass the event name over. As such it should be possible to do this in the SellXed plugin as well.
Since we did not code it, it’s very difficult for us to even offer a diagnosis, SellXed should be troubleshooting this and if they believe it to be a bug on our end (you can’t rule that out) then they should be approaching us with details and potential a pull request (a request to fix the issue).
So, I am very sorry to pass you back to them, but as the code did not originate here, and as I know that event details can and do get passed over to payment gateways, I have to assume the issue lies in the SellXed integration.
|
