You can solve for that by having short validity of the offline tokens on device and having that equal the cool-off period for reclaiming those funds when new device is provisioned. If I had ₹100 unspent tokens in my offline capable device that I lost, and got a new device provisioned the same day, then that ₹100 will show up in my account and be available to load on my device only after, say 7 days, of cooling-off period. In those 7 days, if someone who found your device could spend it and if so you lose it. If you know you are likely to be offline only sporadically for few hours and not for days, you can reduce the validity (and hence cooling-off period) significantly to just 12 or 24 hours.
Who would accept "provisional money" though, if there is a realistic risk of it being double spent and therefore effectively worthless?
> Double-spends will happen in any system that allows offline transactions
Only if you assume untrusted devices. That's why in most past and existing stored-value systems, smartcards are being used – these have different security properties.
It's up to the receiver whether they want to walk to the internet cafe and connect to verify it, or if they just trust the person they got it from.
If all the devices are trusted, but can be lost/destroyed and re-issued, you have the same problem.
But these aren't mandatory: Physical cash also can't be replaced when lost, and only rarely when physically destroyed. That model might be preferred in some scenarios.
Then the users and merchants can decide if they wait to click the verify button. And the default for anyone with data connectivity should probably be auto-verification. There is an incentive to verify, because if any double-spending has happened, the first to verify is the one who gets the money.
Double-spends will happen, because a user has to be allowed to log into a new device (if they lose their old one), and there is no way to know if the money spent from their old device was synced to the server yet.