---
title: "Receive an SMS or Gmail verification code"
description: "Use temporary receiving resources only when your order and target service permit them, and resume after a refresh."
image: "https://docs.xiu.ai/og.png"
---

> XiuAI documentation index
> Full documentation index: https://docs.xiu.ai/en/llms.txt
> Check the index for current pages before reading.

# Receive an SMS or Gmail verification code

Use the code receiver only when your order explicitly includes temporary receiving resources and the target service allows them. It does not guarantee that a platform accepts the number, mailbox, or account eligibility.

> **Temporary resources are not long-term recovery details**
>
> Do not use this tool to bypass a requirement for a personally controlled long-term number or a prohibition on VoIP and app-generated numbers.

As reviewed on 2026-08-02:

- Ordinary ChatGPT registration and use do not require a phone number. Do not buy SMS verification for that purpose.
- Claude requires a supported-region number you can control long-term and use for SMS. It rejects VoIP, Google Voice, app-generated numbers, and landlines. This tool is not for Claude registration.
- Google may require verification depending on the account and situation. Prefer your own long-term number and recovery email; use this tool only when the order explicitly covers the flow.

## Choose the resource type

- **SMS** provides a phone number and receives SMS verification codes.
- **Gmail** provides a Gmail mailbox and receives email verification codes.

## Receive a code

1. Open [XiuStore code receiver](https://store.xiu.ai/en/receiver/), choose SMS or Gmail, enter the complete redemption code, and verify it.
2. Once verified, request a number or email address and enter the assigned value on the target platform.
3. Return to XiuStore and wait for automatic refresh. Use only the latest code shown as received.
4. Copy the code back to the target platform and complete verification. Keep the code and assigned resource private.

The expected progression is ready to use, resource assigned, receiving, then received with the latest code displayed.

## Replace a number or mailbox

Replace it only when the page offers that action. Waiting periods and replacement limits may apply. Avoid replacing a resource after receiving a code, which can invalidate the original flow.

## Resume after refreshing

The current device stores each resource type's redemption code, assigned resource, receiving state, and random device identifier so the flow can resume. Verification codes are not written to browser local storage. Requests and responses pass through XiuStore's receiver API and its upstream service.

Avoid one-time receivers on shared devices, for long-term account recovery, or for highly sensitive accounts.

## Troubleshoot

| Symptom | Next step |
| --- | --- |
| Code unavailable | Recheck the full code and selected resource type |
| No number or email returned | Do not submit a blank value to the platform; request again or contact support |
| No verification code arrives | Confirm that the original platform sent it, wait for refresh, and use replacement only as permitted |
| Code expired | Restart verification on the original platform and use only its latest code |

Keep the order reference, time, and redacted error. Do not send verification codes, passwords, or complete assigned resources to support.

## Sources and review date

Reviewed on 2026-08-31. This translation preserves that date. Google, OpenAI, and Anthropic requirements vary by account and situation; follow the target platform's current instructions.

Source: https://docs.xiu.ai/en/store/verification-code-receiver/index.mdx