​
Stablepay Change Log

This document provides a chronological list of notable changes, updates, and improvements made to the Stablepay platform. We recommend all developers to regularly review this change log to stay informed about new features, optimizations, deprecations, and potential breaking changes.

​
[Added]

  • Updated endpoint: /tx/createTransferRequest to take new acquirer field
  • Deprecated devnet field, real and test transaction have the same metadata, no need for discriminator
  • Atomic disbursement transactions

​
[Unreleased]

  • New endpoint: /v2/transactions/generateReference to generate reference for transactions
  • Support for custom transaction metadata
  • Webhook notifications for failed transactions

​
Added

  • Better Error handly for failed disbursement

​
Changed

  • Improved transaction processing speed

​
Deprecated

  • Legacy reporting API (to be removed in v2.5.0)

​
[v2.1.0] - 2024-08-15

​
Changed

  • Change API Keys
  • Optimized database queries for faster response times

​
Fixed

  • Issue with decimal precision in high-value transactions
  • Rare race condition in concurrent withdrawals

​
[v2.0.0] - 2024-05-20

​
Added

  • Complete API redesign for improved developer experience
  • Real-time payment status retrieval

​
Changed

  • Authentication mechanism: Now using JWT
  • Renamed several API endpoints for consistency (see migration guide)
  • Improved error messages with more detailed information

​
Deprecated

  • v1 API (to be removed on 2024-05-01)

​
Removed

  • Support for legacy integrations

​
[v1.5.2] - 2024-03-23

​
Fixed

  • Security patch for potential XSS vulnerability.
  • Corrected inconsistent behavior in split wallet generation

​
[v1.5.1] - 2024-03-22

​
Fixed

  • Rare issue with transaction rollback in high-concurrency scenarios

​
[v1.0.0] - 2024-03-14

​
Added

  • Initial release of Stable Pay API
  • Basic payment processing functionality
  • User authentication and authorization
  • Transaction history and reporting
  • Webhook notifications for payment events

​
How to Use This Change Log

  • Version Numbers: We use semantic versioning (MAJOR.MINOR.PATCH).
  • Categories: Changes are grouped into Added, Changed, Deprecated, Removed, and Fixed.
  • Dates: Release dates are in YYYY-MM-DD format.
  • [Unreleased]: This section contains upcoming changes that are not yet released.

​
Staying Updated

To ensure you’re always using the latest features and following best practices:

  1. Regularly check this change log for updates.

For any questions about these changes or for migration assistance, please contact our developer support team at hello@stablepay.com.