docs: test mode — concept page, authentication page, test-first quickstart#79
Open
riveign wants to merge 11 commits into
Open
docs: test mode — concept page, authentication page, test-first quickstart#79riveign wants to merge 11 commits into
riveign wants to merge 11 commits into
Conversation
…t test-first - New payments/merchant/test-mode page: account-level test/live model, switch-by-key, wcp_test_ prefix, synthetic tx hashes, webhook behavior, go-live path; env diagram in purple (test-mode color) - New api-reference/authentication page: Api-Key header, test vs live key semantics, no environment field on responses - Quickstart reframed test-first with wcp_test_ examples + go-live section - Overview: test-before-live messaging + merchant/test-mode cards - Reconcile the two contradictory wallet Test Payment Links blurbs; remove the last "sandbox" mention (term is "test mode") Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ashboard walkthrough, no webhook mentions - Amounts: test options now quote from the requested amount at real exchange rates (pay-core #1028) — replaces stale fixed-1-unit claim - Replace go-live framing with the pilot limit: live env starts in pilot, Pilot to Live card, Request to go live flow (MX #798 copy) - New dashboard walkthrough: create a test payment + Simulation actions status transitions (with state diagram) - Quickstart: test-vs-live intro up front; 'From test to live' = same six steps with a live key - Remove all webhook mentions (not released yet), incl. pre-existing quickstart tip; purple = docs convention only (dashboard uses env selector) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…le + dashboard menu Verified against buyer-experience: purple test banner + Test Console (Confirm success / Simulate failure / Expire / Cancel) + simulated Test Wallet on the payment page; purple claim extended to payment page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Environment selector, create-payment dialog, payment-created link, hosted payment page (purple banner + Test Console), and Test Console actions. Pilot to Live card shot pending team update. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…age layout - Say test/live *mode* everywhere; never 'environment' (incl. table headers and the no-env-field warnings) - Create-a-test-payment: add the create-merchant step (per-mode data) - One screenshot in the create section; payment page + Test Console side by side in columns (fixes stacked/overlapping frames) - Remove now-unused env-selector + payment-created screenshots - 'Allowed status transitions' subtitle over the state diagram - Drop leftover webhooks mention in the intro Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
payments/merchant/test-mode → payments/test-mode; nav entry moves to the WalletConnect Pay group (both version blocks) so the Merchants section opens with Quickstart. All links updated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
rtomas
approved these changes
Jul 13, 2026
rtomas
left a comment
Member
There was a problem hiding this comment.
I prefer mermaid without the actions buttons
|
|
||
| Test and live are separated at the **account level**, and you choose the mode by **which API key you use**. There is no `test` flag or mode parameter on any request — a payment created with a test key is a test payment, and a payment created with a live key is a live payment. | ||
|
|
||
| ```mermaid |
Member
There was a problem hiding this comment.
Suggested change
| ```mermaid | |
| ```mermaid actions={false} |
|
|
||
| Whichever surface you use, a test payment can only move along these paths: | ||
|
|
||
| ```mermaid |
Member
There was a problem hiding this comment.
Suggested change
| ```mermaid | |
| ```mermaid actions={false} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Public docs coverage for test mode, targeting the Jul 15 GA. Follows the Test Mode — Public Docs Alignment doc + the comments on it. Opened as a draft to iterate on — comment freely.
New pages
payments/merchant/test-mode— the concept page: account-level test/live, switch-by-key (no test flag/param anywhere),wcp_test_prefix, what test payments do/don't do (no on-chain execution, synthetictest:{paymentId}tx hash, fixed 1-unit amounts), webhooks fire in test mode, go-live path. Includes an environment diagram with test mode in purple (per Rocky's diagram ask + Tomas R.'s purple-as-test-color proposal).api-reference/authentication— the previously-missing auth page:Api-Keyheader, test vs live key semantics, 401/403, key safety.Edits
wcp_test_, synthetictxIdin the status example, closing "Go live" section.docs.json) — both version blocks updated.Decisions baked in (from the alignment thread)
&_t=1gateway tag is treated as an implementation detail — not documented.Not in this PR (follow-ups)
not_sandbox_api_keyenum. They should be regenerated, not hand-edited, so the JSONs are untouched here.mint broken-linkspasses.🤖 Generated with Claude Code