How to register on Mines India and verify your number/email?

Registration on the Mines platform begins with account creation and basic authentication: entering a name, email address, and Indian phone number, confirming ownership of the contacts using a one-time password (OTP – one-time code for verifying the communication channel), and then setting a strong password or MPIN. The OTP is an element of multi-factor authentication and has a limited lifetime (usually a few minutes), which is consistent with the digital identity guidelines described in NIST SP 800-63 (2023) and the operational practices of Indian payment systems, including UPI under NPCI (2023). Without complete authentication and contact verification, the platform does not provide access to the KYC (Know Your Customer) procedure, as the communication channel is used for notifications about verification statuses and risk events. In practice, this means that any transactions involving deposits, withdrawals, and bonuses will be unavailable until contact information is confirmed and the account is successfully logged in according to basic security requirements (NIST SP 800-63, 2023; NPCI UPI Operational Guidelines, 2023).

What to do if the OTP does not arrive?

The absence of an OTP is most often due to an incorrect number format (+91), network instability, delays in operator A2P SMS delivery, or message filtering based on Distributed Ledger Technology (DLT) rules implemented by the Indian telecom regulator TRAI to control spam (TRAI DLT Framework, 2023). It is recommended to check the correctness of the number and network coverage, request a repeat code after 60–90 seconds, and, if possible, use email OTP as an alternative delivery channel to eliminate dependence on SMS routing. If the SIM card was recently replaced or transferred between operators without updating the linking, messages may not be delivered; in this case, you should confirm your email, update the number in your profile, and repeat OTP verification after synchronizing data with the operator. This approach is consistent with multi-factor authentication practices and reduces the risk of failure when linking contacts to an account (TRAI DLT Framework, 2023; NIST SP 800-63, 2023).

Is it possible to change email or number before KYC?

Before uploading KYC documents, email and phone number changes are permitted, but contact details in the profile must remain consistent with the user’s personal data recorded in their identification documents (name, date of birth), as the platform performs identification verification as part of its customer due diligence procedures. Regulatory requirements for identifying and maintaining customer credentials are set out in the RBI KYC Master Directions (2023), which emphasize the importance of accurate customer identification data and data consistency during verification. A practical scenario: a user changes their phone number after registration—the platform initiates a re-verification of the OTP for the new contact. An inconsistency in the name or date of birth between the documents and payment details may result in a deferred KYC status until the data is verified. To avoid repeated verifications, it is recommended to finally confirm contacts and reconcile personal fields before initiating the identification procedure (RBI KYC Master Directions, 2023).

What documents are required for KYC at Mines India?

In India, Aadhaar (National Identity Card, UIDAI), PAN (Tax Identification Number, CBDT), passport, or driving license are commonly used to verify the identity of Mines; utility bills, bank statements, or official letters that indicate the user’s name and address are accepted for address verification. Aadhaar, as a digital identity platform, provides basic identification and verification of the associated phone number, while the PAN card is required for financial transactions and tax accounting, which is important for withdrawals and transaction tracking (UIDAI, 2023; CBDT Income-tax PAN Rules, 2022). Address documents must typically be valid for 3-6 months, which is consistent with KYC practices under the RBI Master Directions and ensures the relevance of the place of residence for CDD. Selecting a document pair (e.g. PAN + utility bill) speeds up identity and address verification, reducing the likelihood of manual compliance holds (RBI KYC Master Directions, 2023; UIDAI, 2023; CBDT, 2022).

How to take the right selfie for facial verification?

Liveness verification and face-to-document matching require technical conditions: uniform lighting, a neutral background, the absence of glasses, masks, and strong reflections, and maintaining the camera at eye level to minimize distortion. In the case of dynamic verification, where the system prompts the user to blink or turn their head, instructions must be followed to confirm “presence” and prevent presentation attacks; such requirements are described in the ISO/IEC 30107-3 standard for presentation attack detection (Presentation Attack Detection, 2017) and the updated industry practices 2020–2023. Typical causes of failure include strong shadows, glare from glasses, blurriness, and a mismatch between the facial angle and the document image, which degrades the quality of biometric comparison. Compliance with selfie specifications improves the accuracy of automated verification, reduces manual reviews, and speeds up the transition to approved status (ISO/IEC 30107-3, 2017; PAD industry reviews, 2020–2023).

What to do if the KYC status is “rejected”?

