Skip to main content

​
Latest Updates

Stay informed about new features, improvements, and bug fixes in the HOST Pay API. Versions and dates follow the platform’s internal release track.

​
[0.14.0] - 2026-10-02

This release improves payment processing and webhook delivery performance while preserving existing API routes, payloads and signatures.
  • Monime calls reuse HTTP connections within each worker execution context, without retaining your application credentials or cookies in session defaults. Timeouts, TLS verification and payment idempotency are unchanged; payment POSTs are not automatically retried by this transport. No client changes are needed for connection reuse.
  • Reconciliation uses bounded batches and an independent transaction per payment. One failure no longer rolls back other payments. Financial changes and outgoing notifications still commit together.
  • Reconciliation selects the correct live/test provider credentials and respects existing payout reservations, avoiding a second debit for reserved payouts. Reservations are released on confirmed provider failure, not an ambiguous pending response.
  • Automatic webhook sweeps select at most 50 deliveries and share four senders per worker process, including across overlapping sweeps. A slow client no longer holds up every other delivery. More worker processes increase the overall concurrency.
  • Automatic and manual results cannot overwrite a newer delivery claim. Manual webhook dispatch can return HTTP 409 if its claim changed while the request was waiting. Its delayed result cannot overwrite the newer claim.
  • API routes, payloads, signatures, response fields and the ten-attempt retry policy are unchanged. No new migration or dependency is required.
Your webhook receiver must accept concurrent requests, deduplicate delivery IDs atomically and protect transaction state from older notifications. Ordered or exactly-once HTTP delivery is not guaranteed. See Delivery concurrency and ordering for receiver guidance.

​
[0.13.0] - 2026-10-02

This release includes optional pagination and backend compatibility cleanup. API routes remain under /api/v1, and webhook payload versions are unchanged.

​
Pagination and compatibility

  • You can opt into bounded pages and server-side search on user and wallet lists. Existing calls without the new options still return arrays containing the full list.
  • Wallet sorting applies before pagination; optional summaries describe all matching records, with balances kept separate by currency.
  • The dashboard loads 50 records at a time and reports a compatibility error if the API does not provide the required summary headers.
  • No schema migration or new dependency is required. See List users and List wallets for parameters and compatibility.
  • Wallet transaction history also supports optional pages, full-history search and matching summary headers. The dashboard loads 50 newest-first transactions with completed amounts separated by currency; summaries are not page-only totals.
  • Existing wallet-history calls retain their full-array ordering and empty-history HTTP 404. Opted-in reads return unique transactions and empty arrays when no matches remain. See Wallet transactions for parameters and summary semantics. SDK signatures are unchanged.

​
Backend maintenance

  • Deprecated Python typing aliases, SQLModel session calls, Pydantic declarations and Stripe exception imports use their supported replacements. You do not need to change your request bodies, authentication headers or stored API keys.
  • Existing environment variable names and migration history are unchanged; no database migration or dependency upgrade is required for this release.

​
[0.12.0] - 2026-10-01

This release includes payment concurrency, dashboard performance and atomic payment notifications.

​
Performance and compatibility

  • Blocking wallet/payment work runs outside the API event loop so slow provider calls do not block unrelated requests. Provider response times and available worker/database capacity still limit throughput.
  • Stripe requests use application-specific credentials without modifying a process-global key. Your authentication headers and raw API keys are unchanged.
  • Dashboard analytics combine database queries while preserving response fields.
  • API routes remain under /api/v1; no new database migration is required.

​
Payment notifications

  • Payment handlers, reconciliation, transfers and escrow record outgoing events and matching deliveries in the same database transaction as their local financial changes. If event recording fails, those local changes roll back. This cannot reverse money already moved by a payment provider.
  • Delivery remains asynchronous. The worker discovers committed deliveries on its 30-second scheduled sweep; queue outages and retries can delay delivery. Do not expect the webhook to arrive before the initiating API request returns.
  • Monime failed-deposit callbacks also record payment.failed events. Receivers subscribed to this event or payment.* should handle the failure state.
  • Payload versions, signature verification and API routes are unchanged. Keep deduplicating delivery IDs; this does not promise exactly-once HTTP delivery or automatically recover historical missing notifications.

