ok

a couple of things for future reference (and thinking out loud for a bit here too)

– although there’s no checkbox option to turn this post/zipcode validation off (as this really is a security validation you should have enabled to combat fraud) if one really wants to disable this (for whatever reason), there’s a filter included that could be used to disable this verification like so

add_filter('wppizza_gateway_stripe_filter_vars', 'myprefix_stripe_filter_vars');
function myprefix_stripe_filter_vars($vars){
unset($vars['zipCode']);
/* or alternatively */
$vars['zipCode'] = 'false';
return vars;
}

– hmm, i wonder about the following though (not a too common scenario i would think but not impossible either):
what happens if i have a UK credit card and bank account. I then move to another country – let’s say Spain – and change the address associated with this account/credit card – as i would have to.
therefore my postcode changes from something like ‘SW6 1AB’ to ‘071234’ ….

I would have thought it’s still a UK credit card (UK Bank), but the zip/postcode has a different validation structure now.
Admittedly, the chances are also quite good that i would also have “proper” credit/debit card associated with a spanish bank and postcode, but still….or maybe stripe is clever enough to be able to work out this kind of thing too. (the validation rules in the gateway implementation are set by stripe , not by me btw)

again, just thinking out loud here…and it’s probably still a lot safer to insist on postcodes that match the card-country even if it means perhaps loosing a customer or two (though – as mentioned above – the chances are they will also have alternative ways to pay)