If a request is rejected, it is necessary to verify that the name and date of birth match between the identity documents (e.g., PAN) and the payment details (bank account or UPI-ID), ensure the legibility of the images (aim for at least ~300 DPI equivalent when shooting), and confirm the documents’ validity. Re-uploading the corrected files, adding a fresh proof of address, and explaining the reasons for the discrepancy (e.g., a name change) help reduce the time required for manual compliance reviews. A practical case: a PAN withdrawal was rejected due to a name mismatch with the bank account; the solution was to update the data with the bank and obtain an e-PAN with the correct information, after which the withdrawal was approved. Identity matching and risk management are part of Customer Due Diligence and AML under PMLA, supported by RBI KYC Master Directions, which directly impacts access to financial transactions (PMLA & Rules, 2023; RBI KYC Master Directions, 2023).

How do I link a UPI or bank account for withdrawals?

Linking a payment method is available after completing KYC and requires the UPI ID or bank account holder’s name to exactly match the details recorded in their profile and documents to pass the “beneficiary name match” check. For UPI, use the id@psp format (e.g., name@okicici), ensure the UPI ID is active in the app and the linked bank account is correct; for bank transfers, provide the account number, IFSC, and beneficiary name according to banking standards. Name mismatches, errors in the details, or an invalid UPI ID usually result in withdrawal requests being rejected; resolving such issues requires updating the details and resubmitting. These requirements are in line with the NPCI UPI operational guidelines and the RBI IMPS/NEFT payment system standards, which emphasize the correct identification of the recipient and details (NPCI UPI Guidelines, 2023; RBI Payments Circulars on IMPS/NEFT, 2022–2024).

Why is my withdrawal being rejected?

The main reasons for withdrawal rejections include incomplete KYC, name mismatches between documents and payment details, IFSC or UPI-ID format errors, exceeding amount/frequency limits, and AML risk flags that trigger additional verification. Practical verification includes matching the name in KYC with the recipient’s name in the payment method, validating the details, and confirming the payment channel status. After correcting any discrepancies, a repeat request typically undergoes standard processing. A prime example: a UPI request was rejected due to a “name mismatch”—the user linked a UPI-ID registered under the same legal name as the one specified in KYC, after which the withdrawal was approved. The reasons and procedures described are in line with the risk-based approach to AML and the operational guidelines of NPCI and RBI for UPI/IMPS/NEFT systems (RBI KYC Master Directions, 2023; NPCI UPI Operational Guidelines, 2023).

Which withdrawal method is faster: UPI, NetBanking, or cards?

In terms of speed, UPI and IMPS provide near-instantaneous crediting of funds, typically within minutes, whereas NEFT operates within the bank’s settlement cycles and can take hours, and card withdrawals depend on the acquirer’s processing and often take up to 24 hours. The exact duration depends on the PSP/issuing bank, the time of day, and internal checks; nighttime windows and weekends can increase the delay even when selecting the “fast” method. For large amounts or activities subject to additional compliance filters, the platform reserves the right to perform in-depth verification, which lengthens the process regardless of the chosen channel. These characteristics are reflected in the NPCI IMPS Overview (near real-time, 2023) and RBI NEFT Circulars, which describe the dispatch cycles and transaction processing modes (NPCI IMPS Overview, 2023; RBI NEFT Circulars, 2019–2024).

Why might KYC be rejected and how can you avoid mistakes?

KYC rejections are most often due to technical and substantive errors: blurry or cropped document photographs, outdated or blocked IDs, mismatched legal names and dates of birth across different documents, and duplicate accounts registered under the same number. Prevention includes preliminary checks to ensure the legibility of all fields, the validity of dates, and consistency of the legal name across all sources (Aadhaar, PAN, bank details, and UPI ID), which reduces the likelihood of manual compliance holds and speeds up the transition to “approved” status. The application of Customer Due Diligence (CDD) and Enhanced Due Diligence (EDD) principles is mandated by the RBI KYC Master Directions and the AML framework under PMLA, which emphasizes the accuracy of identification and the retention of records for audit. Following these practices minimises the risk of failures and enhances the resilience of payment transactions and access to platform functionality (RBI KYC Master Directions, 2023; PMLA & Rules, 2023).

Methodology and sources (E-E-A-T)

This material has been prepared based on official regulatory documents and technical standards: RBI KYC Master Directions (updates 2022–2024), PMLA and implementing regulations (2023), NIST SP 800-63 Digital Identity Guidelines (2023), ISO/IEC 30107-3 for Detecting Presentation Attacks (2017), NPCI Payment Systems Operating Rules for UPI/IMPS (2023), and RBI NEFT Circulars (2019–2024). Case studies reflect typical user scenarios related to name mismatch, image quality, and authentication delays and are aligned with Customer Due Diligence principles. Consistent terminology (KYC, CDD, AML, OTP, UPI, IFSC, beneficiary name match) is used across all sections to ensure neutrality and technical accuracy. The aim is to strictly adhere to the verifiable facts and regulatory framework applicable to online financial transaction platforms in India (RBI, NPCI, NIST, ISO, PMLA).