​
[0.11.0] - 2026-09-08

API release 0.11.0 keeps the /api/v1 route prefix and strengthens webhook security.

​
Potentially breaking changes

  • Live webhook delivery requires public HTTPS with valid TLS. Redirects are blocked, including trailing-slash and HTTP-to-HTTPS redirects.
  • Destination safety is checked again for every delivery. Private/internal destinations, mixed public/private DNS answers and URL credentials are rejected.
  • Missing, inactive or unreadable signing secrets no longer fall back to unsigned HTTP requests. Failures are recorded and follow the bounded retry policy.
  • Manual dispatch of an inactive subscription returns HTTP 409.

​
Response and dashboard changes

  • Delivery responses expose nullable processing_started_at. Clients must handle the processing status and tolerate the new response field.
  • The dashboard distinguishes Processing, Retry pending and Stopped, shows errors and attempt counts, and flags possibly stalled deliveries within the latest 50 records. These are snapshot counts, not global queue totals.
  • The retry limit is 10 total attempts, including preparation failures. This corrects earlier documentation that described 10 retries after the first attempt.
The event payload format, payload version and HMAC signature format are unchanged. Review the integration checklist to ensure your webhook receiver meets these requirements.

​
[0.10.0] - 2026-06-30

​
Added

  • Escrow webhook events: escrow.held, escrow.released, and escrow.refunded are now emitted through the webhook subscription pipeline, so you can react to escrow state changes.
  • Editable webhook subscriptions: Update a subscription’s events and active status from the dashboard in place, without deleting and recreating it (which previously rotated the signing secret).

​
Changed

  • String app_user_id: app_user_id now accepts arbitrary external identifiers (e.g. user_123, UUIDs), not just integers. Existing numeric values keep working.

​
Documentation

  • Split the Webhooks guide into dedicated Events, Security, and Testing pages.

​
[0.9.0] - 2026-06-02

​
Added

  • Application base currency: Choose and change your application’s base currency (USD or SLE) during registration and updates.
  • Multi-currency formatting: Amounts across the dashboard now use thousands separators and the correct currency symbol for your base currency.

​
[0.8.0] - 2026-04-24

​
Added

  • Dashboard Analytics API: New GET /api/v1/analytics/dashboard aggregating volume, net revenue, active users, wallet counts, a 14-day volume chart, and recent activity.
  • Expanded transaction analytics: GET /api/v1/transactions/admin/analytics now returns success rate, average amount, and volume breakdowns by type and currency.

​
[0.7.0] - 2026-01-28

​
Added

  • Full multi-currency support: Applications can operate natively in SLE or another base currency; transactions, fees, and balances reflect it, with automatic SLE↔USD conversion only when a provider requires it.
  • Currency-aware notifications: SMS and event payloads adapt to your base currency.

​
Fixed

  • Corrected Monime amount unit and fee-percentage handling that could mis-credit wallets.

​
[0.6.0] - 2026-01-16

​
Added

  • Stripe identity verification sync: Endpoint to re-sync Stripe Connect verification requirements and status.
  • Monime webhook self-healing: Automatic transaction recovery from webhook metadata after failed requests.

​
Fixed

  • Atomic transfers and database connection stability improvements.

​
[0.5.0] - 2026-01-12

​
Added

  • Security hardening: SHA-256 hashed API keys and secrets, SSRF protection on outbound webhooks, PII/secret log redaction, admin brute-force lockout with per-IP rate limiting, and lock-first idempotency to prevent double-processing under concurrency.

​
[0.4.0] - 2025-12-20

​
Added

  • Escrow: Dedicated escrow wallet plus a fund-management API — POST /api/v1/escrow/hold, POST /api/v1/escrow/{id}/release, and POST /api/v1/escrow/{id}/refund.

​
Earlier releases (0.1.0 – 0.3.x, 2025)

Initial platform: application onboarding and API credentials, user wallets, card deposits (Stripe) and mobile-money deposits (Monime), wallet-to-wallet transfers, payouts, background reconciliation, and outbound webhooks.