What is it?

A library to return the name and branding colour of a bank by the first few digits of a card number.  It will also help you generate CSS files to use.

What is it good for?

Changing the colours on a billing page to match the user’s banking colours, making you look impressively switched on (and maybe a little creepy).

Is there a demo?

There Sure Is.

What issues does it have?

There are only entries for users which have contributed them, so some banks will be unmatched (unless you contribute!).

Users may think you’re stealing their credit card information, despite the fact that they’re literally about to give it too them.

How do I…

Install it? npm install banks-db

Ensure my bank is present?  Like So.

Use it from Javascript?  Got you covered.

Get the docs and source?  Right Here.


Since writing your own UI elements from scratch is for chumps, I’ve been using jQuery to construct our new booking systems.  Lots of shiny there, all the better to Web-2.0 your social media with, my dear.

*{vomits a little in his mouth}*

I have a sortable list where each li element has an attribute storing object data.  An AJAX lookup supplies the data from a 3rd party source, and there can be 1..n li elements.  Calling serialize on that list allows me to get the ids of the list objects in their currently sorted order:

>>> $("#waypoints").sortable("serialize")


That’s OK, but I want to access the json data, not the ids.  I could put that data in a javascript array and then simply re-order it (or post the ids and the data separately and use the controller to order them), and I also could gouge my eyeballs out with a rusty spoon.  Thankfully, according to the docs, I can pass a hash to serialize specifying which attribute to return:

>>> $("#waypoints").sortable("serialize" {attribute: "json_data"})

"{"des_id":"a","des_name":"r","fleet[]=id":"5"}&  "{"des_id":"a","des_name":"r","fleet[]=id":"8"}

…Well that’s not what we what.  That’s weird, and what the fuck is going on with that inserted []?  Hmm, perhaps the key parameter is being clobbered and needs to be set as well (thus specifying what the first part should be):

>>> $("#waypoints").sortable("serialize" {attribute: "json_data", key: "waypoints"})

"waypoints[]=id":"5"}&waypoints=name":"8" }"

Nope, still fucked.  And weirdly escaped now, also.  I could use expression to create my own parsing regex, but I also could gouge my eyes out with a rusty spoon.  Into the source code, then, to see what the hell’s going on.

 serialize is defined on line 3365 of my copy of jquery-ui.js, and has this snippet:

$(items).each(function() {
    var res = ($(o.item || this).attr(o.attribute || 'id') || '').match(o.expression || (/(.+)[-=_](.+)/));
    if(res) str.push((o.key || res[1]+'[]')+'='+(o.key && o.expression ? res[1] : res[2]));

Ah.  That explains why I was getting that inserted [] in the last part of each value, and also why I wasn’t getting the full thing when I changed the key.  When I don’t pass an expression in, it chunks up the value by discarding the first group, and using the second.  In this case, everything up to the last underscore is discarded and the key used is everything before the last underscore, with a [] appended.  

When I supplied a key, it simply discarded the entire first matched group and returned the second.

So now I can solve my problem.  To parse an attribute containing underscores (or – or =) with serialize, I simply need to provide the attribute name, the key and a catchall expression, say, (.+):

>>> $("#waypoints").sortable("serialize" {attribute: "json_data", key: "waypoints", expression: "(.+)"})

"waypoints[]={"des_id":"a","des_name":"r","fleet_id":"5"}&  "{"des_id":"a","des_name":"r","fleet_id":"8"}"