Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
QuickPay not recording transaction/reg/payment ID | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › QuickPay not recording transaction/reg/payment ID

QuickPay not recording transaction/reg/payment ID

Posted: November 22, 2012 at 10:07 am

Viewing 1 reply thread


Runemester

November 22, 2012 at 10:07 am

We are having trouble tracking payments through the QuickPay gateway with event espresso @ http://www.esrum.dk. The registration ID (in the pattern of: 22-5075367dbe725) is only recorded locally in event espresso and is not sent through to QuickPay. At QuickPay a randomly generated transaction ID is recorded but this has no correlation with the IDs recorded in event espresso. Do you have any suggestions as to how we can fix this issue – could this be a bug in the gateway file? Unfortunately this issue is a major obstacle for us as we desperately need to be able to connect credit card payment IDs with the tickets purchased through Event Espresso.

Thanks
Rune


Josh

November 23, 2012 at 7:41 am

Hi Rune,

Sidney followed up with you in the other thread:
http://staging.eventespresso.com/topic/quickpay-not-recording-transactionregpayment-id/
Viewing 1 reply thread

The support post ‘QuickPay not recording transaction/reg/payment ID’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by Josh 12 years, 1 month ago ago

Topic Tags

Tagged: , , , , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server