topic Re: API documentation in Integration and Testing

API / Features documentation

Anurag — Sun, 15 Apr 2018 20:21:35 GMT

Use the features you want to build the payment solution you need.

You'll be up and running in minutes.

Features : https://developer.authorize.net/api/

SDKS : https://github.com/AuthorizeNet

API reference : https://developer.authorize.net/api/reference/index.html

Response Code : https://developer.authorize.net/api/reference/responseCodes.html

Re: API documentation

bsknowlton1 — Thu, 04 Jan 2018 05:17:46 GMT

I see that there is a schema definition one can use to pull fields. Is there a way to pull say a "custom" schema in which if custom fields were created for a particular instance and the schama can be parsed?

Apologies if this is confusing and I can clear it up if I need to. Rather new here.

Two APIs I'm using are in the transaction reporting (getSettledBatchListRequest & getTransactionListRequest).

Thanks in advance!

Re: API documentation

Anurag — Thu, 04 Jan 2018 08:51:51 GMT

Hi @bsknowlton1

Will need more details on it ?

Also are you using our SDKs for calling the mentioned APIs ?

https://github.com/AuthorizeNet

Re: API documentation

bsknowlton1 — Thu, 04 Jan 2018 16:56:24 GMT

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

Details, I'm doing a integration/transformation on the two methods above. The details in the documentation specify a concrete/static set of fields on the response, but was wondering if there could be custom fields returned and how I'd be able to get those fields on the fly.
** To note, I need to build the object definition for the end user to be able to transform and map across another system. So if a field isn't in the definition it won't show up.

Thanks again!

Re: API documentation

Anurag — Thu, 04 Jan 2018 19:51:51 GMT

Hi @bsknowlton1

We will not send 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

Re: API documentation

ohoppe — Sun, 18 Mar 2018 15:16:48 GMT

The API Reference seems not to include a reference for the In-Person Payments. Where would I find that, please? Searched all over your site, googled, no luck :-(

Thanks for helping!

Re: API documentation

Anurag — Mon, 19 Mar 2018 06:34:09 GMT

Hi @ohoppe

Have you seen the inperson feature page at https://developer.authorize.net/api/reference/features/in-person.html

Hope it helps .

Re: API documentation

ohoppe — Mon, 19 Mar 2018 12:56:07 GMT

Hi Anurag

Thanks a lot for your reply!

When clicking on the link it says, "Page Not Found". The only documentation I found was this page and the pages it refers to. But this is not thorough developer documentation as you find it e.g. on this API Reference page. And the documentation that comes with the In-Person SDK for Android is also nowhere near that thorough. In fact, when following the instructions given with the In-Person SDK it wouldn't work. The best "documentation" available so far is the sample app, but that doesn't explain the background (like that you seemingly cannot run this in a Background Service but need an Activity because the SDK will add their own Actvity e.g. for signature capture) nor does it provide details on the available classes, functions and their parameters etc.

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.

Would have expected better from Authorize.net.

Re: API documentation

Anurag — Tue, 20 Mar 2018 05:19:14 GMT

Hi @ohoppe

Thanks for your feedback . We have provided these inputs to the concerned teams .

The in person SDK readme file do have a section on using without UI .

https://github.com/AuthorizeNet/inperson-sdk-android#quick-chip-in-the-background

Below is a list of devices that Authorize.Net has tested and confirmed works with our mPOS Mobile Application/VPOS v2 Application and supported secure card readers. These readers support additional devices that Authorize.Net has not tested, but may work as well. Authorize.Net does not guarantee all device compatibility.

https://support.authorize.net/s/article/Authorize-Net-mPOS-Mobile-Application-VPOS-v2-Application-Tested-Devices

Also we will be launching the Chipper 2X BT pretty soon .

Hope it helps !!!

Thanks

Re: API documentation

ohoppe — Tue, 20 Mar 2018 13:44:50 GMT

Just checked on the supported Android tablets. The Samsung Galaxy Tab 4 10.1 and Tab 2 10.1 are both discontinued, and the Tab S2 9.7 is double as expensive as e.g. the Tab A 10.1 which is an outstanding tablet with 1920x1200 resolution, 2/16 GB memory, 1.6GHz octacore processor and up to 13h battery life. A standard EMV transaction works on this Tab A to the extent that it will always only authorize, but not capture. It will return "Transaction Declined", but the authorization was successful and capture can be done in second step via "regular" Authorize.net SDK (or REST call). Whereas the swipe (magnetic stripe) is not working.

Would be nice if this tablet could be fully supported also!

Thanks for considering! :-)

Re: API documentation

Lilith — Wed, 21 Mar 2018 15:14:16 GMT

@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.

Editing credit card expiration date

sriniputla — Sun, 29 Jul 2018 18:13:53 GMT

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?

Re: API / Features documentation

jtCarillon — Tue, 14 Aug 2018 21:21:00 GMT

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?

Re: API documentation

Sean478 — Thu, 21 Feb 2019 07:14:42 GMT

Re: API / Features documentation

tricksfly — Mon, 29 Nov 2021 18:16:21 GMT

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

Re: API / Features documentation

feedbacklive — Mon, 29 Nov 2021 18:17:52 GMT

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

Re: API documentation

gavinter — Tue, 02 Feb 2021 10:38:58 GMT

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

Re: API / Features documentation

FontsChoice — Mon, 29 Nov 2021 18:11:02 GMT

Thanks, found this helpful. Related question: Do you have any favorite 3rd party API documentation tools which can nicely display the endpoint description, code snipets, and navigation for a website developer module?