In Germany, there's the 'next-bike', and 'call a bike'. I have been waiting to add them until I have the new structure of the project figured out. At that point, they will be much easier to have, and less hacky.
The 'call a bike' system is interesting, and differs from the overall scheme of most bike sharing systems. You have to call a number, enter a pin, and then you get a code to unlock the chain. I find it pretty intelligent, but a bit conflicting with what I have currently running.
At the same time, both systems are really small in stations, but big in locations (as in, there are lots of cities). That's the main reason I have to not support them at the moment, and the main reason of rewriting the architecture of the project. I did not know the project was going to grow at the start, so every city is a different module, if possible, with some inheritance. The new architecture [1] will feature systems as instances, instead of a separated class, thus, making it trivial to generate instances on the run.
Not sure if I went too far with the response, hope it's useful.
[1]: https://github.com/eskerda/pybikes/wiki/architecture