This is a followup question to my earlier question: Read and Write Card Details using a Smart Card Reader
I have got the SDK and gone through the reference manual and sample code. But the SDK mentions very low level details like turning light on or off, sending APDU commands, etc.
My requirement is to read the card data like member name, membership no., etc. which is stored inside the card.
My client has arranged the SDK from the vendor, but I am still no better at reading the data inside the card. Can anyone suggest what should I do next?
Also, how to find out the type of the card, i.e. whether its a MiFare card, or other PICC Card? There is nothing on the card to suggest this way or that way.
Thanks.
Apparently the SDK concerns the reader. However, you need substantial additional information concerning the card itself. Nobody here can help without that information. Still then the provider of the card has to provide documentation, where the data you want to read is stored, and which access rights are necessary to do so, which keys to use etc. It is very optimistic to expect, that everything to be known can be found out by looking at the card. Sorry, but your question is currently an invitation to guess based on no facts.
Related
Rather new to Bluetooth Low-energy devices, and having recently purchased a bunch of trackers off Amazon, decided to write a little application to see what type of information I can get from these.
The trackers are from a Chinese company, and they don't have a ton of information around advertisement information, so I'm playing by best guess here.
What I've been able to achieve so far, through Flutter Reactive BLE, is to find the devices by their ID (filter out additional noise I don't care about) and pull information like RSSI, Name and ID from it.
Now I want to interpret the manufacturerData object, screenshot attached of just one of them, and can't seem to get anything concrete from it.
I half assumed that reactive_ble would've stripped the leading checks and only supplied the the necessary portions of the data object that's relevant to interpret, however, this does not seem to be the case.
My first feel was to just convert this UInt8List to String utf8.decode(device.manufacturerData), however, this returns either a 1x spaced string or nothing at all.
I've tried using ByteData with a start of 3 and end of 4, and that's not very helpful either.
Is there something I'm missing in it's interpretation? I've read the Bluetooth spec and as I don't come from a CompSci background, is rather foreign to me, so would appreciate a layman response.
The first 16 bits (little endian) in manufacturer data contain the manufacturer id (Bluetooth SIG's web site has a list). The layout of the rest of the bytes are totally up to the manufacturer. If you can't guess what they mean, you'll have to ask the manufacturer.
I am working on a Mobile POS integration with Verifone E315. I am relatively new to this payment processing industry, so i don't know the nuances and how things work. Following are my questions -
I would like to know if Verifone E315 is just a card reader or will also take care of payment processing.
Also, can we integrate other payment gateways by just using the Verifone E315 as a card reader?
Is there any sample code available to read card data with Verifone E315?
How does Apple Pay integration works with Verifone E315?
Any help would appreciated.
payworks offers a SDK to do transactions with the E315.
Disclosure: I am a software engineer at payworks
I have worked with all sorts of VeriFone terminals from Tranz/Zon to Omni 3200, to Verix/VerixV and eVo (3740/3750, 3730/510, 570, and 520). Unfortunately, I am not familiar with the E315, but I suspect my answer will apply to it as much as it would to the other platforms (you may want to follow up with a VeriFone rep to make sure--I'm sure he/she would be very happy to discuss it with you if there is a chance you may be buying some more of their hardware).
All VeriFone terminals I have ever worked with are just empty hardware--you have to provide all the software in order to make it work. There are various companies (and I think VeriFone is one of them) that have already developed software for the terminals that will handle credit card processing and/or check processing. I have never done this, but I've seen them in use in in many stores. Alternately, you can write your own program which will include all user prompts, all communication to a remote server that will do the actual processing, all the code for printing receipts, etc. (this is what I do). Obviously, this is a lot more work, but it gives you all the flexibility you could want.
That really depends on what you are trying to do, but probably. We actually do something like this--we read card data on the terminal and then send that card data to a server which in turn connects with one of a variety of other platforms we have integrated with and it all works swimmingly.
Again, I'm not familiar with the E315 or its platform, but the SDKs for the other models have all come with lots of documentation including, in some cases, sample code here and there. Again, contact a VeriFone rep and see what you need to do to get access to their developer's web site, "DevNet".
Sorry--I'm afraid I don't know anything about Apple Pay.
I'm searching for a method to add DRM on ePub files programmatically. Anyone know how to do that? Maybe 3rd party software?
I added DRM with following things:
if ePub is coming from server, make zip file password protected and inside HTML pages you can encrypt via AES-128. For images also you can encrypt but you need to add more code on your reader part.
if you are encrypting images, then all images must be decrypted before you load HTML page in web or browser.
If you just want to protect your books from copying, then publish them through Amazon or Apple. As long as you don't select otherwise, those bookstores will wrap the books in DRM that allows them to be read only a limited number of devices belonging to the purchaser.
If you have some reason for wanting to worry about DRM yourself, then after carefully considering why on earth you'd want to, you'll need to find a vendor who can provide both the DRM technology and the reader (perhaps white-labeled for you) which knows how to read those DRM'd books. You see, DRM is useless unless there's a reader that can read the DRM'd books. And what's more, you need a back-end infrastructure to keep track of which devices belong to which person. There are vendors who provide such solutions. However, you'll end up paying them some of the money you were trying to save by avoiding Amazon or Apple.
The pricey Adobe solution mentioned by one commenter has the advantage that it is used by multiple bookstores/reading systems, including Kobo and Sony, so if you use it, then people buying your books can read them on any of these devices--albeit with an annoying step involving some software called ADE.
If for some strange reason you are thinking of building this entire infrastructure yourself, all I can say is, good luck.
More generally, even if you work through Amazon or Apple, it's well worth stepping back and thinking if you really want to do DRM or not. It's a natural human instinct to think, "By golly, I'm not going to let anyone steal MY book!!", but many of the people that might pirate a non-DRM'd book would not have paid money in the first place, so it's hard to say you're actually "losing" money. And someone who pirated the book might then Tweet or tell their friends about it and you'll end up selling more books than otherwise. Finally, someone who really wants the book without paying will crack the DRM anyway, as another commenter noted.
If you ever used Analytics in your apps, have you included information disclosing that you're collecting Information from them? Or do you omit this? It will be my first time using Analytics and I just wanted to hear your opinions on this.
Thanks.
Be transparent about it. Tell the user that you are collecting data, explain what you are collecting and give them the possibility to opt-out.
Currently there is a lot of talk about address books and photos being uploaded without user consent. You want to ensure that your users understand what you are collecting and that you respect them and their personal data.
You might want to look at Localytics. Their library is open source therefore you can see what data collected and you can enable logging to see what would be uploaded. Using their services would save you from setting up your own server.
The tagEvent: would be useful to gather where the users spend their time, there is probably no need to go for a paid plan.
It is almost always safe (legally) to use anonymous information. If you are collecting information and linking it to an email or an account, then you really should tell the people what you are doing.
No matter what, it would be best/required in some places to have a notice somewhere in the app that you are collecting data.
I want to be able to run queries locally comparing latitude and longitude of locations so I can run queries for certain addresses I've captured based on distance.
I found a free database that has this information for zip codes but I want this information for more specific addresses. I've looked at google's geolocation service and it appears it's against the TOS to store these values in my database or to use them for anything other than doing stuff with google maps. (If somebody's looked deeper into this and I'm incorrect let me know)
Am I likely to find any (free or pay) service that will let me store these lat/lon values locally? The number of addresses I need is currently pretty small but if my site becomes popular it could expand quite a bit over time to a large number. I just need to get the coordinates of each address entered once though.
This question hasn't received enough attention...
You're correct -- it can't be done with Google's service and still conform to the TOS. Cheers to you for honestly seeking to comply with the TOS.
I work at a company called SmartyStreets where we process addresses and verify addresses -- and geocode them, too. Google's terms don't allow you to store the data returned from the API, and there's pretty strict usage limits before they throttle or cut off your access.
Screen scraping presents many challenges and problems which are both technical and ethical, and I don't suppose I'll get into them here. The Microsoft library linked to by Giorgio is for .NET only.
If you're still serious about doing this, we have a service called LiveAddress which is accessible from any platform or language. It's a RESTful API which can be called using GET or POST for example, and the output is JSON which is easy to parse in pretty much every common language/platform.
Our terms allow you to store the data you collect as long as you don't re-manufacture our product or build your own database in an attempt to duplicate ours (or something of the like). For what you've described, though, it shouldn't be a problem.
Let me know if you have further questions about address geocoding; I'll be happy to help.
By the way, there's some sample code at our GitHub repo: https://github.com/smartystreets/LiveAddressSamples
http://www.zip-info.com/cgi-local/zipsrch.exe?ll=ll&zip=13206&Go=Go could use a screen scraper if you just need to get them once.
Also Microsoft provides this service. Check if this can help you http://msdn.microsoft.com/en-us/library/cc966913.aspx