A Major Blip in Blippy's Security

Create a vendor selection project
Click to express your interest in this report
Indication of coverage against your requirements
A subscription is required to activate this feature. Contact us for more info.
Celent have reviewed this profile and believe it to be accurate.
We are waiting for the vendor to publish their solution profile. Contact us or request the RFX.
Projects allow you to export Registered Vendor details and survey responses for analysis outside of Marsh CND. Please refer to the Marsh CND User Guide for detailed instructions.
Download Registered Vendor Survey responses as PDF
Contact vendor directly with specific questions (ie. pricing, capacity, etc)
23 April 2010


  • Jacob, this blip actually begs the question of who is responsible for this non-PCI compliance? The data exposed seems to be the transaction memo. So who is responsible? Blippy or their back end provider (Yodlee) or the bank/bank processor?

  • Thanks for your comments Guillaume. Agreed, fault could lie elsewhere. However the public goes to and that is all they care about.

  • [...] off - is it secure to provide my banking credentials to this site ? I think the Rudder and Blippy mishaps have taught us enough about this. This startup doesn’t have the bank-level security that [...]