I’ve been playing around a bit with the Android/Chrome implementation and trying to imagine how the Dutch payment method iDeal could fit into Payment Handler. For those unfamiliar with it: it’s the most popular way of paying online in the Netherlands (57% market share) with over half of transactions being done on mobile (source: Currence, the company that owns iDeal).
The simplified way it currently works for ecommerce:
entranceCode
, purchaseID
and the merchantReturnURL
) by the merchant on the iDeal network (gateway/acquiring bank). The response contains a issuerAuthenticationURL
, purchaseID
and transactionID
.merchantReturnURL
which can be a website or native mobile app link. The ec
(entranceCode) and trxid
(transactionID) fields are appended in the query string that allows the merchant to retrieve the initiated iDeal session for a purchase and the transaction status.As it currently stands, it seems that Payment Handler could work with Dutch banking apps on Chrome/Android with no major changes to UX and use the same fields in the PaymentHandlerResponse details.
For service workers things are less clear for me:
Hope this makes sense!
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.3