in essence, regardless of how one does this, an address has to conform to a location google knows about .
i am aware that in some locations , google has not indexed housenumbers, so a validation will say it’s ambiguous, but there’s nothing i can do about this

what “all sorts of errors” exactly ?
and what do i have to do exactly to get those errors ?
(and a link to your site you are referring to please)

just a few things on a sunday night (monday morning actually) and in no particular order

– I don’t think it’s that easy for the average user to change their IP address (given that most people these days will have a static ip), so there are plenty of security plugin that let you block by IP to start off with

– >if there would be a mistake in the streets we would call the customer
and that “fake” customer who you just called – as you cannot know that the phonenumber belongs to the person the order is supposed to be delivered to – can simply say : “that’s all great, please deliver”

– furthermore, assuming that you will have had some “no pay” issue with certain addresses, one would think you have a list of those somewhere and if it looks suspicious , you simply pick up the phone (but the above still applies somewhat)

– additionally – as unfortunate as it is – fraud is part of doing business I’m afraid and the police is the right place to really contact in those instances.

– >we got a small percent of customers who are order some pizza and then refuse to take or pay the order
again, that’s for law enforcement to deal with. there’s nothing the plugin can do (but as mentioned, if you were to only accept credit cards, that won’t be an issue, though that’s your/your boss’s decision of course)

– regarding GDPR/Privacy etc : this is pretty much irrelevant here as you are perfectly entitled – in fact, in most cases even required – to collect customer information (called something like “legitimate business interests” ) and the plugin does collect ipaddress, browser parameters etc , regardless (though can be anonymised on request at a later stage)

anyway, I think that’s it from me on the subject for the time being

blocking streets , surnames etc etc is i game you cannot win, as i only have to -deliberately – mistype things slightly and your block will not work so you have to forever add things

one option is this
https://www.wp-pizza.com/downloads/wppizza-confirm-reject-notify/
which allows you to reject not-yet-paid orders (among a number of other things like requiring confirmation of a not yet paid order)

simplest thing however is to just not accept cash on delivery or similar orders at all and only accept orders that were prepaid (credit card/paypal or whatever)

unless people use stolen credit cards (not much you can do about that) it will stop fake orders for good as people have paid up front

PS: please do not send the same question 2x.
it confuses the issue and will not get you support more quickly (in fact, it’s more likely to be the opposite)

Note: as of september 2018 a plugin exists for this sort of thing
https://www.wp-pizza.com/downloads/wppizza-mailinglists/

sounds like a rounding issue somewhere perhaps ?! (just guessing though)
can you post the whole stripe POST /v1/charges output here (make it a private reply)
maybe we can see something there to start off with

thing is, if 1889 does not match 1890 (presumably the actual order value) it should throw some errors somewhere before it even gets to stripe (i.e the 2 amounts must match EXACTLY)

that’s just off the top off my head at the moment (haven’t come across this before )

furthermore – are you willing and able to get out some info out of the wppizza orders table ? (not everybody knows how to access database table data so am asking first of all)

in theory , one can do all sorts of things.
however, if you are referring to the Coupons/Discounts plugin in particular, then I’m afraid , that’s not implemented there (and there are no plans – at the moment at least – to do so)

I’m afraid there are no “prepaid voucher” or similar options/extensions/plugins available at this time.

At some point in the future, this kind of option/plugin *might* be made available/possible, but as of writing , I cannot tell you when – or even of – this might be implemented.

Sorry