Where to store financial transaction payment system?

Good day! Designing a payment system for internal payments between clients of the company.

Goal: to Provide 10 000 customers of the company the possibility of mutual settlements and transfers of funds between your accounts with a transaction speed of no more than 5 seconds in 80% of cases and a maximum amount equivalent to EUR 30 000 per day per customer.

The reliability requirement: the System must not allow more than 1 failure per 10,000 transactions with a maximum recovery time of 30 minutes.

I have different types of data:
Usernames and password hashes. The main risk: it is impossible to prevent loss of access to system owner
Customer data, personal data and reference data. The main risk: data Leakage.
Scanned copies of documents. The main risk: Slow entry and data extraction (large volume). Data leak.
Financial transactions. The main squeak: it is Impossible to prevent changes to the data. Thus it is necessary to provide an acceptable transaction rate. The data do not, under any circumstances, may be lost.
The event log (user authentication, user actions). The main squeak: it is Impossible to prevent changes to the data. The write speed should be high.
Application settings
Log files
Obedennyi management data (OLAP cubes, data marts)

The most sensitive issue for financial transactions. Where better to store them? Blockchain?
And most importantly - in the numbers to justify to justify the validity of the choice of solutions?
March 20th 20 at 11:44
4 answers
March 20th 20 at 11:46
Where better to store them? Blockchain?

Oh, this fashion.

The blockchain is a protection against fakes.
Assuming that someone will conduct themselves regardless of double transaction.
Thus, you do someone will not be able to cheat.

Will you be someone (an independent organisation/independent person)?
If not - then no blockchain, it does not benefit from buduet.

Otherwise - the usual neradovac server DBMS with synchronous replication, but at least PostgreSQL.
And the rank and file of the signature, even though the RSA algorithm
March 20th 20 at 11:48
Good question, long and detailed. We immediately see that you figured out what you need.

Designing a payment system for internal payments between clients of the company.

This centralized system such existed 500 years before the invention of the blockchain, since the emergence of banks (that I figure to substantiate threw).

Now go and shake the garbage out of my head. Maybe it will help.
March 20th 20 at 11:50
Where to store financial transaction payment system?
In the database.
Everything else is not a question, but a fairly large task that requires analysis of the situation and a decent amount of work.
In General, this is outside the subject of the resource.

The most sensitive issue for financial transactions. Where better to store them? Blockchain?
Database.
The blockchain if you want you can stick anywhere, but the described situation it is absolutely useless and has no meaning.
March 20th 20 at 11:52
Give the keyboard an adult. Not your it...

Find more questions by tags Information securityDesigning software