Hey Pat,
Usually, this is something that you would build on your end as it's not really a subscription-based model.
The idea here is that a customer signs up for your service and can fill their balance on their account. In your example, you charge them $50 and you keep track of their balance in your database. Every time they make a transaction on your service, you decrease their balance by the expected amount. If the balance goes below a certain threshold ($10) you then call the Create Charge API [1] to charge them the expected amount. If the charge succeeds, you increase their balance by the charge amount. If it fails, you email them to warn them about their low balance and ask them to come update their card details.
If you don't want to store this in your own database, you could use the `account_balance` property [2] on the Customer object [3]. You'd have to be careful in that case to avoid two separate requests trying to update the account balance at the same time as those calls are not atomic in Stripe. Otherwise a customer could use your service twice in the same second for example and you'd end up assuming the balance was $42 in both cases for example and incorrectly.
As for the name for this kind of "plan", I hadn't heard of "Fast Trak" and instead usually call this a "Pay as you go" service. It's fairly common in cities with public transportation such as London with the Oyster card. Hopefully you might get a bit more information or examples based on this other name.
Hope this helps!
Remi