Chrome Extension for Receiving DCP Cash Payments - 3

Chrome Extension for Receiving DCP Cash Payments - Requirements General Explanation: The extension will allow payments with DCP Cash on any desired website. Site identification will be done through one of two options: either a site that embeds identification within it or a domain that is registered and verified in DNS. Upon entering a website, both options will be checked to ensure identification. The extension will display a message upon entering the site (on any page) but only once per visit. Additionally, a payment window will open on the relevant page. Registered users will have the option to fill in the following information on a dedicated website: Domain Page URL for displaying the message (default: entry page of the site, the first opened page) (marked with an asterisk, meaning all pages of the domain, zero implies none) The message will contain the words "Payment with DCP Cash is available on this site" (modifiable) and any additional information site owners may want to add, such as a 10% discount for DCP payments. Wallet owner's name Wallet identification The address where the payment window will be displayed (marked with an asterisk, meaning all pages of the domain) Payment message text LocalStorage path for the payment amount LocalStorage path for currency (USD, DCP, or STAS) The address to which the user's payment will be returned Reporting address for payments Option for security through the Arbitrator LocalStorage path for PurchaseId Invoice retrieval password Option to open without specifying an amount Option to open in a separate window When a user reaches the desired domain, a window with the message will appear after about 10 seconds. Wherever there is a LocalStorage path, you can use a placeholder tag to insert the actual value (the parameter name will change accordingly). When saving data, there will be an option to enter nested variables that represent LocalStorage paths, such as saving a return path that includes nested identifiers for transaction identification. All values are optional. There will be a tag on the website data that specifies whether it's required or not. The rest of the data will be required from the registration site. When a user arrives at the payment page (and this is the amount), either based on local storage or if it's set to open without specifying an amount, a window for transferring payment in DCP will open. This window will display the text according to the provided data, followed by "Amount to Pay," and at the bottom, a button that says "Pay with DCP." The extension will construct the appropriate link based on the provided data. Clicking the button will redirect the user to the wallet's payment page as described in the documentation. The support website will include registration, login, password recovery, etc. Registration will also include domain registration and all the aforementioned details. DNS verification (using a tag, no data verification required; using domain registration on the site will require verification). Recording all received payments. Option to delete a site from the database. (Open page:) A list of websites that support the application, with links, descriptions, and icons, based on their respective websites. The website code will be in React, while the server will use Python. I will need you to provide the code so that I can upload it to my servers. The extension needs to be responsive and mobile-friendly as well. The final payment will be made only after the code has been uploaded to the store and verified as correct. The payment can be divided into milestones Also, if you are interested in doing only the extension, without the server and without the registration site, that is also possible The idea is that anyone who has an e-commerce site can insert the tag into their code (or register through the registration site) Then receive payments for his products in DCP CASH Anyone who has the extension will be able to pay with DCP cash The general idea of the extension is that a website owner who wants to allow his customers to pay in DCP cash will be able to do so in 2 ways: If he has access to the code - he will embed the tag in the code and thus the extension will know how to activate the payment option (first milestone) If he does not have access to the code, he will register on the website and register the domain and thus the extension will know how to open the payment option on his website (fourth milestone) For this purpose, a website is needed where he can register (The website will also be used to track the transactions and update data) Distribution of milestones I divided the work into 5 milestones: First step: Implementing the serverless extension only receives data locally The extension will check every page that opens if it has the <dcp-payment> tag If so: We will check the attributes If it has msg_path, (Example: <dcp-payment msg_path="......" >), the message will open only if the address matches, if not, the message will open if the previous page displayed in the browser is not associated with the same domain The content of the message will be obtained from the attribute msg_text, if it does not exist the message Payment with DCP Cash is available on this site wallet_owners_name wallet_id payment_path payment_text LocalStorage_amount_path LocalStorage_currency_path LocalStorage_purchaseId_path returned_path reporting_path arbitrator invoice_retrieval_password open_without_amount separate_window An example of a tag with attributes: <dcp-payment msg_path="......" msg_text="" An explanation of each The extension should work fully already in the first stage, that is to present the data and refer to the wallet for the realization of the payment, already in this milestone, It will pull the data either from the tag embedded in the website or from the local store it will not need (at this stage) to receive data through the server The data for the link, at this stage, will be taken either from the tag or from local storage I will explain If a clothing store sells a shirt to a customer The identification of the seller's wallet, to which the money will be transferred, will be on the tag, as this is something that does not change in every transaction On the other hand, the amount to be paid varies with each transaction, so we will have to take it from local storage This is the dcp online wallet documentation for building a link to payment pages: [login to view URL] Second step: building the server Third step, building a client side service website Fourth step Expanding the extension in a way that will support receiving data from the server Step five Upload, run and check for correctness and fix bugs