3 ms·

It says something when traditional banks are basically the same price now and are almost as good in features (and many other card processors are cheaper, especi

It says something when traditional banks are basically the same price now and are almost as good in features (and many other card processors are cheaper, especially if eg you stick to a processor in the EU for EU cards) - I'm not sure why anyone would pick Stripe anymore, especially as they have just as many "hidden" costs as others (eg fraud stuff)

bryanrasmussen 4y ago
is one of the features that they're as easy to set up? on edit: actually serious question, have been away from this area for a while but thinking about making a personal project soon.
- throwaway67743 4y ago
  For quite a while they've been trying to emulate fintech style ease, and to some degree they have made it (although most still insist on their own hosted gateways, which is fine as SAQ D compliance is a real chore) - they do things like OOB webhooks etc, like Stripe/Paypal/whoever do, so really the flow and integration is pretty much the same edit: my experience only applies to UK (which were better and cheaper way before EU) and EU banks, the US is a minefield that actually is better avoided by just paying higher fees to a popular processor rather than deal with banks who think its the 1800s)
pancrufty 4y ago
Having seen many of these systems myself, I doubt they’re “almost as good in features.” My European bank (one of the largest in my country) doesn’t accept passwords longer than 8 characters. Imagine how bad the rest of the systems is.
- candiodari 4y ago
  If you're working with COBOL records then changing the number of characters of any field, or adding or removing a field is pretty much impossible. Which leads to funny questions at development time like "how many characters do we reserve in the customer record for the third child of the second wife of customer X, when they're remarried, this third child is not a child of the customer but there does exist an alimentation 'agreement' between the customer and their third wife". You must make this decision knowing that whatever your answer ... it can never be changed again. >500kb per record. And, of course, mostly it just has first and last name, address, birthdate and balance, nothing else. Makes the web look efficient.
  - 01acheru 4y ago
    Well... yeah, but no one on their sane mind would build the backend of a mobile app or of a web app in COBOL. Of course you can have all your COBOL and your mainframes down below rolling and churning like it's 1975, but the authentication of an app is layers up above in a totally distinct system. Or this or you're crazy.
- stefan_ 4y ago
  You will find there is often a big difference between logging into the account and making any change or transaction. Getting the password right might give you account details and some basic transaction history, but it won't allow you to transfer money without 2FA.
  - pancrufty 4y ago
    True, but you assume 2FA is implemented correctly and doesn’t have a bypass. What I’m saying is that they’re often poor at what they do, so I don’t put excessive trust in them.

bryanrasmussen 4y ago

is one of the features that they're as easy to set up? on edit: actually serious question, have been away from this area for a while but thinking about making a personal project soon.

throwaway67743 4y ago
For quite a while they've been trying to emulate fintech style ease, and to some degree they have made it (although most still insist on their own hosted gateways, which is fine as SAQ D compliance is a real chore) - they do things like OOB webhooks etc, like Stripe/Paypal/whoever do, so really the flow and integration is pretty much the same edit: my experience only applies to UK (which were better and cheaper way before EU) and EU banks, the US is a minefield that actually is better avoided by just paying higher fees to a popular processor rather than deal with banks who think its the 1800s)

pancrufty 4y ago

Having seen many of these systems myself, I doubt they’re “almost as good in features.” My European bank (one of the largest in my country) doesn’t accept passwords longer than 8 characters. Imagine how bad the rest of the systems is.

candiodari 4y ago
If you're working with COBOL records then changing the number of characters of any field, or adding or removing a field is pretty much impossible. Which leads to funny questions at development time like "how many characters do we reserve in the customer record for the third child of the second wife of customer X, when they're remarried, this third child is not a child of the customer but there does exist an alimentation 'agreement' between the customer and their third wife". You must make this decision knowing that whatever your answer ... it can never be changed again. >500kb per record. And, of course, mostly it just has first and last name, address, birthdate and balance, nothing else. Makes the web look efficient.
- 01acheru 4y ago
  Well... yeah, but no one on their sane mind would build the backend of a mobile app or of a web app in COBOL. Of course you can have all your COBOL and your mainframes down below rolling and churning like it's 1975, but the authentication of an app is layers up above in a totally distinct system. Or this or you're crazy.
stefan_ 4y ago
You will find there is often a big difference between logging into the account and making any change or transaction. Getting the password right might give you account details and some basic transaction history, but it won't allow you to transfer money without 2FA.
- pancrufty 4y ago
  True, but you assume 2FA is implemented correctly and doesn’t have a bypass. What I’m saying is that they’re often poor at what they do, so I don’t put excessive trust in them.