Re:Payment Request API
by jimktrains2 on Sunday September 17, 2017 @09:24PM
(#15272733)
Just a clarification, a credit card number is an iin, pan, and checksum.
Interesting that the post says the term BIN (vs. IIN) isn't commonly used anymore, but it's practically the only thing I've heard them called in the last 10+ years of ecomm dev.
Re:Payment Request API
by jimktrains2 on Sunday September 17, 2017 @09:59PM
(#15272848)
I've seen both. When I wrote the post all the docs from the gateways I had access to called then iin with a historical note on bin. I done have access to those docs anymore though.
Re:Payment Request API
by jimktrains2 on Monday September 18, 2017 @02:34AM
(#15273800)
I've seen both. When I wrote the post all the docs from the gateways I had access to called it the iin with a historical note on bin. I don't have access to those docs anymore, though.
Edit: I really need to check when posting from my phone
I don't doubt you, but as an example, the recent notification of BIN/IIN prefix additions for Mastercard uses BIN 19 times and IIN 2 times.
https://www.mastercard.us/en-us/issuers/get-support/2-series...
Re:Payment Request API
by jimktrains2 on Monday September 18, 2017 @01:36PM
(#15277853)
Interesting, maybe I should update that page then.
When it comes down to it, a credit card number is kind of serving double as a username and password for online payments right now. This new API has the potential to significantly improve upon the security of raw PANs.