Payment API used not in a Web Application [ Edited ]

[#1]

Hi,

I've read through Payment API documentation and seen some posts on the topic here but still it is not clear for me if it is possible to use Payment API in a standalone, not web application.

In other words - is it possible to create new transactions without having a browser and redirecting user to external pages?

Example -  a windows desktop/native mobile application where users can purchase goods by entering their AT&T account credentials.

Thanks,

Alex.

[#2]

Hi Alex,

Technically, you don't need a browser, however it would very cumbersome without one. When the end user is redirected for consent (between end user and AT&T), the interaction is browser based. That's the part that is tricky without a browser. So, realistically at least this part would have to be browser based.

Hope that helps,

     --brett

[#3]

Hi Brett,

Thanks for such fast feedback!

So if I've understood you correctly, when performing a payment user needs to do concent (i.e. confirm that he allows our application to perform payments using his AT&T account).

Using current API version this can be done only using browser, correct?

Could you please give some direction as for technical aproach that can be used to perform payments from native applications?

Thanks,

Alex.

[#4 · Accepted solution]

Hi Alex,

I haven't done this myself, but I believe some platforms have embeddable browser widgets. I think Android has this, and I think iOS. So, you might be able to embed that in the application, and call that widget when the consent flow is perfromed.

Again, I haven't tried this, but I think something like that would work. You really just need something that will render the HTML properly so that the end user can interact with it.

Hope that helps,

    --brett

[#5]

Hi Brett,

After quick investigation we were leaning towards "embedded browser" solution also. I just wanted to make sure that we haven't missed some easier way of implementing this.

Thanks for your help!