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 Stripe and Zip Code/CSV Verfication | Event Espresso - Staging Server
I have a client who is using Stripe as their payment processor. On the Stripe backend they have set up Stripe to Decline Charges that fail CVS verification and
decline charges that fail zip verification. However ticket purchases are still going through even if cvs and zip code are incorrect. Is the zip code and cvs info passed on to Stripe when an order is charged.
I checked and it appears that the CVC is passed, but the zip code isn’t. A few lines of code in the Stripe gateway can be modified to make that happen.
1) In the Stripe gateway’s stripe.class.php file on line 7 the $bzip variable can be added:
function do_transaction($amount ,$cc, $cvc, $exp_month, $exp_year, $name, $bzip, $description, $payment_data){
2) In the same file the address_zip can be added. I’ll include the entire array for context:
If you copy the stripe folder over to /wp-content/uploads/espresso/gateways it will not get overwritten on an update. I will create a ticket so the zip field gets added the next time the stripe gateway gets an update. Hope this helps.
The support post ‘Stripe and Zip Code/CSV Verfication’ 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.