Conversation
docs: document merge-method rule and broken-link caveat in CLAUDE.md
#193) * docs(restapi): document NoTransactionToCancel error and release REST API 2.29.0 Adds error code 1005 (NoTransactionToCancel) to the /transactions response table, distinguishing "no transaction to cancel" from the generic CancelOperationNotAllowed (1003) case, and cuts the 2.29.0 docs version to publish it. * Corrected no reader reversal responses updated responses for reversals without reader --------- Co-authored-by: ecunado <ecunado@ecunados-MacBook-Pro.local> Co-authored-by: AlexDLL31 <alexdll@protonmail.com>
…ject (#194) * docs(restapi): fix Reversal response docs and add ViscusReversalResponse object The Reversal endpoint's Returns table linked to DeferredTokenizationResponse (copy-paste from the Deferred Tokenization section, added by cloudapi PR #432). No ViscusReversalResponse object existed to link to, so it is now documented with the real gateway field set. Also fixes the restobjects.md link that pointed to the non-existent restendpoints#reversal-operations anchor, and adds the missing timestamp parameter to the endpoint's Parameters table. * docs(restapi): drop internal Viscus prefix from Reversal object names Sibling objects (BatchCloseRequest, MotoReversalRequest, etc.) don't carry implementation-detail prefixes; ViscusReversalRequest/ViscusReversalResponse leaked the internal cloudapi model class name into public docs. --------- Co-authored-by: ecunado <ecunado@ecunados-MacBook-Pro.local>
changes/fixes that were sitting on next and apply to 2.29.0 were added to the restendpoints and objects pages
* updated 2.29.0 with Next changes/fixes that were sitting on next and apply to 2.29.0 were added to the restendpoints and objects pages * docs: fix Reversal/Sale/Refund docs, correct release-notes attribution, and repair dead anchors REST API (2.28.0 & 2.29.0): - Reversal (no-reader) endpoint: add info note clarifying that reversals through this endpoint are attributed to the original device in Analytics and won't appear in the Handpoint Payments App. - Sale and Refund (MOTO) endpoints: add 200 OK example response tabs. - MOTO Reversal: remove the incorrect "Optional merchant references: customerReference, transactionReference" line - MotoReversalRequest does not support these fields. - Release notes: move the "Reversal without reader" feature entry to a new 2.28.0 section, since that's the version it actually shipped in, and note that batchNumber is now optional on POST /close in 2.29.0. Windows SDK (all versions, 3.2.0 through current): - Fix #status-info anchor to match the real statusInfo heading ID (kept the legacy kebab-case form in 3.2.0, the one version whose heading has no explicit anchor and still relies on the auto-slug). - Fix OperationStartResul typo (missing trailing "t") to OperationStartResult in windowstransactions.md. - Remove two dead self-page anchor links (#7 on ConnectionStatusChanged, #11 on TransactionResultReady) that pointed to nonexistent legacy numbered anchors; kept the surrounding text, just de-linked it. Android SDK (all versions with the section): - Add the missing {#cloudTokenizedPaymentsOperations} anchor to the "Cloud Tokenized Payments Operations" heading, fixing a broken cross-plugin anchor referenced from the Windows, JavaScript, and REST API docs. yarn build passes with no new broken links/anchors introduced. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
* fix: mobile touch events on cpdocs.js page - Add overflowX: auto to TableContainer components so wide MUI tables don't push the body wider than the viewport, which was hiding the navbar burger button off-screen on mobile - Add cursor: pointer + touch-action: manipulation to .pills__item so iOS Safari fires click events on the li elements in InfoTabs * fix: add cursor:pointer to pills__item for iOS Safari
* docs: add Billing object for MoTo AVS support Documents the new billing field (zipCode, address) accepted by POST /transactions for moToSale and moToPreAuthorization, used for Address Verification Service. Matches the cloudapi implementation on feature/avs-moto and the terminal-side support shipped in hapi-android. * docs: add billing (AVS) field to MotoSaleRequest POST /moto/sale now accepts the same optional billing address used for Address Verification Service (AVS) as the Transaction Request Object, matching Viscus's ecomm API support for AVS on MOTO sale. --------- Co-authored-by: ecunado <ecunado@ecunados-MacBook-Pro.local>
* docs(android): document core library desugaring requirement for 7.1014.0 Starting with SDK 7.1014.0, apps must enable Android Gradle Plugin core library desugaring to keep backwards compatibility with older Android APIs while the SDK adopts modern Java APIs internally. Add the Gradle setup snippet to the intro and all three integration guide paths (PAX, HiLite, USB), and record it as a breaking change in the release notes. BREAKING CHANGE: apps consuming Android SDK 7.1014.0+ must add coreLibraryDesugaringEnabled and the desugar_jdk_libs dependency to their build.gradle, or the build will fail. Co-Authored-By: Claude Code - Claude Sonnet 5 <noreply@anthropic.com> * docs(android): document AVS support for MoTo transactions Add the Billing object and the new MoToOptions billing/enableAvsFields fields to the objects reference, plus a code example showing both ways to supply AVS data. Record the feature in the 7.1014.0 release notes. Co-Authored-By: Claude Code - Claude Sonnet 5 <noreply@anthropic.com> * docs(android): document AVS result on TransactionResult Add the addressVerification field (AddressVerification object, AvsResultCode enum) to the Transaction Result reference, and note in the 7.1014.0 release entry that the AVS outcome is returned there. Co-Authored-By: Claude Code - Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Code - Claude Sonnet 5 <noreply@anthropic.com>
* feat: add Android SDK 7.1014.0 and REST API 2.30.0 versions Android SDK 7.1014.0 - Add version snapshot (android_versioned_docs/version-Android SDK 7.1014.0/) - Add sidebar JSON for the new version - Update android_versions.json to include 7.1014.0 - Insert 7.1013.0 release notes in androidreleasenotes.md (between 7.1014.0 and 7.1012.3): NFC performance, duplicate-check for MoTo, deferred tokenization, UNDEFINED recovery fix, chip fallback entry type fix REST API 2.30.0 - Add version snapshot (restapi_versioned_docs/version-REST API 2.30.0/) - Add sidebar JSON for the new version - Update restapi_versions.json to include REST API 2.30.0 - Add 2.30.0 release notes: AVS support via billing object on moToSaleRequest and transactionRequest Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(7.1013.0): recategorise MoTo UNDEFINED recovery as improvement MoTo previously had no transactionReference so status recovery was impossible — adding it is a new capability, not a bug fix. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * fix(7.1013.0): scope UNDEFINED recovery note to MoTo Sale only Scope unclear — narrowing to Sale until confirmed by SDK team. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fix broken cross-plugin markdown link in android release notes Replace relative restreleasenotes.md link with pathname:// protocol to allow cross-plugin linking from android docs to restapi docs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…scription (#213) restapi: remove misleading AVS fallback sentence from Billing description Remove "When omitted and AVS is enabled on the device's configuration template, the terminal prompts the operator for the billing details instead." from the Billing object description and from the billing property row in the MotoSaleRequest table. Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
alexdll31
changed the title
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
3 participants
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
Commits included (10)
Test plan
🤖 Generated with Claude Code