Hey everyone, happy new year! We've been hard at work making changes to Tokeet's payment processing and billings components. We have some big plans and lots of development in the works so stay tuned. Today I am excited to release the first step in our plan. Tokeet now automatically saves your guest's billing details from Booking.com and Expedia to your connected payment gateway. We currently only support Stripe, but this too will change in the near future.

So now when a guest enters their credit card details when booking on Booking.com and Expedia Tokeet saves this information into Stripe for future use. You may automatically charge this card from any invoice using the new 'Pay with saved card' button located directly in the invoice. You never have to leave Tokeet to charge your guests and you may issue new charges for additional invoices directly from Tokeet.

We plan to enable this feature for every new payment gateway which we integrate into Tokeet. If you have a preferred payment gateway please let me know so we may consider it for integration.

Fixed a bug affecting promotional rates which caused the base rate to take effect at the end of any promotional rate.

If you have specific currency requests please let us know and we can added them.

Fixed bug which prevented previous years from being selected in Tokeet Reports. Now you may select from 2016 forward.

If you've been seeing some illegible characters in your messages then rest assured we're working on resolving these. It's been an annoying issue that pops up every now and then as we try to manage encoding across all the message mediums.

The issue is that Tokeet was built to be multi-language. As such it must be able to handle all UTF-8 characters across the various languages. This seems simple, however as your message moves from the DB to the API and then out to the various channels (Email, SMS, Airbnb, Booking.com, etc) we must change encodings, strip some encodings, translate from UTF-8 to HTML encodings, from language-specific unicode to other forms, and so forth. This has resulted in a whack-a-mole type issue where we are constantly finding new, unhandled scenarios.

Please hang in there with us as we try to get this correct.

We've just added search and filter functionality to the Channel Details page. For those users who have lots of connections in any single channel you can now search for your connection via the channel property name. You may also filter linked and unlinked connections so you can find those new properties and get them linked quickly.

We've added a filter to the rental rates so that you may select to show rates of a specific category only. This helps if you have lots of rates and want to edit a set category. The filter will hide rates from any other category which leaves you with a cleaner and less confusing table to manage.

We've updated the message and activity feeds so a user will not see feed items that are restricted to them.

We've fixed a few reporting bugs. There was an error in the calculation of utilization across multiple rentals. Also, please note that revenue is attributed to the month a booking starts. So, if a booking spans two or more months, all revenue will be attributed to the first month. Finally, all rental-related metrics will use the current count of rentals in your account. So, utilization calculations are based on the current count of rentals and do not consider when a rental was actually added to your account and available for rent. This will cause the numbers to be off if you frequently add/remove rentals throughout the year.