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
Beanstream not working due to invalid credit card expiry month | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Beanstream not working due to invalid credit card expiry month

Beanstream not working due to invalid credit card expiry month

Posted: January 28, 2013 at 2:23 pm

Viewing 7 reply threads


MAGentix

January 28, 2013 at 2:23 pm

After testing payments on our website using Beanstream, the credit cards keep getting rejected due to an invalid expiry date month, see result text below:

“Attention: Your transaction was declined for the following reason(s):
%3CLI%3EInvalid+expiration+month%3Cbr%3E”

I talked to customer support at Beanstream and they confirmed that the transactions aren’t coming through due to the month format. The current format is one digit, ex: January=1, March=3. I need the month format to be in 2 digits, ex: January=01, March=03.
I’ve searched the support forums and have seen people with this problem using payment methods other than Beanstream. I know that some diting can be done in the aim_vars.php file but I’m not very experienced php and do not want to break any code.

Thanks for your help ,


MAGentix

January 28, 2013 at 2:23 pm

After testing payments on our website using Beanstream, the credit cards keep getting rejected due to an invalid expiry date month, see result text below:


Josh

January 28, 2013 at 2:28 pm

Hi there,

This has been fixed in the 3.1.30 pre release. You can download the (almost) final version from the pre-release channel by opting-in to the pre-release channel from your account page.


MAGentix

January 29, 2013 at 6:03 am

Thanks,

What’s the simple way to update Event Espresso through the WordPress control panel?
There’s doesn’t seem to be a way to upload the new version .zip file and have it update seamlessly.


Josh

January 29, 2013 at 8:08 am

Hi there,

The simplest would be to wait for the official release. If you want to go ahead and try the pre-release, you can deactivate the version of Event Espresso that’s installed right now, and use the plugin uploader on the WP plugin admin page, then upload and activate the Event Espresso pre-release.

Once the official version is up, you can deactivate and delete the pre-release, then active the official release channel version and click through the auto update.


MAGentix

January 29, 2013 at 8:27 am

No problem, most of this I was aware of, but I’m concerned that all of my Event Espresso settings and events will be erased. Are they safe if I uninstall the current version then immediately install the pre-release?


Chris Reynolds

  • Support Staff

    •

January 29, 2013 at 11:31 am

The settings should be shared between the pre-release version and the final version. We don’t add new database tables/values for just the pre-release version.


MAGentix

January 29, 2013 at 12:53 pm

Thanks for the reassurance, made the switch, everything worked fine
Viewing 7 reply threads

The support post ‘Beanstream not working due to invalid credit card expiry month’ 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 MAGentix 11 years, 11 months ago ago

Topic Tags

Tagged: , , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server