Skip to content

docs: add Vipps MobilePay gateway page#118

Merged
kilbot merged 9 commits into
mainfrom
vipps-docs
Mar 1, 2026
Merged

docs: add Vipps MobilePay gateway page#118
kilbot merged 9 commits into
mainfrom
vipps-docs

Conversation

@kilbot
Copy link
Copy Markdown
Contributor

@kilbot kilbot commented Mar 1, 2026

Summary

  • Add new documentation page for the WCPOS Vipps MobilePay payment gateway covering features, installation, usage (QR code + push notification flows), supported Nordic markets, requirements, and troubleshooting
  • Add Vipps MobilePay to the custom gateways index page under a new "Mobile Payment Gateways" category
  • Add Vipps MobilePay to the versioned sidebar
  • Update WooCommerce POS requirement from "Free or Pro" to "Pro version required for POS checkout" across all existing custom gateway pages (Stripe Terminal, SumUp Terminal, Email Invoice, Web Checkout)

Test plan

  • Visit /payment/custom-gateways/vipps-mobilepay/ and verify the page renders with all components (feature grid, installation steps, accordion, requirements list, markets table)
  • Check the sidebar shows "Vipps MobilePay Gateway" under Payment > Custom Gateways, positioned between SumUp Terminal and Email Invoice
  • Visit /payment/custom-gateways/ and verify the index page shows the new "Mobile Payment Gateways" section with the Vipps link
  • Verify all links work: GitHub releases, Vipps Portal, Vipps developer docs
  • Spot-check existing gateway pages (Stripe, SumUp, Email Invoice, Web Checkout) still render correctly with the updated Pro requirement text

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Added comprehensive Vipps MobilePay gateway guide with installation, payment flows, refunds, supported markets, and troubleshooting
    • Clarified WooCommerce POS checkout requirement across gateway docs to state Pro version is required
    • Updated navigation to include the new Vipps MobilePay documentation entry

kilbot added 8 commits March 1, 2026 09:23
- Update gateway name references to "WCPOS Vipps MobilePay"
- Fix plugin link to point to Checkout with Vipps MobilePay (was
  linking to the recurring payments plugin)
- Remove Sweden from supported markets (uses Swish, not Vipps)
- Clarify WCPOS Pro requirement (needed for POS, gateway also works
  on standard WooCommerce checkout)
- Improve "no need to enable" note wording
All custom payment gateways require Pro for POS checkout. Update
wording from "Free or Pro version installed and activated" to
"Pro version required for POS checkout" across Stripe Terminal,
SumUp Terminal, Email Invoice, Web Checkout, and the index page.
@vercel
Copy link
Copy Markdown

vercel Bot commented Mar 1, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Mar 1, 2026 9:03am

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 1, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between adf1b33 and 599396f.

📒 Files selected for processing (1)
  • versioned_docs/version-1.x/payment/custom-gateways/vipps-mobilepay.mdx

📝 Walkthrough

Walkthrough

Standardizes WooCommerce POS requirement wording to state "Pro version required for POS checkout" across multiple gateway docs, adds a new Vipps MobilePay gateway documentation page, and updates the versioned sidebar to include the new page.

Changes

Cohort / File(s) Summary
POS Requirement Wording
versioned_docs/version-1.x/payment/custom-gateways/email-invoice.mdx, versioned_docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx, versioned_docs/version-1.x/payment/custom-gateways/sumup-terminal.mdx, versioned_docs/version-1.x/payment/custom-gateways/web-checkout.mdx
Replaced RequirementsList item text to require the Pro version for POS checkout in each gateway document.
Vipps MobilePay Documentation
versioned_docs/version-1.x/payment/custom-gateways/vipps-mobilepay.mdx, versioned_docs/version-1.x/payment/custom-gateways/index.mdx
Added a new Vipps MobilePay MDX page (features, installation, flows, refunds, troubleshooting) and added a "Mobile Payment Gateways" subsection to the index listing Vipps MobilePay.
Sidebar Navigation
versioned_sidebars/version-1.x-sidebars.json
Inserted payment/custom-gateways/vipps-mobilepay into the Payment → Custom Gateways items list in the versioned sidebar.

Sequence Diagram(s)

(omitted — changes are documentation and sidebar updates without new runtime control flow)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐰 I hopped through docs both near and far,

Pro POS now shines like a star,
Vipps MobilePay joined the trail,
QR hops and push notifications prevail,
A celebratory nibble and a joyful ear-twitch! 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'docs: add Vipps MobilePay gateway page' is concise, clear, and accurately reflects the primary change—adding documentation for a new Vipps MobilePay payment gateway.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch vipps-docs

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@versioned_docs/version-1.x/payment/custom-gateways/vipps-mobilepay.mdx`:
- Around line 68-72: The gateway label is inconsistent between steps (one place
uses "WCPOS Vipps MobilePay" and another uses "Vipps MobilePay"); update the
StepCard title and any step text to use a single, consistent label (choose
either "WCPOS Vipps MobilePay" or "Vipps MobilePay")—for example, change the
StepCard title="Enable in WooCommerce POS" and the step list entry that finds
the gateway to reference the exact same label "Vipps MobilePay" to keep wording
consistent across the setup steps.

ℹ️ Review info

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a7d8150 and adf1b33.

📒 Files selected for processing (7)
  • versioned_docs/version-1.x/payment/custom-gateways/email-invoice.mdx
  • versioned_docs/version-1.x/payment/custom-gateways/index.mdx
  • versioned_docs/version-1.x/payment/custom-gateways/stripe-terminal.mdx
  • versioned_docs/version-1.x/payment/custom-gateways/sumup-terminal.mdx
  • versioned_docs/version-1.x/payment/custom-gateways/vipps-mobilepay.mdx
  • versioned_docs/version-1.x/payment/custom-gateways/web-checkout.mdx
  • versioned_sidebars/version-1.x-sidebars.json

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.

1 participant