Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API assumes Issuer communication is OOB #447

Closed
cyberphone opened this issue Mar 3, 2017 · 6 comments
Closed

API assumes Issuer communication is OOB #447

cyberphone opened this issue Mar 3, 2017 · 6 comments

Comments

@cyberphone
Copy link

The current Web Payment API does the (implicit) assumption that interactions with the issuer is performed OOB. However, the Saturn payment authorization scheme uses a "conversational" mode where all "Wallet" communication goes through the Merchant. It is therefore incompatible with the Web Payment API. It might be worth knowing at least.

https://cyberphone.github.io/doc/saturn/bank2bank-payment.html#provuserresp

Why the Saturn Wallet only talks to the Merchant? Because it has considerable system advantages.

@marcoscaceres
Copy link
Member

marcoscaceres commented Mar 3, 2017 via email

@bentian
Copy link

bentian commented Mar 3, 2017

I think OOB=Out-of-band.

Out-of-band is activity outside a defined telecommunications frequency band, or, metaphorically, outside some other kind of activity.

@cyberphone
Copy link
Author

@marcoscaceres
Copy link
Member

marcoscaceres commented Mar 3, 2017 via email

@ianbjacobs
Copy link
Collaborator

Nothing prevents a payment app from communicating with other parties. That is neither required nor forbidden by this API. Payment service providers can communicate through multiple paths.

I am closing this issue. If there is a more specific issue with the specification we can revisit it.

@cyberphone
Copy link
Author

cyberphone commented Mar 3, 2017

Nothing prevents a payment app from communicating with other parties. That is neither required nor forbidden by this API

What I said (or meant at least), is that the API (particularly when used with native Apps), requires OOB calls for anything outside of the core API. Putting it another way: The API fits card-emulating Apps like Android Pay but may turn out to be less useful for more advanced schemes, designed from scratch (including Saturn).

OOB means that the invoking Web page is not in the process and may have to be dealt with through AJAX hacks. Multiple channels to the Merchant adds complexity.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants