docs(moonpay-commerce): merge x402 paylink flow into commerce skill#73
Open
xyz1hang wants to merge 4 commits intomoonpay:mainfrom
Open
docs(moonpay-commerce): merge x402 paylink flow into commerce skill#73xyz1hang wants to merge 4 commits intomoonpay:mainfrom
xyz1hang wants to merge 4 commits intomoonpay:mainfrom
Conversation
Add MoonPay Commerce x402 paylink payment guidance to the moonpay-commerce skill so a single skill covers both Shopify storefront checkout and direct paylink payments via api.hel.io. - Existing Shopify storefront content (mp commerce store/product/cart/checkout) preserved verbatim under the original "# Shop with crypto" heading. - New "## MoonPay Commerce" section covers the x402 paylink flow: api endpoints, payerAddress requirement, 402 response decoding, supported chains, error table, settlement, amount conversion, worked example, custom client notes, security, and troubleshooting. - Frontmatter description and tags widened so the skill is discovered for either Shopify shopping or paylink payment requests. - Solana-only note scoped to the storefront flow; multi-chain (Base, Ethereum, Polygon, Arbitrum, BSC, Solana) applies only to the x402 flow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…rification
Document the new POST /v1/x402/checkout/charge/{chargeToken} endpoint
(heliofi/backend#4161) that lets an agent settle the in-flight Charge
created by Shopify when the buyer selects Solana Pay at checkout — instead
of creating a parallel x402 Charge.
- Add the charge endpoint to the API table.
- Add a "Charge resume (Shopify-source paylinks)" subsection under Payment
flow with the Solana-only constraint and the no-amount rule (price comes
from Charge.usdcAmount).
- Add a "Verifying payment status" subsection: agents must poll
GET /v1/charge/{chargeToken} after the 200 to confirm the PaylinkTx and
read the on-chain txSignature, which is not returned in the 200 body for
the charge-resume flow.
- Extend the error table with charge-token-specific cases: 404 NOT_FOUND,
400 NON_SHOPIFY, 409 ALREADY_SETTLED, 410 EXPIRED.
- Update the pre-payment checklist and custom-client integration steps to
include the charge status poll.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Add a "When to use" bullet and an identifier routing cheat-sheet so the
agent recognizes that a bare UUID (e.g. 6d0a1c57-3544-42e2-aa44-b654077c7529)
supplied alongside the word "charge" is a chargeToken — and should be sent
to POST /v1/x402/checkout/charge/{chargeToken}, not to /checkout/{paylinkId},
/deposit/{depositId}, or /v1/paylink/{id}/public.
The cheat-sheet covers the three ID shapes (paylink slug, depositId, UUID
chargeToken) and the fallback rule: if the charge endpoint returns
CHARGE_NOT_FOUND (404), only then try the other endpoints.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Merge the MoonPay Commerce x402 paylink payment flow into the existing
moonpay-commerceskill so a single skill covers both checkout surfaces:mp commerce store/product/cart/checkout(Solana Pay) — existing content preserved verbatim under the original# Shop with cryptoheading.mp x402 requestagainsthttps://api.hel.io/v1/x402/checkout/{id}and/deposit/{id}— added under a new## MoonPay Commercesection.Frontmatter
descriptionandtagswidened so the skill is discovered for either Shopify shopping or direct paylink payment requests. TheTipsnote about Solana-only support is scoped to the storefront flow only — the x402 flow supports Base, Ethereum, Polygon, Arbitrum, BSC, and Solana.What's not included
No existing content was removed. Production-only / environment framing from the source material was intentionally omitted — only protocol, API, error, and workflow guidance was merged.
Checklist
skills/moonpay-commerce/SKILL.mdupdated with merged contentname,description,tags) widened.claude-plugin/marketplace.json(skill already registered)MoonPay Integration
The x402 flow uses the local MoonPay wallet (
mp wallet list) to sign EIP-3009 / SPL token transfers against MoonPay Commerce paylinks; settlement is handled by the Helio resource server. The Shopify flow is unchanged — Helio pays gas, buyer pays the item price in USDC.Test plan
skills/moonpay-commerce/SKILL.mdend-to-end — both flows render cleanlymp commerce store list,cart add,checkout, etc.)?payerAddress=, 402 structure, chains, errors, settlement, troubleshooting)🤖 Generated with Claude Code