CON-10571: rewrite Payment automation for Mews Payments Checkout#68
CON-10571: rewrite Payment automation for Mews Payments Checkout#68jnv wants to merge 7 commits into
Conversation
|
✅ Review posted. View review · run |
moxly
left a comment
There was a problem hiding this comment.
Risk Assessment
Score: 1/10 — low
This is a documentation-only rewrite. Verified all internal anchor links (#flow-1-capture-a-payment-request, #collecting-a-payment-method-for-future-charges, #context, #testing, etc.) resolve to their corresponding headings, and all cross-file references (paymentrequests.md#add-payment-requests, paymentmethodrequests.md#add-payment-method-request, reservations.md#reservation-parameters, creditcards.md#charge-credit-card, payments.md#add-credit-card-payment, guidelines/environments.md, contact-support/README.md) point to real files and existing headings. GitBook {% hint %} / {% stepper %} syntax matches existing conventions elsewhere in the repo, the new en-dash rule in AGENTS.md is followed throughout the rewritten page (no em dashes found), and the PR's claimed removal (orphaned "merchant ID" row in how-to.md) is reflected in the diff. No stale references to the dropped Secure Fields / tokenized-credit-card flow remain elsewhere in the repo.
Review Summary
Verdict: APPROVE
No findings — the rewrite is internally consistent and well cross-checked against existing repo conventions and operation references.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Summary
CON-10571: Rewrites the Connector API Payment automation use case to document Mews Payments Checkout, the embeddable JavaScript checkout SDK for collecting payments and payment methods directly in a partner application. This replaces the previous tokenized-credit-card / Secure Fields (PCI Proxy) manual flow.
What changed:
https://cdn.mews.com/payments/checkout-embed.js.{% hint %}callouts and{% stepper %}step sequences, with heading-based callout titles to match repo conventions (e.g.concepts/restrictions.md).../operations/*.md#anchor), consistent with the rest of the space; cross-space and external links stay absolute.Note: the previous Secure Fields / Add tokenized credit card flow is intentionally dropped and no longer documented elsewhere in the Connector API guide.
Checklist
SUMMARY.mdupdated if new pages addedAPI