Google Pay via NFC rejects SELECT PPSE(2PAY.SYS.DDF01) - nfc

I'm programming kiosk application to accept contactless payments via device with NFC reader.
So far I achieved success with a number of Visa and Mastercard cards, and with Apple Pay.
But with Google Pay it fails on sending SELECT PPSE(2PAY.SYS.DDF01) APDU (device API function ExcangeAPDU() returns undocumented error number).
Does Google Pay support this command, or I should use something else to communicate with it? Or may be it requires some tricky initialization?

Related

Is there any restriction on the use of dji-sdk?

I want to know that whether there is any restriction on the use of dji-sdk?
Does the api provided in the SDK have a limit on the number of accesses,
is there a limit on the access time and is there a limit on access traffic?
Are the features provided by SDK completely free?
Can a mobile phone connect to multiple DJI devices?
If you pay the subscription fee, then there are no restrictions. If you don't pay the subscription fee then you are limited to a few devices registering for SDK access.
Yes, a single mobile device can connect to any supported DJI device and should work. Connections to devices are not limited if you don't pay the subscription but you are still limited to the number if devices you can register until the subscription is paid.

Codename one NFC Integration

There's a way from Codename One to provide access to Near Field Communication (NFC) ?
Anything new, out this post codename-one-nfc-beacon?
NFC is an Android only API and even there the availability in devices is "problematic". In iOS it's restricted to payment so there is no access to the underlying hardware. So there is no point in supporting the API in a framework that is designed for cross platform. I'm sure you can create a cn1lib similar to the fingerprint reader API or the SMS intercept API.

How to build an bulk sms sender or voip server?

I want to know how can I build my own Sms service provider?
In another say; What is needed to have a system to inject sms messages to the mobile network systems freely or is it possible at all?
with VoIP server we can do voice and video and text messaging through internet; but what about from internet to the land line or mobile network?
How Skype, smartvoip, etc. do this?
Please give me a direction that I could go through.
You need some sort of interface to the Mobile network to make this work. Your choices include:
build a system with a GSM/UMTS card or phone which you control to send SMS messages into the network. This will need a valid SIM and contract (and the small print may say that you are not allowed to use it to provide an IP to SMS service to others). If you google 'Asterix SMS Gateway' you can find several open source examples. You could also look at http://www.kannel.org/overview.shtml, although I am not sure how actively this is being maintained these days.
Build a front end for your SMS service and use an existing back end SMS service in whatever your target market is - i.e. connect directly to your local operators SMSC, most likely using SMPP protocol. This assumes the operator provides this service in your target network/market.
Use an SMS aggregator service such as MBlox or Clickatell

How to send a USSD Code to mobile phones

I want to send and run a USSD code on mobile phones via PHP. I have an SMS gateway, can I send it through SMS or do I need to purchase an other service? I have been searching the net and didn't come to a solution that's perfect for me.
Some company's support told me that I can send it using XML in SMS.
The USSD command I want to run is :
1. *21*___SOME NO____#
2. #21#
USSD and SMS are two different services that are both supported in 3gpp mobile protocols.
Check your documentation, or ask a support engineer at the organisation that supplies your SMS gateway to know if they also support USSD. If yes, then they should give you details on how to use it.
The interface to a USSD gateway is not standard, it will depend on how the individual company has implemented it.
A quick search on Google for the words "ussd gateway" brings up several USSD products.

Replying to an SMS sent from a modem of SMS service?

I am trying to implement my own theoretical SMS web service (just to understand how this stuff works, I have posted a few other related questions, I think this is it).
Set up a PC. It takes requests from a website I make to send out SMS messages: a user-entered destination phone number, and a user-entered text message
I get a GSM modem, or just a GSM phone. I connect it to the computer.
I get a service plan from Verizon or whoever, some sort of unlimited SMS messaging plan.
They give me a SIM card, which has my unique phone # attached to it (ex: 555-5555). I stick this in the GSM modem.
I get some application (like Kannel) which handles interfacing with the modem and sending out the messages from my machine.
Now users can visit my theoretical website, enter a phone # and message. I grab that data, forward it to Kannel. Kannel interacts with the modem, passing it the data for the message. The modem interacts with the carrier network I signed up with, and broadcasts the actual SMS to it. The carrier network handles routing the message to the actual destination.
This is my understanding of how it works. Now the recipient of this text message will see this message pop up on their device from my modem's number (555-5555). In fact, all the thousands of people using my service will all see the same origin phone number.
If that's so, how do these 3rd party SMS applications give people unique #s for replying to messages they send out?
For example, when I sign up for one of these 'free' SMS services on iPhone, they assign me a unique user ID, like '123'. My friend is on a normal AT&T phone plan. He can send an SMS addressed to '123', and somehow I will get the message. How does AT&T know to route that to this third party service? I can't imagine that they would somehow get a new SIM card with a unique phone number per user that signs up for their service!
Thanks for all your help.
Thanks
The cell network carriers (e.g. AT&T, Verizon) actually rent out custom phone numbers (called "short codes") to 3rd parties to use.
You usually can't acquire these short codes directly from the carrier, but you can go through a 3rd party company to rent the short code. I've worked with companies like MBlox and OpenMarket to use carrier short codes. These companies are sometimes referred to as "SMS/MMS messaging aggregators," because they aggregate messaging services across multiple carriers and offer them to people/companies like you. Most of the time the aggregator will expose some sort of API (SOAP/XML or binary protocol) to access the messaging services to send and receive messages.
There may be other ways to do it, this is just my experience.
I think your comment at the bottom of your message is misleading.
Your friend probably doesn't send a message to "123" infact he probably sends "123 hello george" to a central number, which in turns routes "123" on to you, behind the scenes.
FWIW, mobile messages can appear as though they come from anything (including, for example, a word, and not a number).
Your general underlying assumption as to how gateways work (acquiring simcards) is accurate enough.

Resources