Skip to main content
This log covers changes to the documentation and to the integrations described here. The RSS feed is available at /en/changelog/rss.xml.
​
Widget
Payment button (widget)

​
Payment button (widget)

New Payment button (widget) section: a single /v1/sdk.js script that adds a floating button to your page and opens the payment process for your product in a modal. No backend and no API key - the product ID is all it needs.
  • Configuration with data-* attributes: button text, bubble, language, position, several widgets on one page
  • Controlling the widget window.PaymoveWidget, the paymove:completed event and custom buttons
  • Paying for a specific document (data-external-id) and a document-number entry screen (data-document-entry)
  • Apple Pay activation: the widget requires merchantDomain on the product and a verification file from paymove hosted on your domain
​
APISDKDocPay
Payout account

​
Payout account (IBAN) on the product and the payment

We documented how to choose the account Paymove pays funds out to. You set it when creating the product, and a single payment or subproduct can override it. Details: REST API, Configuration, SDK and DocPay. The same information is in skill.md, agents.md and llms.txt.
  • The bankAccountDetails object (iban, holderName, nip - only iban is required) when creating a product, a payment and a subproduct, also in the OpenAPI specifications
  • The bankAccount field of the SDK’s createPayment - the IBAN alone as a string
  • An invalid IBAN returns 400, and a product’s account cannot be changed with PATCH - you can only set it at creation
​
Payment methodsAI agents
Payment methods

​
Sandbox BLIK test code and PayPo minimum amount

The Payment methods page now explains how to pay in sandbox and from what amount the customer sees PayPo. The same information is in skill.md, agents.md and llms.txt.
  • Sandbox BLIK test code: any 6 digits starting with 777, e.g. 777123
  • PayPo appears on the checkout only from 10.00 PLN (price of 1000 or more) - below that the method is not listed
​
APIWebhooksDocPay
Corrections

​
Corrections after verifying the docs against the API

We went through the documentation endpoint by endpoint and checked every claim against the running API. Here is what needed correcting.
  • price in the webhook payload is the amount you sent when creating the payment, not the amount net of the fee - you can compare it against your own record
  • retries and expectedCode are required when registering a webhook; omitting either returns 500
  • The details field of a DocPay pricing entry is a JSON object, not a string
  • The webhook list endpoint accepts only the productId parameter
  • CARD added to the list of details.triggerPayment values in the OpenAPI specification
  • The activeFrom field in the webhook payload, plus partnerId, productIds and retryOnCodes on the webhook object
​
Docs
Design

​
New look for the documentation

The documentation now uses the Paymove design system: light and dark themes, Google Sans Flex and Geist Mono typography, Lucide icons and redesigned components.
  • New home page with quick links, products, popular pages and a prompt for AI assistants
  • Changelog tab with this log and an RSS feed
  • Dark code blocks in both themes - syntax is always readable
​
AI agentsAPI
skill.md

​
Clearer instructions for AI agents

We updated skill.md, agents.md and llms.txt as well as the product and webhook configuration guide so an agent creates them correctly the first time.
  • Product field metadata.logoUrl - the shop logo shown on the checkout
  • Product field descriptions: what is optional, what the customer sees, what lands in the webhook
  • Error codes 401 (key lacks permissions) and 403 (foreign partnerId) on the Error codes page
​
WidgetPayment methods
Apple Pay

​
Apple Pay in the widget

In the modal the checkout runs in an iframe on your domain, so Apple requires that domain to be registered. The Browser widget page describes how.
  • Product field metadata.merchantDomain and the Apple verification file
  • Without this configuration Apple Pay does not appear in the modal’s payment methods
​
APIWidget
autoclose

​
Automatic return to the shop

The new details.autoclose field (milliseconds) makes the checkout return to returnUrl on its own after a successful payment, or close the modal in the widget. The countdown is shown in the “Back to shop” button and any customer interaction cancels it.
  • details.autoclose in the REST API and in SDK types from release 0.3.0
  • The widget’s autocloseDelay option replaced by autoclose in the payment data
​
AI agentsDocs
Markdown

​
Documentation for AI agents

Every page can be fetched as plain Markdown, and an agent gets the complete integration procedure at a single URL.
​
AI Payments
MCP

​
AI Payments: MCP and ElevenLabs

The AI Payments section gained integration guides: the MCP server for clients such as Claude Desktop or Claude Code and the ElevenLabs voice agent.
​
SDKAPI
Naming

​
Naming change: merchant → product

In the JavaScript SDK and the OpenAPI specification the term merchant was replaced with product. Payments are created within a product identified by productId.
  • Unified names in the SDK and the API reference