Changelog
Creator Studio and account-level tipping
Creators can now launch public tipping pages without merchant onboarding, accept multi-chain wallet payments with live transaction scanning, and manage donation records in Creator Studio.
What changed
- Account-owned public tip pages allow creators to customize introductions, display platform badges (GitHub, X, Instagram), and share reusable donation links.
- Donation sessions support direct wallet transfers and Web3 wallet connections with live USD price conversion, unique payment matching, and automatic on-chain arrival confirmation.
- Creator Studio provides recipient wallet management, donor messages and receipts, and incoming donation analytics directly inside the account dashboard.
Related links
Account notifications and delivery recovery
Payment and subscription notices now remain traceable through in-app and account-email delivery, with retry handling that rechecks whether a notice is still valid.
What changed
- Payment and subscription events create durable in-app records and account-email deliveries. Notification history exposes the delivery state while the message is processed.
- Failed account emails use stepped backoff with up to five attempts. Before an automatic or manual retry, PolyPay rechecks the current subscription or monitored-address state and cancels stale notices instead of sending them.
- System notices do not consume the wallet-monitoring notification allowance. Wallet-monitoring delivery limits and address-state rules remain documented separately.
Related links
Wallet monitoring notification window and address import
Wallet monitoring now limits notifications to recent on-chain activity, stops retries when a monitored address is no longer active, and can import a merchant receiving wallet without requesting a private key.
What changed
- Notifications are sent only for transactions whose on-chain time is within the past 72 hours. Older transactions remain in history, but do not create in-app, external-channel, or Webhook notifications.
- When a monitored address is disabled, deleted, or paused for billing, queued channel retries and manual resends are blocked. Messages already sent are not recalled.
- The Add monitored address flow can import a merchant receiving wallet from the selected merchant and wallet. PolyPay uses the public address and never requests the private key.
Related links
Channel invitation Pro trials
New users can enter a valid channel code during signup or use an invitation link to receive three calendar months of the payment Pro plan on their first merchant. The trial is free, does not auto-renew, and does not waive transaction, network, or usage fees.
What changed
- The signup page accepts a PP- channel code or a signup link with ?ref=CODE, checks the offer before registration, and shows the channel and trial terms when the code is valid.
- Email signup and new OAuth signup grant the entitlement atomically to the first merchant, once per account. Existing accounts cannot claim it, and channel trials cannot be combined with friend balance rewards.
- The trial covers only the payment Pro subscription fee. Its amount is zero and auto-renewal is off; after three calendar months the merchant returns to the free plan unless they choose an existing paid-plan flow.
Wallet monitoring and notification templates
PolyPay now lets you monitor income and expenses for public blockchain addresses, manage wallet notifications separately, and configure an independent wallet-monitoring Webhook.
What changed
- Add a public address to Wallet Monitoring and review its income and expense activity on a separate page. A monitored address is separate from a receiving wallet, and PolyPay never requests a private key.
- Manage wallet income and expense templates by channel and language in Notification Settings. Enabled monitored addresses use the human notification channels supported by the plan; only successful deliveries consume the account notification allowance.
- Configure one independent wallet-monitoring Webhook with its own event and address scope, HMAC-SHA256 signature, retry state, and versioned JSON payload. Changes stay disabled until a signed test passes.
JavaScript SDK 2.0 moves checkout creation to the server
JavaScript SDK 2.0 removes browser-side order creation and signed checkout construction. Browsers now open only Hosted Checkout URLs created by a trusted merchant server.
What changed
- Create Hosted Checkout on the merchant server with an API key, then return only the opaque checkout_url to browser code. API keys, amounts, callback URLs, and signing material no longer belong in the browser integration.
- PolyPayCheckout.redirect() and openModal() accept the server-created URL. A redirect or popup close is not payment proof; confirm payment through a verified webhook or an authenticated server-side order query.
- Browser Public Key order creation, Session Tokens, browser order/status APIs, and signed checkout URL builders have been removed. Server-side x402 support remains available through @polypay/sdk/x402.
Related links
Merchant archiving and restore
Merchants can now archive an inactive merchant without losing its history, then restore it later from Account Settings.
What changed
- Archive the current merchant from Merchant Management after a confirmation step. The archived merchant is removed from the regular switcher, its business features stop, and subscription auto-renewal is disabled.
- Archiving preserves historical orders and subscriptions and does not affect the account balance or withdrawals.
- View and restore archived merchants in Account Settings. Subscription auto-renewal must be enabled manually after restoration if it is still needed.
Related links
Agent-readable documentation
PolyPay documentation now exposes public, machine-readable discovery surfaces for coding agents and other automated tools.
What changed
- Added llms.txt as a concise map of public documentation.
- Added an RFC 9727 API catalog for machine-readable API discovery.
- Kept authenticated dashboards, checkout sessions, and private APIs outside the public agent surface.