Skip to content

[Wallets] Add Cloudflare Wallets handle reservation docs - #32568

Draft
h3nrybrown wants to merge 2 commits into
productionfrom
wallets-handle-docs
Draft

[Wallets] Add Cloudflare Wallets handle reservation docs#32568
h3nrybrown wants to merge 2 commits into
productionfrom
wallets-handle-docs

Conversation

@h3nrybrown

@h3nrybrown h3nrybrown commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

New product section documenting the Cloudflare Wallets handle reservation flow at cloudflare.pay, announced in Announcing Cloudflare Wallets. The blog post is currently the only public source, so nothing published covers how reservations work.

Reviewed with the Agent Payments team. The policy below has been corrected from the first draft: reservations are not final, and Cloudflare reserves the right to reject or reclaim one. Still holding as draft pending the rest of that review.

Five pages under /cloudflare-wallets/:

Page Type Covers
index.mdx overview What Cloudflare Wallets is, and that handle reservation is the only part open today
wallet-handles.mdx concept Allocation, what can be changed after reserving, account binding, trademark reports
reserve-a-wallet-handle.mdx how-to The reservation flow, and how to confirm cloudflare.pay is genuine
wallet-handle-requirements.mdx reference Length, character, reserved name, and filtering rules
faq.mdx faq Cost, plan requirements, published information, and reservation errors

Behaviour and policy documented:

  • Handles are allocated first come, first served.
  • Cloudflare reserves the right to reject or reclaim a handle reservation at any time, for any reason. Reserving a handle does not grant ownership of a name or any trademark rights.
  • No self-service way to change, release, or transfer a handle exists today. Support is the route for those requests.
  • Revoking the Cloudflare Wallet Launch Site connected application does not release a handle.
  • Deleting a Cloudflare account does not release a handle, and a recreated account does not inherit it.
  • Trademark holders can report a handle through the abuse form, consistent with Complaint types.
  • cloudflare.pay is a genuine Cloudflare domain. Sign-in happens on dash.cloudflare.com, and the application requests read-only access.
  • Handles are not case-sensitive, and the reserved word and profanity filters match on substrings.

Also adds the cloudflare-wallets directory entry and a landing nav link under Build > AI.

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.

Documents the wallet handle reservation flow at cloudflare.pay, which
launched via the Cloudflare Wallets announcement but has no docs coverage.

Covers how handles are allocated and why reservations are final, the
format and reserved name rules, how to confirm the reservation site is
genuine, and the trademark reporting route.
@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
*.ts @cloudflare/content-engineering, @kodster28
* @cloudflare/product-owners

Reservations are not final. Cloudflare reserves the right to reject or
reclaim a handle reservation at any time, for any reason.

Replaces the permanence claim with the current position: handles are
first come, first served, no self-service change, release, or transfer
exists today, and Support is the route for those requests. Drops the
claim that trademark review is the only route by which a handle is
reconsidered, and that Support cannot act on one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants