Merchant UI and payment integrator

The aim is to develop a unique payment software that is like sofort. Using technology like REST API. It is necessary to develop a whole merchant administration. It should be possible to create a reseller in the merchant administration. Reseller should have an overview of volume of transactions from their customers. It is necessary to create a API for the reseller, that they are able to generate an invoice for their merchant. The API for reseller needs the function readout number of transactions and volume of transactions in the period X of the own merchant. It should be possible to consign different fees for each merchant. There are two types of fees. One fee per transaction and a percentage fee per volume of transaction. We need our own API between us and the customer, because the payment will be carried out by the fintecsystem API. The customer shall not see that the fintecsystem API is used. Everything that is related to the transactions will be supplied by the fintecsystem API We will supply a mechanism there is no need to create one. Only a positioning of the number of transactions and the volume of transactions and the fees is required. The whole system should be multilingual. This means that it should be possible to choose different languages later. Enclosed a list of requirements and screeshots how the merchant administration could look like:  Merchant Cockpit Provision of a system for the merchant to manage the mode of payment XYz Dashbord For the first overview, encloses values : transactions today, volume of transactions today, transactions total and volume of transactions total, follow up chart of transactions ( something nice to look at) b) search for transactions offers a list of every transaction from a customer in the system and it should be possible to filter depositor, IBAN,BIC ( sender and/ or recipient) transactions_ID, date The results are shown in a list. transaction_ID, sender account, details ( reference, value) and date. The transaction will be linked to the transactions details, where additional status, mode ( test, live) and the webhooks ( merchant server notification ) are listed. c) configuration For the operation of the system the merchant has to do just a few settings: success link URL, whereupon the system will send the paying customer following the payment termination link: if he wants to cancel the payment webhook: URL, where we send the dataset of the successful transaction (server - to - server) It is necessary to create a unique API key that the merchant will be able to communicate with our API. Indicate the API key for the idenfication fo the merchant at Global Humax Pay All data should be saved on a MySQL database. d) account administration change password change master data e) login/ logout functions f) registration registration option for the merchant on the landing page entry form for relevant data master data (address, AP, VAT ) debit entry data mandate text approval fixed deposited general business terms and DSHW (opt) data set transfer status initial "pending" 3. administration area development of an administration area Usermanagement Admin User transactions - list of customers with number of their transactions - list of reseller with number of their transactions - filter: month/year - additional as CSV export for further use at Global Humax accounting system customer administration list and option to edit customer master data activation/ work clearance customer registration with activation send an email to merchant with access data blocking function of a merchant (for example , termination) reseller administration -create and maintain reseller enclosed some screenshot how a merchant administration could look like