Amazon is 4 in every $10 spent online in the US. They have a scale similar to Costco/WM who only got deals for/to break exclusivity. Amazon pays less than 2%, much less depending on card type. Manages fraud to about 6BPS on transactional basis. But the concept of the running a CC is not out of the question, but the economics/complexity don't align yet...
There are a tons of reasons to keep our signups closed for now. One non-obvious reason to most people is that it costs us money to lend out money to customers. Theres a ton of others we're working on solving in parallel too
Email me @ [email protected] I'd love to hear more, if you don't mind. We encourage people to use the physical card and just treat it as disposable if it ever gets skimmed/breached/stolen/lost. We made sure it impacts none of your other relationships :)
Email me at [email protected] and we can get you a code to apply :) We're working on broadening our underwriting criteria, but this is a complicated business overseen by an incredible amount of regulation, while also taking risk when we issue new lines of credit. Large banks throw around a lot of $ to make it work (a lot in this statement), but to start a new provider takes a lot of tactical decisions and iteration to grow in a safe and sustainable way.
Industry standard is about 10 BPS for affinity programs and a bounty for acquiring customers for the bank. No rewards program might make this one higher, maybe 70-110 but none more.
A better plan if you wanted to support Linux would be 2% cashback card that you donate all rewards to Linux.
Thanks will look into it. Some old janky JS we have from what is still our original marketing site at its core. This codebase is separate from all actual customer data/sensitive things, so it could use some JS best practice cleanup clearly (even though this might be a responsive CSS thing)
Both email and phone, but for full transparency we actually prefer email since it keeps a full log of conversations with consumers for both parties to have. Our card has a number on the back of it and a few other in-app spots have our number on it.
We seriously appreciate the thoughtful feedback. Email me, [email protected], if you want to learn/discuss more about why we made some of the decisions we made day one. It really comes down to resources and a team of 12 working against incumbents with teams of 1200+.
Working on native Android full steam now, but yep started with iPhone for now. Web is full responsive and have a ton of Android users using it and happy w/ experience. But point taken.
Fair point, problem is that theres no short answer here. We partners with a bank to get our own BIN (https://en.wikipedia.org/wiki/Payment_card_number), that when loaded onto the networks, gets routed to our core infrastructure. There are many ways to segment this BIN, randomly, PRIN(?), few other industry standards, and so when you want to issue a new consumer a new card # you use whatever your algorithm is, and assign it to that customers account (or whatever exactly your data model is).
So its 2/3rds BD to get setup, 1/3 enterprise engineering and a lot of integration work to get fully setup and running. Payments is the only trillion dollar industry where nothing is written down, we're working on changing that since we find a lot of the stories fascinating and so do most people we retell them to.
If anyone is in Oakland area and wants a primer, always happy to share, we spent 3 years learning industry and now its our time to start giving back.
In all honesty, the juice isn't worth the squeeze. When you put a battery into that form factor battery life is a big issue and keeping in sync with your phone really harms it. Add recharging and you have other tradeoffs, so EMV gets us 95%+ of the way there and we're happy not having to solve really hard esoteric challenges related to things like the Bluetooth stack for BLE use.