News for hackers. Stuff that matters.

A comment on Root – Programmable bank account for software developers. Parent comment

Re:Root – Programmable bank account for software developers by RickS on Wednesday May 03, 2017 @12:22PM (#14257221)
Hey - I previously worked on a prepaid debit platform that worked slightly farther from the metal here (post-processor).

I'm interested in two pieces of data we couldn't get there, but that I had really high hopes for.

1) Dynamic merchant-type filtering before auth. For example, if tom has spent 50$ on food this month, all merchants that identify as "food" will fail auth on further transaction attempts. I'm not sure if these are still called MCCs outside of the US, or "merchant codes".

2) Level 3/line item receipt data. For example, instead of showing I spent 5.00 at QuikEMart, it shows 2.50 on soda, 2.00 candy bar, 0.50 tax.

Will your platform offer that level of control/visibility?

[ Parent | on HN ]
Re:Root – Programmable bank account for software developers by louwhopley on Wednesday May 03, 2017 @12:25PM (#14257266)
Hey RickS, they are still called MCCs :) (2) is a bit more tricky to get our hands on, at least in South Africa
[ Parent | on HN ]
Re:Root – Programmable bank account for software developers by RickS on Wednesday May 03, 2017 @01:59PM (#14258343)
Cool - is MCC identifiable as part of the auth process, in the way my parent comment describes (conditional auth based on MCC)
[ Parent | on HN ]
Re:Root – Programmable bank account for software developers by louwhopley on Friday May 05, 2017 @09:55AM (#14273422)
Yeah, MCC and a bunch of other information on the merchant (name, location, etc)
[ Parent | on HN ]