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 Accepting Credit Cards, no API gateway | Event Espresso - Staging Server
Due to needing to verify membership status offline, from registrants, we need the ability to take credit card payments, but to process them offline. I did not see this option under the payment options.
While using an API gateway is the safest method for purchasers, there are alternate, and safe ways of taking credit card data; SSL in combination with .htaccess restrictions, and file encryption can be used to ensure payment information remains secure. Let’s be honest, the vast majority of users do not even properly secure their CMS (wordpress). But all that is beside the point.
Is the answer that the software (event espresso) does not allow for credit cards to be entered without a payment gateway?
Event Espresso can be used to capture any information on the registration form, but it stores the information in the database. Storing credit card information this way may not be legal though.
I’m afraid that setting up a custom registration form that captures credit card numbers would not be PCI-compliant, and it does expose people to risk, so we only recommend accepting credit card information online through a payment gateway.
The support post ‘Accepting Credit Cards, no API gateway’ 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.