|
frogmorris
|
March 14, 2017 at 4:56 am
We have recently migrated to PayPal Express in the hopes that it will solve some of the problems we were having with Event Espresso losing over 10% of tickets that were successfully paid for. So far this seems better.
However, it does throw up some serious problems with reporting. With regular PayPal, we would get the ticket and the event name reported, like so:
Ticket For 18th March for Simon Amstell: Work in Progress
Ticket For 18th March is the ticket name, and after the ‘for’ it’s the event name. However, with PayPal Express, you seem to only be feeding them the event name:
Event Registrations from Angel Comedy Club for Simon Amstell: Work in Progress
The first two bits of information are useless to us, as it will always be for event registrations and from us. Yet without the Ticket information it is very hard to keep track of what is being spent where, and who needs payment.
I cannot find anywhere in the Payment Methods settings to change this, but I’m hoping we can find a way to fix this quickly, as it make billing almost impossible.
Thank you.
|
|
Josh
|
March 14, 2017 at 8:40 pm
Hi there,
Event Espresso actually does send the ticket name to PayPal Express, and it sends each ticket’s name along as the item name field. It sounds like you’re looking at the order description, which with PayPal Standard would also be generic (it would return “Shopping Cart”). The order description is generic by design because there could be many tickets in one order, but each of those ticket names do get sent to Paypal Express as separate line items.
All that said, these things can be customized by using the filter hooks, and here’s a link to some example code that shows how to add the Attendee name along with the item description for any of the PayPal gateways:
https://github.com/eventespresso/ee-code-snippet-library/blob/master/checkout/mn_gateway_line_item_custom_descriptions.php
|
|
frogmorris
|
March 16, 2017 at 4:26 am
Thanks Josh,
PayPal reports these as Item Name. I presumed that PayPal took this from a string you were feeding them. Are you saying that PayPal generates this itself from various strings that you feed them, and that PayPal Express generates the Item Name in a different way from PayPal Standard?
Is the implementation different at your end or at PayPal’s end?
I’d rather not go down the custom code route if at all possible (although thank you for the link), as this can cause problems when systems change further down the line.
Thanks!
|
|
Josh
|
March 16, 2017 at 8:32 am
Are you saying that PayPal generates this itself from various strings that you feed them, and that PayPal Express generates the Item Name in a different way from PayPal Standard?
Not quite. You’re not looking at the item name in PayPal Express. You’re looking at the Order Description. The order description is not the item name. They are two different things.
Is the implementation different at your end or at PayPal’s end?
They’re different at both ends in that PayPal Express and PayPal Standard have slightly different names for the fields between the two. However, they both have what’s equivalent to an item name field, and EE sends the ticket name for the item name field.
What you could do is reach out to PayPal and find out if they can include the item names in the transaction history for PayPal Express transactions. Event Espresso is sending that info to PayPal Express. In fact, if you go into Event Espresso > Payment Methods > logs, then check the transaction logs there, you’ll see where Event Espresso sends the Ticket Name to the PayPal Express in the Payment Token Request as the L_PAYMENTREQUEST_0_NAME1 field.
|
