2 ms·

Problems off the top of my head: 1) standard bank transfers often aren't instantaneous (idk about Germany) 2) no support for handling disputes etc. 3) banks can

Problems off the top of my head: 1) standard bank transfers often aren't instantaneous (idk about Germany) 2) no support for handling disputes etc. 3) banks can simply try to block you if it ever gets traction 4) a lot of friction, no mobile support 5) it's hardly that much better than just having people do the transfer manually 6) you'll have to integrate across many banks UIs Can you even verify if the transfer really happened based on this csv info?

l5870uoo9y 9y ago
Thanks for the feedback. 1. The transfer is immediately registered as a transaction on your account statement overview. 2. Yes, disputes would have to be handled by contacting your bank. I don't know the exact possibilities here, but would notice many complain about Paypal's polices too. 3. Yes, but don't see why moving customers away from other payment platforms to the online would be bad business for them. 4. Yes, no mobile. There are some constrains to it. 5. It is essentially just a manual that get verified by a third party. In principle you could pay online shops manually, but the problem is that the shop owner would have to manually verify it, that is reading through his account statements. This Chrome extension does exactly this. 6. To integrate you need to make sure the bank offers CSV data export with following the CAMT format (or something similar). This is required by the bank SEPA agreement in EU. To verify a payment I reckon you need the following: amount, currency, account number and a token as payee note, see http://i.imgur.com/m1ltZNg.png http://i.imgur.com/m1ltZNg.png The unique token is generated by my server. Naturally there will have to be some testing with the different online banks. I have done many (failed) projects before so I am likewise critical.

2 ms·

Problems off the top of my head: 1) standard bank transfers often aren't instantaneous (idk about Germany) 2) no support for handling disputes etc. 3) banks can

by auganov 9y ago

l5870uoo9y 9y ago
Thanks for the feedback. 1. The transfer is immediately registered as a transaction on your account statement overview. 2. Yes, disputes would have to be handled by contacting your bank. I don't know the exact possibilities here, but would notice many complain about Paypal's polices too. 3. Yes, but don't see why moving customers away from other payment platforms to the online would be bad business for them. 4. Yes, no mobile. There are some constrains to it. 5. It is essentially just a manual that get verified by a third party. In principle you could pay online shops manually, but the problem is that the shop owner would have to manually verify it, that is reading through his account statements. This Chrome extension does exactly this. 6. To integrate you need to make sure the bank offers CSV data export with following the CAMT format (or something similar). This is required by the bank SEPA agreement in EU. To verify a payment I reckon you need the following: amount, currency, account number and a token as payee note, see http://i.imgur.com/m1ltZNg.png http://i.imgur.com/m1ltZNg.png The unique token is generated by my server. Naturally there will have to be some testing with the different online banks. I have done many (failed) projects before so I am likewise critical.