Integration and Testing

[Lilith Administrator]

@ohoppe Thank you for your API documentation feedback, it's very helpful.

I'd like to provide a bit of context for the In-Person SDK page. That page was created with a presumption that developers would naturally go to the SDK pages on GitHub and see the individual documentation in the README.md files. I'm sorry to say that presumption doesn't really stand, as you've rightly called out. Developers deserve a clear path to the documentation they need.

We're adding direct links to the README.md files, and they'll be in the orange Resources bar near the top of the page. That should make it a bit more clear where developers should go if they need more details. We have a new documentation release in about two weeks, at which point the links will be live on the page.

Your comments -- and comments from others -- are really valuable to us. They start conversations about how we can make our documentation better for our partner developers, and we're truly grateful for them. Again, thank you.

[sriniputla]

I am working on editing the credit card expiration date. With current API, along with editing the expirtion date, other options are provided to the end user to register new card. Is there anyway we could disable or not show any other links other than allowing user to edit the card expiration date?

[jtCarillon]

  I have been looking at the in person sdk readme https://github.com/AuthorizeNet/inperson-sdk-windows/ and it isn't as informative as the API Reference Guide https://developer.authorize.net/api/reference/. The API Reference Guide has input and output values and what each method does but the in person sdk readme seems to be lacking information. For example method "void requestSelectApplication(List<string> appList);" is mentioned to be one of startQuickChipWithoutUI's listener methods but it doesn't mention what it does or if it is always called when startQuickChipWithoutUI is called. Is there more informative documentation for windows in person sdk?

[Sean478]

All in all a very disappointing experience so far with this In-Person SDK for Android. Tried 3 different Android tablets with different (recent) Android versions and it would not work. You have no choice of hardware and the provided hardware only works (or tries to work) with the Audio plug which is apparently not well supported (yet) by computing devices for data transfer. And you cannot use it with a desktop PC running Linux which is not so uncommon in the POS world. And you seemingly cannot customize the UI or integrate it with your already existing UI. And the documentation is apparently lacking, far behind the API Reference.

[oyeusman1997]

I appreciate the quick response. I'm not using any of the SDKs. Building one of my own on Ruby with limited functionality.

[tricksfly]

This means in turn that Authorize.net has to be able to take the encrypted data, along with some key that's set using a totally separate process and stored internally on their end, and decrypt it. While there is a field in the Authorize.net CNP API for specifying a device, as far as I know, there is no support for proprietary decryption of this sort.

TRICKSFLY

[feedbacklive]

Thanks for sharing this valuable information with API Features documentation. website

[gavinter]

Hi,
You won't get any other custom fields for these APIs other than what is documented in the XSD for it .

Any reasons for not using our SDKs for it ? it will be much easier for you . Thanks