Reply
Highlighted
Member
Posts: 1
Registered: ‎01-23-2015

Mobile User Purchases Best Practices

Hello,

 

I'm a developer working on an app for a library, and they would like to integrate the ability to pay library fines into their application.  They have requested that we do as much of the logic as possible from mobile device.

 

From my reading/understanding of the documentation it appears that the most we can do on the device is to collect the card information and (securely) post that information to the library's server (which is in PHP and already has Authorize.net integration), as the mobile SDKs are more for use to write merchant apps where the merchant uses the phone to swipe a customer's card.

 

One question I have is if there is any way to do more than this? For instance, is there an API that lets one directly post the card information from the device to an Authorize.net web service?  I've seen topics in the community that suggest using a mobile/responsive website, however those were almost a year old so I wanted to make sure such answers were still the recommended approach.

Highlighted
Posts: 2,765
Topics: 57
Kudos: 248
Blog Posts: 67
Registered: ‎12-05-2011

Re: Mobile User Purchases Best Practices

Hello @michaelAtClearl 

 

This would be done by using your PHP web server to generate an authentication fingerprint. As documented in our Apple Pay documentation this same authentication method can be used for regular transactions, but it is generally seen as more complex than simply running the transaction through the web server.

 

This will look something like this:

 

<merchantAuthentication>

  <name>API_LOGIN</name>

  <fingerPrint>

    <hashValue>HASH_VALUE</hashValue>

    <sequence>SEQUENCE_NUMBER</sequence>

    <timestamp>TIMESTAMP</timestamp>

  </fingerPrint>

</merchantAuthentication>