Preparing details for registration, verification and first issuance
Register using the current email, email-code and password fields. Before first issuance, submit your genuine identity details and complete required checks. Registration, identity verification, funding and issuance are separate states; submission is not approval or immediate issuance.
Information for registration and issuance
Register using the current email, email-code and password fields. Before first issuance, submit your genuine identity details and complete required checks. Registration, identity verification, funding and issuance are separate states; submission is not approval or immediate issuance.
- Prepare your own email
- Use an email you can continue accessing for codes and notifications, not someone else’s inbox.
- Check genuine details
- Enter name, document type and number, birth date and other requested fields accurately.
- Check each stage
- Confirm verification, then separately check deposit credit, issuance orders and actual card status.
Registration establishes login access; pre-issuance identity verification checks holder details. Prepare email, code, password and your genuine identity information under the current prompts.
Registration does not prove identity approval; approval does not prove credited funds or completed issuance. Check the original record for an unfinished stage rather than create accounts, duplicate deposits or repeat orders.
Different roles of prepaid funds and identity checks
Pikabao Virtual Credit Cards use prepaid funds rather than bank credit repaid later. That does not mean no checks or guaranteed issuance: identity, eligibility and security requirements still apply.
| Stage | Check | Do not infer |
|---|---|---|
| Registration | Email, email code and password | Completed identity approval |
| Identity verification | Genuine details and review outcome | Approval on input or permanent exemption from additional details |
| Two-step verification | Prompts for the current action | Document authenticity or merchant eligibility |
| Issuance | Fees, funds and issuance order | Acceptance by every merchant |
Names, document details and birth dates serve identity checks; tools such as Google Authenticator check access. A valid code does not prove identity approval or merchant payment authentication.
Prepare email, verification codes and a password
Choose an email you can keep accessing and check it character by character. Temporary, shared or borrowed inboxes can complicate recovery and privacy.
Request a code through the page. If missing, check the address, spam folder and send status. New requests may invalidate old codes; follow current prompts and the latest valid email instead of resending indefinitely.
Use a unique password rather than reuse exchange, email or merchant credentials. Enter passwords and codes only on verified official pages; do not send them to support or publish screenshots.
Genuine identity details and verification prompts
Check current requirements for name, document type and number, birth date and other fields. Document formats and name order may differ from the form; follow field instructions without changing genuine content.
If a form separates year, month and day, split the document date accordingly. For alphanumeric numbers, check case, spaces and character width under the instructions. Do not change identities or borrow details to test approval.
Later checks, additional details or reverification depend on current pages and official notices. Do not assume every detail is submitted only once forever. During manual review, retain and track the original request.
References and operation links: Checking identity-verification failures and review records
Review data purposes, retention and privacy
Before submitting, review collection scope, purpose, retention and contact channels in the privacy policy. Use designated official channels, not private requests for extra document images or authenticator recovery details.
| Data | Check the purpose | Your action |
|---|---|---|
| Login, codes and notices | Maintain secure inbox access | |
| Identity fields | Identity and eligibility checks | Submit only your required genuine details |
| Verification information | Confirm access for the current action | Do not share codes, secrets or recovery codes |
| Submission record | Tracking and reviewing exceptions | Keep IDs and masked error screenshots |
Data processing and fund handling are different matters. Encryption claims or legal links alone cannot establish zero leakage risk, deposit protection or universal compliance. Use verifiable policies for specific commitments.
References and operation links: Hong Kong Privacy Commissioner for Personal Data · An Overview of the Personal Data (Privacy) Ordinance (external source, for verification only, not an endorsement) · Privacy Policy
External materials explain general rules; they do not endorse Pikabao’s qualifications, rates or particular processing outcomes.
Track the stages from registration to the first card
After registration, check account status and submit genuine identity details under issuance prompts. Use the actual result, not a redirect, email code or submitted form, as evidence of approval.
Check supported deposit networks, addresses, receiving minimums and sender charges, then confirm on-chain records and platform credit. Timing depends on sender processing, confirmations and platform handling, not a universal few-minute promise.
Choose a suitable segment, check card funds, issuing and funding fees, then track the original order and card page. Receiving number, CVV, expiry, address, postal code and name does not remove merchant acceptance requirements.
References and operation links: pricing page · product overview
Check details and operation records
Check applicable policies, details and original records for this topic. Use official channels for questions instead of repeated submissions or test payments.