Read the docs

Product and API Changelog

Read dated Dedyx changes, integration requirements and compatibility notes. Local changes are distinguished from production releases.

These entries describe source and local validation milestones. They are not a claim that the same revision is deployed to production. Public release status will be recorded when a release is verified.

2026-10-07 · Payment verification and webhook recovery

Added CHECKING for a saved 10-minute verification period after the sending deadline, safe merchant delivery diagnostics and audited retry of exhausted events. Checkout retains the last known status and displays the last successful refresh during connection errors. Trust Wallet preparation is experimental; address QR and manual copying remain available.

Compatibility: schema v5 and refreshed grants are required. Responses add verification_until and server_time; integrations must handle CHECKING. Webhook payloads and event IDs are preserved. Wallet phone acceptance and production deployment are separate checks.

2026-10-07 · Concurrent payments on one address

One merchant wallet can now have concurrent unfinished orders with distinct exact amounts. An unfinished PENDING/CHECKING/REVIEW order reserves its amount on that address; normalized duplicates return 409. Each order still requires one full exact transfer inside its payment window.

Compatibility: payment states, API models and webhook payloads are unchanged. Reusing an amount still carries the late-transfer attribution risk described in Payments. This entry records source and local validation, not a production deployment.

2026-10-07 · Operator credential recovery

Added audited operator recovery and revocation of API credentials, active/inactive account controls and verification of stored webhook keys under the current server master. Recovery preserves the account and payment history; inactive accounts retain existing payment checks and webhook delivery.

Compatibility: source requires database schema v4 and refreshed runtime grants. Public API routes and webhook payloads are unchanged. Production deployment is not implied.

2026-10-07 · SEO and integration material

  • Added public guides, use cases and FAQ.
  • Added canonical metadata, generated sitemap, social cards and explicit preview indexing rules.
  • Added Python and Node.js example clients with retry and webhook verification helpers.

Compatibility: API requests, payment matching and webhook payloads are unchanged.

2026-10-07 · Brand and checkout presentation

  • Selected the blue Dedyx mark and the Ocean palette.
  • Updated the API-focused home page, documentation and payment typography.
  • Added an explicit EN/RU language control and compatibility handling for cached checkout markup.

Compatibility: the existing public payment token and payment states are retained.

2026-10-07 · Merchant webhook configuration

Merchant-specific configuration uses GET/PUT /api/v1/merchant/webhook and POST /api/v1/merchant/webhook/rotate-key. A configured webhook is required before new payment creation. Save the first returned signing_key securely.

Integration requirement: configure the receiver through the merchant API; payment creation no longer accepts callback_url. See Webhooks.

2026-10-06 · Payment integrity and access controls

Source work introduced isolated runtime roles, safe idempotent creation, transfer event attribution, ledger/outbox consistency and signature/receiver protections. Sequential wallet reuse is documented with its limitations.

Compatibility: use a stable Idempotency-Key, verify event IDs and deduplicate webhook business actions. These entries report local validation; they do not establish a production deployment date.