Changelog

​

Latest Updates

Stay informed about new features, improvements, and bug fixes in the HOST Pay API.

---

​

[0.3.0] - 2026-03-22

​

Added

• Configurable Base Currency: Applications can now define their own base currency (e.g., USD, SLE) for all internal accounting and wallet balances.
• Native Monime Integration: Direct, native support for Sierra Leone’s mobile money ecosystem (Orange Money, Africell Money) through the Monime provider API.
• Automatic USSD Generation: Automatic generation of USSD codes for mobile money deposits, simplifying the customer experience.
• Real-time Exchange Rates: Integrated exchange rate service for automatic conversion between user-entered SLE and the application’s base currency.
• Mock Monime Service: Enhanced sandbox environment for testing mobile money flows without using real funds.

​

Changed

• Currency-Aware Handlers: Transaction deposit and payout handlers now dynamically handle conversions based on the application’s configured base currency.
• Wallet Balances: Standardized all wallet balance tracking and history to use the application’s base currency.

---

​

[0.2.2] - 2025-01-16

​

Fixed

• Mobile Money Deposit Response: Fixed missing transaction_id field in mobile money deposit response
  • Added transaction_id to the top level of the response payload for consistency with card deposits
  • Resolves Django client integration issue: “Failed to get transaction_id from HostPay response”
  • MockMonimePaymentService now works correctly with test API credentials
  • Ensures consistent response structure across all deposit methods (card and mobile money)

​

Changed

• Standardized deposit endpoint responses to always include transaction_id at the top level
• Improved API consistency between test mode (MockMonime) and live mode (real Monime) operations

---

​

[0.2.1] - 2025-01-15

​

Fixed

• Wallet Enable Validation: Fixed bug where wallets could be enabled even when the user account was disabled
  • Added validation to check user status before allowing wallet enable
  • Returns clear error message: “Cannot enable wallet: User account is disabled. Please enable the user account first.”
  • Prevents inconsistent state where wallet is active but user is disabled
  • Maintains data integrity and proper account status hierarchy

​

Security

• Enhanced wallet state management to prevent unauthorized wallet access through disabled user accounts

---

​

[0.2.0] - 2025-01-15

​

Added

​

User & Wallet Status Management

• User Enable/Disable Endpoints
  • POST /api/v1/users/{user_id}/disable - Disable a user and automatically disable their wallet
  • POST /api/v1/users/{user_id}/enable - Enable a user and automatically enable their wallet
  • When a user is disabled, their associated wallet is automatically disabled
  • Cascading behavior ensures consistent state between user and wallet
• Wallet Enable/Disable Endpoints
  • POST /api/v1/wallets/{wallet_id}/disable - Disable a wallet independently without affecting user status
  • POST /api/v1/wallets/{wallet_id}/enable - Enable a wallet independently without affecting user status
  • Provides granular control over wallet functionality
  • User status remains unchanged when wallet is disabled separately

​

Status Filtering

• Query Parameter Filtering
  • GET /api/v1/users/?is_active=true|false - Filter users by active status
  • GET /api/v1/wallets/?is_active=true|false - Filter wallets by active status
  • Optional parameter - returns all records if not specified
  • Improves API usability for managing active/inactive entities

​

Transaction Validation

• Status-Based Transaction Prevention
  • All transaction endpoints now validate user and wallet status before processing
  • Deposits (card & mobile money) - checks user and wallet active status
  • Transfers - validates both sender and recipient user and wallet status
  • Payouts (mobile money & Stripe) - ensures user and wallet are active
  • Returns 403 Forbidden with clear error messages when accounts are disabled
  • Error messages: “Transaction failed: User account is disabled” or “Transaction failed: Wallet is disabled”

​

Security

• Enhanced security by preventing transactions on disabled accounts
• Prevents unauthorized transactions on suspended users or wallets
• Enforces data integrity through status validation

​

Changed

• Improved error handling with specific status codes (403) for disabled account operations
• Enhanced logging for all status change operations
• Updated API documentation to reflect new endpoints and parameters

---

​

[0.1.1] - 2025-01-10

​

Added

• Application wallet service for fee collection
• Transaction fee percentage configuration per application
• Platform-managed application fees on transfers
• Enhanced webhook event system for transfers and payouts

​

Changed

• Improved transaction handlers with better error messages
• Enhanced Stripe Connect payout workflow
• Better exchange rate handling for mobile money transactions

​

Fixed

• Transaction fee rounding issues
• Correct decimal handling for transaction amounts
• Fixed webhook event delivery for payout transactions

---

​

[0.1.0] - 2025-01-01

​

Added

• Initial API Release
  • User management endpoints
  • Wallet creation and management
  • Transaction processing (deposits, transfers, payouts)
  • Stripe integration for card payments
  • Monime integration for mobile money
  • Webhook system for event notifications
  • Test and Live environment support
  • API key authentication
  • Rate limiting
  • Admin dashboard for application management

​

Features

• Multi-application support with isolated schemas
• Dual-mode operation (Test and Live)
• Multiple payment methods (Card, Mobile Money, Wallet Transfer)
• Comprehensive error handling
• Transaction history and reporting
• Real-time webhook notifications

---

​

Version History

​

Upgrade Guide

When upgrading between versions, review the changelog for:

• Breaking Changes 🔴 - Require code updates
• New Features 🟢 - Optional enhancements
• Bug Fixes 🟡 - Improvements and corrections

​

Stay Updated

​

Feedback

Have suggestions or found an issue?