I’m testing purchases with my Event Espresso 3 plugin. I’m in test mode, so it’s not live. When I test a purchase, I get the following error message:
Status:
Error: Error (Merchant config file is missing, empty or cannot be read).
I’ve setup my .pem file and it’s in place under /gateways/firstdata. As you can see, First Data is my merchant. Any help would be great as my client wants this live ASAP.
Is this on a live site or locally hosted? If on an actual server, are the file permissions correct (All directories should be 755 or 750. All files should be 644 or 640.)?
It could be the storenumber that EE is using to look for the file is not the same as the one in the filename. Double check the entry in the EE payment settings, looking for a leading or trailing space, especially.
The store numbers match between the entry in EE and the .pem file name. Any other thoughts? For time purposes, can I give you access to the files and let you take a look? This is time sensitive.
I think I found the problem. First Data requires a separate “testing” account when testing in debug mode. I need to get a separate store number and PEM file while in debug mode. I will request that from them.
Thank you for your prompt and timely response to my question. I will let you know if I have any other issues.
Viewing 8 reply threads
The support post ‘Merchant config file is missing, empty or cannot be read – Error message’ 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.
Support forum for Event Espresso 3 and Event Espresso 4.