Support

Home Forums Event Espresso Premium Non Sequential Transaction IDs

Non Sequential Transaction IDs

Posted: November 22, 2019 at 9:45 am


DynamicHospitality

November 22, 2019 at 9:45 am

Hello,

My accountant has come back to me with a very concerning issues. The transaction IDs are skipping and it is very hard for us to (a) keep track of transactions and if all are being received, (b) we have no record of the transactions that failed/ abandoned.

In the following link I found another support ticket that mentions the same issue and the explanation does make sense but when I go to transactions, abandoned has only 1 and failed transactions has 0 so in the end I have no record of what happened to the transactions missing in between the ones recorded (i.e. ID 27 – 31). Is there a setting I did not check off to allow all transactions (complete, failed and abandoned) to show up under transactions?

My accountant mentioned the auditor will be asking about this inconsistency and I need to get down to the bottom of this before we get too far into selling tickets on this platform as we are live now for a few days now.

Please advise. Thank you.

https://eventespresso.com/topic/non-sequential-transaction-ids/


DynamicHospitality

November 22, 2019 at 10:22 am

I just realized that the Gateway Transaction ID number in the excel sheet exported from the registrations panel coincides with the Transaction ID for PayPal. Is there a short code I can add to the Registration Approved email message that our event admin receive? That will resolve this the accounting issues for this at least but not the tracking issue.

Please advise. Thank you.


Josh

  • Support Staff

November 22, 2019 at 10:31 am

Hi,

There’s no setting to show all transactions. A minor point of clarification: The UI shows Completed, Incomplete, Abandoned. If you want to view the failed transactions from the past 7 days, you can add this to the end of your site’s URL:

wp-admin/admin.php?page=espresso_transactions&action=default&status=failed&return=default

Please note that the transactions that get started but do not progress to the point of completing a registration form are considered Failed transactions (which means they didn’t even progress to “Abandoned”). These are automatically deleted after 7 days.


Josh

  • Support Staff

November 22, 2019 at 10:52 am

Is there a short code I can add to the Registration Approved email message that our event admin receive?

Yes, you can add:

[LAST_PAYMENT_TRANSACTION_ID]

to that email template.


DynamicHospitality

November 22, 2019 at 11:44 am

Thank you Josh.

I will wait for another transaction to come through to see if that code lines up with paypal.

Re. the failed transactions, is there a way to…

(a) have the failed transactions show up on the Transactions list or at least have the option available somewhere for me to click and reference easily? I have other team members that are MUCH less tech savy than me, and this might be a bit much for them to wrap their heads around.
(b) extend the 7 day expiry since it is sitting on our server? Maybe extend it to 1 year?

Thank you.


DynamicHospitality

November 22, 2019 at 12:48 pm

Sorry to add to question (a)… an email every time registration fails would suffice too… we just need a record of it for the auditors. Would that be possible by creating a custom new message instead with these details?


Josh

  • Support Staff

November 22, 2019 at 2:56 pm

is there a way to…

(a) have the failed transactions show up on the Transactions list or at least have the option available somewhere for me to click and reference easily?

Yes you can add this code to a site functions plugin:

add_filter(
'FHEE__Transactions_Admin_Page___set_list_table_views_default__display_failed_txns_list',
'__return_true'
);

That will add a “Failed Transactions” link to the Transactions page.

Then you can add this to your site functions plugin to change the delay for the junk transaction cleanup to one year:

add_filter(
'FHEE__EEM_Transaction__delete_junk_transactions__time_to_leave_alone'
,
YEAR_IN_SECONDS
);

A word of caution about changing the delay from 1 week to 1 year: Your database might crash at that one year point if many (like thousands or more) junk transactions are in the database when it tries to delete that first run. You might consider changing the delay to 1 month, 3 months, or if not many junk transactions 6 months.

You can add the above code to a functions plugin, this guide outlines how to add a functions plugin.


DynamicHospitality

November 22, 2019 at 4:24 pm

Thank you Josh,

This is great, really appreciate it.

One more question, would we be able to generate an email message every time a failed transaction arises instead so we don’t have to manually go online and remember to download the list of transactions every 3 months?

Thank you.


Josh

  • Support Staff

November 22, 2019 at 5:02 pm

Not exactly and the reason why is because every transaction starts out as a failed transaction. Then they progress on to the next status as each step in the checkout process is completed. So if you were build out a new message type to send out messages for failed transaction, they would have to work out a way to monitor transactions and send a message if they do not progress after a specific amount of time. Currently Event Espresso does not have any of this, so this is something that would need to be custom developed.


DynamicHospitality

November 22, 2019 at 5:15 pm

Got it! Thank you. I’ll work with this workaround you’ve provided us. Thank you so much. My tech might have a follow-up question for you here if they are running into issues with putting the code in you suggested. Thank you again.

The support post ‘Non Sequential Transaction IDs’ 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.

Event Espresso