Can I use transaction key instead of password to login the mobile device? (in person iOS SDK)

[hiren43]

Hello. I'm using this library for my iOS application which accepts card payments. I already have integrated code in my app but have some queries regarding authorisation with merchant account. I think it is compulsory to login the device using 'mobileDeviceLoginRequest' for performing transactions. This app will be used by our employees which must not know about the merchant credentials. So can't just I use API login id and transaction key to login the mobile device so it can perform transactions? I tried using transaction key in stead of password with no luck. I guess most of the SDKs don't need merchant credentials in the app, they just allow some key to authorise. How should I approach this?

[NexusSoftware]

See the post at : https://community.developer.authorize.net/t5/Integration-and-Testing/iOS-Device-Login-with-loginID-a...

[hiren43]

But there is a loophole. Apps will be used by employees. So they must not know about the merchant credentials(login and password) else they can misuse it. I still am not able to understand the role of transaction key. We should be using that instead of merchant's login data.

[NexusSoftware · Accepted solution]

Storing the API Login and Transaction key on the mobile device is not recommended, but instead use the Login ID and Password. This gives you the ability to remotely approve and disable individual devices within the Merchant interface.

The Transaction Key is like your personal Master Merchant Password.

[hiren43]

thank you for replying. I have created a new user and with new credentials, he is able to login to device(authenticate) now. But when do I need to use transaction key? While performing transaction, will it prompt user to enter transaction key? Can you explain that?