Over the last year DeckBooks has grown in leaps and bounds both feature wise and the huge surge of telephone enquiries from new users. Firstly I would like to thank all of you for choosing DeckBooks for managing your business and making what it is today.
Over the last 6 months we have added extra server capacity and rewritten many parts of the code to better perform with our ever growing user base. Due to the amount of changes and new features we have decided to scrap v1.5 and push our v2.0 of DeckBooks which we have been working on locally and in secret since the release of v1.3 in November 2012.
v2.0 has hundreds of new features as well as running on a new codebase which will expand on our current module system as well as allow you to work alot more efficiently and brand your whole DeckBooks experience for your clients. I cannot show anything at this point in time but I will keep posting regular updates when major features become complete and are ready for public viewing.
Some of the new features for v2.0 have already been previously announced for what was v1.5 such as custom branded domains, payment gateway support and website integration. Yes they are all still coming but bundled in v2.0 which we will slowly be rolling out to beta testers for feedback and refinement as development progresses.
For now enjoy v1.4.5 (which was released today), and if you have any questions or concerns on v2.0 feel free to post on http://community.deckbooks.co.uk/, but we can guarantee you will all love v2.0 when it becomes publicly available later this year.
Firstly we would like to apologise for the delayed release of v1.4.5, this is due to it having numerous backend changes and foundation updates ready for the next release which will be a very significant update with hundreds of new features as well as the usual improvements.
v1.4.5 contained mainly foundation updates, bug fixes and performance improvements. This release contained:
On 7th July 2013 DeckBooks achieved PCI compliance under the PCI DSS standard. Since the initial beta launch of DeckBooks in November 2011 we have always been committed to excellence in security standards and data protection, providing peace of mind to our users.
Over the past few months we have been been doing a lot of work behind the scenes to make DeckBooks completely PCI compliant (hence the lack of feature updates). We contracted a Qualified Security Assessor (TrustWave) to guide us in becoming PCI compliant and now we have achieved compliance (the nice shiny green badge you will see on the website and when you log into DeckBooks).
What is PCI compliance?
The Payment Card Industry Data Security Standard (PCI DSS) has been developed by the credit card industry to combat fraud. There are very strict requirements to the standard that apply to merchants that store, process or transmit cardholder data. DeckBooks uses SagePay to handle our online payment processing and new requirements by merchant providers such as Streamline now require compliancy with the PCI DSS. We have always built DeckBooks with security in mind but we have also introduced new measures to DeckBooks to ensure that we are compliant with the PCI DSS. These include:
- Enforcing strong passwords and storing them with 512-bit encryption
- The entire system is protected using SSL encryption
- Two factor authentication and account protection any important activity (account changes, logins, etc…)
- Ensuring that extremely strict firewall and security policies are followed
- Strictly controlled access to servers and customer data
- Ring fenced and ID controlled access to data center.
- All of our developers are trained in industry security standards
- DeckBooks undergoes regular security scans from an approved PCI scanner every month
What does this mean for users of DeckBooks?
From a user perspective you will not notice anything over than the PCI compliance badge at the bottom of DeckBooks when you log in; however you can feel confident in the peace of mind that we are keeping your data safe and secure and following the strict standards of the PCI DSS compiant standards.