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
Trial Runs Using Stripe for Event Registration Failed | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Trial Runs Using Stripe for Event Registration Failed

Trial Runs Using Stripe for Event Registration Failed

Posted: October 5, 2013 at 11:31 am

Viewing 4 reply threads


Pete Stajk

October 5, 2013 at 11:31 am

The test run for my event registration using Stripe’s test API codes worked, but after I changed the API authentication codes in EE’s Payment Settings to “live”, my 1st 2 trial runs failed in which I used 2 different credit/debit cards of my own.

I reset my event registration cost to $0.01 just to see if it worked with my 2 cards and received this message:

“ERROR: Failed to charge the card.
Looks like something went wrong. Please try again or notify the website administrator.”

What might be causing this problem, and how can I resolve it quickly?

Thank you.


Dean

  • Support Staff

October 7, 2013 at 1:33 am

It could be that there is a minimum amount – https://support.stripe.com/questions/what-is-the-minimum-amount-i-can-charge-with-stripe

Have you checked your settings to make sure the keys are the live keys and there is no extra spaces etc?


Pete Stajk

October 7, 2013 at 7:27 am

It works!


Dean

  • Support Staff

October 7, 2013 at 9:01 am

Awesome, can I ask what the issue was in case it can help others in your position?


Pete Stajk

October 7, 2013 at 11:40 am

It was the minimum amount of $0.50.

Viewing 4 reply threads

The support post ‘Trial Runs Using Stripe for Event Registration Failed’ 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 - Staging Server