Documentation

Changelog

Track breaking changes, new features, and documentation updates. Read this before your quarterly 'why did staging break?' meeting.

Need machine-readable request/response bodies for your AI or codebase? Download this page as plain Markdown.

When should I use this?

  • You upgrade an integration and need to know what changed.
  • You debug behavior differences after a deployment.

Why use Videpay?

  • Breaking changes announced before they affect live.
  • New endpoints documented when released.

Integration maintenance

Before your quarterly integration review, you read the changelog for new webhook events or deprecated fields. You arrive prepared. Your standup thanks you.

July 9, 2026

  1. Recovery holdings (API): new endpoints: GET `/recovery-holdings`, GET `/recovery-holdings/{id}`, POST `/recovery-holdings/{id}/release`. Unsupported tokens recovered from deposit sessions or virtual wallet transfers are recorded as holdings in platform custody; release sends the exact amount to your registered `merchantAddress`.
  2. Recovery holdings (webhooks): new events: `recovery-holding.created`, `recovery-holding.release-queued`, `recovery-holding.released`, `recovery-holding.release-failed`.
  3. Subscription payloads: `customer` is now always present on subscription GET responses and `subscription.*` webhooks; `null` when no `customerId` was set at signup (previously omitted).
  4. Customer in webhooks (docs): embedded `customer` object documented on deposit, payment, and subscription payloads (`{ id, name, email, phoneNumber, reference }`) so you can fulfill orders without a follow-up API call.
  5. Virtual wallet & deposit recovery (docs): unsupported-token flow clarified: TokenRegistry-supported vs unsupported assets, automatic recovery to platform custody, and release via recovery holdings.

July 7, 2026

  1. Documentation overhaul: full request/response bodies and complete webhook payloads from server serializers.
  2. Removed reputation, reconciliation, and merchant setup doc sections.
  3. Split Swap and Cross-chain swap into separate pages.
  4. Per-page Markdown download for AI-assisted integration.