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 Realex (Realauth) payment gateway does not support ACCOUNT | Event Espresso - Staging Server
The RealAuth docs state that the ACCOUNT variable must be used for defining the subaccount used. If this variable is not present in the request then the default ACCOUNT “internet” will be used.
My client is using a different account name then the default so the payments through Realex do not work. I have made some ammendments to the code which will allow the user to set an account name. If it is left blank it will default to the default account “internet”.
I am using version 3.1.27.P
If anyone else needs the same modifications done I can send you the code modifications I made. Or how would I go about submitting the changes so they can be changes in the next version?
Hi Michael,
can you please forard me the code. Need it for testing
Dean, another variable needs to be passed along with merchantid & secret. If account variable is set to internettest, then transaction are made in test mode.
$merchantid = “XXXXXXX”;
$secret = “XXXXXXXX”;
$account = “internettest”;
@Michael, Sorry, thought there was a PM option
If you could email them to alan@ebook.ie
Many thanks
alan
Viewing 4 reply threads
The support post ‘Realex (Realauth) payment gateway does not support ACCOUNT’ 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.