> For the complete documentation index, see [llms.txt](https://mih.gitbook.io/mine-holdings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mih.gitbook.io/mine-holdings/mih-whitepaper/card-application-guide.md).
# Card Application Guide
## 1. Select Card Application
**STEP 1.** Log in to the MINE platform and click the “Card Application” tab.
## 2. Save Card Holder Information
**STEP 2-1.** Select the card type and membership type, then enter the card holder information.
{% hint style="warning" %}
If a general member applies for a membership card, **the application may be canceled.**
{% endhint %}
**STEP 2-2.** Please complete the application form according to the required format.\
All fields must be entered in English.
{% hint style="danger" %}
Please enter your name and phone number **without spaces**, following the required format.
The email address must match your login email address. (**It** **cannot be modified or registered multiple times**.)
If the application form is not submitted in the correct format, holder approval may be rejected.\
(If approval fails, please correct the information and **submit it again**.)
{% endhint %}
## 3. Apply for a Virtual Card
{% hint style="info" %}
A virtual card is issued digitally on the platform without physical card delivery.
{% endhint %}
**STEP 3-1.** Select “Virtual Card” as the card type and choose the membership type.
**STEP 3-2.** Save the application information and click the “Next” button.
**STEP 3-3.** Confirm the deduction of 20 M.Cash and apply for card issuance.
**STEP 3-4.** Once the virtual card is issued, you can check the issued card in the “Card Management” tab.
## 4. Apply for a Physical Card
**STEP 4-1.** Select “Physical Card” as the card type and choose the membership type.
**STEP 4-2.** Confirm the deduction of 100 M.Cash and apply for card issuance.
**STEP 4-3.** Once the card delivery application is completed, a guidance page will appear.
**STEP 4-4.** When shipping begins, a card number input field will be created.\
After receiving the card, enter the card number and click the “Request Delivery Completion” button.
**STEP 4-5.** Once the request is approved, the “Enter Card Information” button will be activated.
**STEP 4-6.** Enter the card number and a 6-digit password, then click the “Send Code” button.\
A card activation code will be sent to your registered email address.
{% hint style="info" %}
The password (PIN number) you set is required for POS payments and ATM withdrawals.
{% endhint %}
**STEP 4-7.** Enter the 8-digit activation code received in your mailbox and click the “Register Card” button.
**STEP 4-8.** Once the physical card registration is completed, you can check the issued card in the “Card Management” tab.
## 5. Manage My Card
**STEP 5-1.** Click the “Card Management” tab.
**STEP 5-2.** You can check your card history.
{% hint style="info" %}
Up to 5 virtual cards and 5 physical cards can be issued per account.
{% endhint %}
**STEP 5-3.** Click the card and select “Detail” to view detailed card information and transaction history.
**STEP 5-4.** You can top up your card in the card detail management section.
**STEP 5-5.** You can change the 6-digit password (PIN code) you previously set.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://mih.gitbook.io/mine-holdings/mih-whitepaper/card-application-guide.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.