Driving payment card adoption with deeplinks, applinks, long cards, and autofill

kunle.app

19 points·kunle··6 comments

Couple points of feedback I'm interested in for this essay

1. Add card to autofill (feels so obvious, not sure why no one's done it): https://kunle.app/checkouttarget.html#/creditCard/4242424242...

2. Using Web3 models of authentication for credential exchange (I feel like this is simpler than typing in a card because every financial institution has a mobile app at this point? What am I missing)

3. Using a well known URL for credential exchange (similar to the well known URL scheme being proposed for password resets: https://w3c.github.io/webappsec-change-password-url/)

Is there a list of accepted best practices in this space?

I'm struggling to figure out push provisioning right now. The thing I don't understand is: why do I need a native mobile app? Why isn't there an HTTP API to add a payment card to Apple Wallet or Google Play?

Authentication - its Apple and googles way of knowing that the card is actually issued by a known app developer, linked To a real financial institution with the right relationship with a card network. Bc the AppStore is locked down Apple can do it this way more easily than on the web.

OP, the link does not work at the bottom of your post to subscribe to your mailing list.

EDIT: Might have been my ad blocker blocking the Substack email subscription iframe embed. Mea culpa. Chrome 93 with uBlock Origin. Might use an href to https://ayokunle.substack.com/ for "here" in the "please subscribe here" sentence in case the iframe isn't loading for some.

Good to know, should be fixed now if you enter and email and hit subscribe. Thanks for reporting. Mind letting me know the browser you're using so I can verify?

Reply on news.ycombinator.com