
Login Testing & Data Extraction Automation
- or -
Post a project like this29
$10/hr
- Posted:
- Proposals: 15
- Remote
- #4500240
- Open for Proposals
WordPress & Shopify Developer | AI Chatbot Automation Expert | Web Scraping | Automation | Data Extraction
Full-Stack Developer | AI-Powered Web & Mobile Apps Automation Expert + AI developer + Dev-Ops | Top-rated
Instagram Marketing | Amazon Private Label | Social Media Manager | AI Chatbot & Automation

134215011227545510548737118184561342885890627891298795568876376460111294277194077481358376
Description
Experience Level: Entry
Deadline is 23.00. 2026-06-05.
We are looking for an experienced automation developer to build a solution that can process a list of authorized test accounts, verify login credentials, and extract specific account information for reporting purposes. The project is intended for legitimate QA, testing, or account-management workflows and must comply with all applicable laws, platform terms of service, and authorization requirements.
The tool should accept a CSV or TXT file containing usernames or email addresses along with passwords. It should attempt to log into each account, determine whether the login was successful or failed, and record the result. For successfully authenticated accounts, the tool should collect available information including shipment totals, country counts (for example, GB: 2, US: 9), account type (Individual or Business), account status (Active or Inactive), account country, account address, company name, and whether an active payment method is attached to the account.
The solution must not collect, display, store, export, or process any sensitive payment information. This includes credit card numbers, expiration dates, CVV codes, bank account details, or payment credentials. The only payment-related information that should be returned is a simple Yes or No indicator showing whether an active payment method exists.
The final output should be provided as a CSV report containing the username, login result, shipment total, country count, account type, account status, account country, account address, company name, payment method present (Yes/No), and any notes or error messages encountered during processing.
OB2 is the preferred technology, The solution should include proper error handling, retry logic where appropriate, clear documentation, and complete source code delivery.
The final deliverables should include the full source code, setup instructions, documentation, an example output CSV file, and a demonstration using authorized test accounts.
We are looking for an experienced automation developer to build a solution that can process a list of authorized test accounts, verify login credentials, and extract specific account information for reporting purposes. The project is intended for legitimate QA, testing, or account-management workflows and must comply with all applicable laws, platform terms of service, and authorization requirements.
The tool should accept a CSV or TXT file containing usernames or email addresses along with passwords. It should attempt to log into each account, determine whether the login was successful or failed, and record the result. For successfully authenticated accounts, the tool should collect available information including shipment totals, country counts (for example, GB: 2, US: 9), account type (Individual or Business), account status (Active or Inactive), account country, account address, company name, and whether an active payment method is attached to the account.
The solution must not collect, display, store, export, or process any sensitive payment information. This includes credit card numbers, expiration dates, CVV codes, bank account details, or payment credentials. The only payment-related information that should be returned is a simple Yes or No indicator showing whether an active payment method exists.
The final output should be provided as a CSV report containing the username, login result, shipment total, country count, account type, account status, account country, account address, company name, payment method present (Yes/No), and any notes or error messages encountered during processing.
OB2 is the preferred technology, The solution should include proper error handling, retry logic where appropriate, clear documentation, and complete source code delivery.
The final deliverables should include the full source code, setup instructions, documentation, an example output CSV file, and a demonstration using authorized test accounts.
Marco Antonio C.
100% (1)Projects Completed
1
Freelancers worked with
1
Projects awarded
31%
Last project
17 Apr 2026
Japan
New Proposal
Login to your account and send a proposal now to get this project.
Log inClarification Board Ask a Question
-
There are no clarification messages.
We collect cookies to enable the proper functioning and security of our website, and to enhance your experience. By clicking on 'Accept All Cookies', you consent to the use of these cookies. You can change your 'Cookies Settings' at any time. For more information, please read ourCookie Policy
Cookie Settings
Accept All Cookies