Normally the way it works is getSubscriptionRequstParams sets the necessary form variables which get submit to the hosted payment page. The payment provider then establishes the recurring profile. When a recurring payment is needed the payment provider will charge the on-file payment method they used and send an IPN to CBSubs to let CBSubs know a payment was made, which is then processed to renew their subscription in handleNotification followed by _returnParamsHandler.

CCBill gateway has an extra feature though to not need IPNs and utilize its Datalink API. This schedules the renewals at CBSubs it self, which are processed by processScheduledAutoRecurringPayment.

The usage of payment tokens sounds more like Stripe though and not a hosted payment solution. So you may want to take a look at Stripe.

Yes, Stripe supports single payments and recurring payments. Not all the payment methods offered by Stripe support recurring payments though.

Correct, Stripe is for on-site payments. We do not have a tokenized hosted payment page solution. Hosted payment pages typically handle the entire payment process and simply notify CBSubs of a new payment using an IPN or CBSubs does a check with the gateway to see if the renewal was paid.

I guess the closest to that is the DataLink usage in CCBill. You're not going to find a copy-paste solution for implementing whatever gateway you're wanting. They are all different. You will have to study whatever closely fits your needs, or several in fact, then begin implementing from there. Gateway development is not an easy task.