Skip to content

feat(docs): add AVS for MOTO feature page and TSYS callout - #200

Open
me-valenzuela wants to merge 9 commits into
docs-v2from
feat/avs_moto
Open

feat(docs): add AVS for MOTO feature page and TSYS callout#200
me-valenzuela wants to merge 9 commits into
docs-v2from
feat/avs_moto

Conversation

@me-valenzuela

@me-valenzuela me-valenzuela commented Aug 6, 2026

Copy link
Copy Markdown

Summary

Adds a new Features section with a full AVS-for-MOTO integration guide
(Android SDK + Cloud API, TSYS only), plus a short summary inside
Functionalities > TSYS > MOTO linking to it.

Changes

  • New docs/features/avs-for-moto.mdx — full AVS-for-MOTO guide.
  • New Features nav tab (docusaurus.config.js, sidebars.js).
  • Short ### AVS subsection under Functionalities > TSYS > MOTO, linking to the Features page.
  • scripts/generate-acquirer-pages.js updated so future page regenerations produce the same subsection automatically.
  • data/acquirers.yaml / src/data/acquirerDetails.js / static/llms.txt updated with the new avs-for-moto capability (TSYS, Cloud API + Android PAX only).

How to test

  1. rm -rf .docusaurus node_modules/.cache && yarn start
  2. Check the new Features nav tab renders AVS for MOTO correctly.
  3. Check Functionalities > TSYS > MOTO shows the new ### AVS subsection and the link works.
  4. Check the Android SDK / Cloud API tabs in the Code section render correctly.

Screenshots

Captura de pantalla 2026-08-06 a las 17 49 45
Captura de pantalla 2026-08-06 a las 18 01 06

Checklist

  • Code builds and runs locally
  • Tests added/updated and passing — not done: scripts/__tests__/generate-acquirer-pages.test.js doesn't cover the new buildPage AVS-injection branch. Couldn't run the suite in this environment (jest binary missing, no network) — untested either way.
  • No secrets, keys, tokens or cardholder data committed
  • Jira ticket linked and updated — no ticket for this change
  • Screenshots attached where relevant

Notes for reviewers

Needs sign-off before merge: the Android SDK code samples (Billing, enableAvsFields, MoToOptions.billing, motoPreauthorization/motoRefund) are transcribed from the AVS integration guide draft and have no precedent anywhere else in this repo — every other MOTO sample only shows hapi.motoSale(BigInteger, Currency). Flagged in-page with a :::caution callout in the Code section. Please verify against the real hapi-android source before this ships to integrators.

Also worth a separate look (pre-existing, unrelated to this PR): src/data/acquirerDetails.js has no importers anywhere in the repo — the live capability table actually reads from src/data/acquirerCaps.js instead. Not blocking this PR, just flagging in case it's meant to feed something external.

Add a new "Features" section with a full AVS-for-MOTO guide (Android
SDK and Cloud API, TSYS only), plus a short "AVS" subsection under
Functionalities > TSYS > MOTO that links to it. Also updates the
acquirer-page generator template so future page regenerations produce
the same subsection.
Cloud API examples pointed at cloud.handpoint.io instead of .com, sent
amount as a JSON number instead of the string format used everywhere
else in the repo, and used a fabricated terminal model (PAXA920MAX).
Also flags the Android SDK code samples as unverified against the real
hapi-android source.
@me-valenzuela
me-valenzuela requested a review from alexdll31 August 6, 2026 15:52
Comment thread docs/features/avs-for-moto.mdx Outdated
Comment thread docs/features/avs-for-moto.mdx Outdated
Comment thread docs/features/avs-for-moto.mdx Outdated
Comment thread docs/features/avs-for-moto.mdx Outdated
… AVS result claim, move code to acquirer page

- Removed all references to a live Console UI for avsForMoto — it's not
  a live product yet; reframed as an internal flag Handpoint sets per
  merchant.
- Corrected "no match result" claim: the issuer/acquirer response does
  include an AVS result. Exact field name/shape is unconfirmed and
  flagged as pending in both the Overview and What Comes Back sections.
- Moved the Android SDK and Cloud API code samples out of the Features
  page and into the MOTO Code tabs on the TSYS acquirer page, next to
  the existing MOTO on-terminal/back-office samples. The Features page
  now just links to them.

Refs: PR review comments from flozanofdez
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants