[jdmichal]

When they say "bank", the term used in payments processing is "issuing bank", or more simply "issuer". The issuer is the entity that processes your application and issues you a card. They are responsible for approving purchases [0] on cards they issue and settling with the merchants.

So that list is basically the set of issuing banks which have done whatever steps are necessary to integrate with Android Pay.

[0] Typical flow looks something like this:

The merchant signs up with a payment processor who issues them a POS; this is the machine you swipe your card through. That swipe goes to the payment processor's network, which looks at the first 6 card digits, otherwise known as the Issuer Identification Number [1], and routes to the appropriate card network. For instance, any card starting with "37xxxx" is going to route to AmEx. The card network then routes to the issuing bank, who actually approves (or not) the transaction.

So POS -> Payment Processor -> Card -> Issuer.

[1] https://en.wikipedia.org/wiki/Bank_card_number#Issuer_identi...

[grahamburger]

I think the point I'm trying to make is that you don't need to be using one of those banks to be using Android Pay. I use Android Pay for tap-to-pay purchases regularly and do not use one of the supported banks. You can use Android Pay with any major credit or debit card.

[jdmichal]

I'll refer you to here: https://www.android.com/pay/#supported-networks

Note the verbiage on the second section of the supported issuers: "Add a card from any of these participating banks and continue to get the same rewards, benefits, and security of your cards."

I have a feeling that unless the issuing bank is supported, that Google is basically routing the payment through themselves. (Your responses on the other thread seems to confirm this.) So basically, Google bills your card directly, and they somehow route the money to the merchant. (Not sure what would the the "normal" way to do that; a bit out of my depth. I could probably ask people if you really want to know.) This means that, for instance, if your card gives a bonus for restaurants, and you use Android Pay and the issuer is not supported, that you likely will not get that bonus. Because according to your card the merchant is actually Google and not the restaurant.

So basically, Google is acting as a middle man in the transaction. They (somehow) pay the merchant in lieu of your card, then bill your card directly. This would not happen with a supported issuer; the payment would proceed as it normally would without Google and you get all your sweet, sweet reward points.

[grahamburger]

Thank you, my curiosity is sated :) I think the 'somehow' is pretty simple - I think they just provide their own CC number (or one they've assigned to me) to the merchant when I tap my card, and then charge me later.

Good point about the merchant specific CC points - it seems obvious that Google is losing out in this strategy because they're probably footing part of the merchant fees instead of passing them on to me (or the seller.) I couldn't think of a way that that would matter to me as a user, though.