Changelog

All notable client-facing changes to this project will be documented in this file.

[2.23.0] - 2019-07-18

Changed

  • /payments/notify/{paymentId} is now POST request instead of GET

Added

  • /anomalies/notify/{paymentId}
  • /payouts/notify/{paymentId}

[2.18.7] - 2019-05-21

  • Require /v2 as URL prefix for API calls

[2.16.2] - 2019-03-39

  • Add support for AUD and JPY

[2.14.0] - 2019-01-15

Added

[2.12.3] - 2018-12-03

Added

  • exchangeRate to POST /payments/new response (see Request New Payment)
  • exchangeRate to POST /payouts response (see Payouts)
  • exchangeRate to payments, payouts and anomaly notifications (see Notifications)

[2.12.0] - 2018-11-19

Added

  • QUEUED status has been added to payouts(see Payout states)
  • notificationUrl parameter to POST /payouts(see Payout notifications)
  • Payouts now support Bech32 addresses

Removed

  • GET /deprecated-payouts endpoint has been removed
  • POST /deprecated-payouts endpoint has been removed

[2.8.0] - 2018-09-03

Changed

  • timeTo query parameter (date-time) in GET /payouts becomes treated as exclusive

Deprecated

  • GET /v2/payments/anomalies - GET /v2/anomalies should be used instead

Removed

  • Removed btcPercentageToKeep from POST /v2/payments/new

[2.7.3] - 2018-06-25

Added

  • HMAC signed notifications

[2.7.1] - 2018-06-18

Added

  • autoApprove option when creating payouts
  • /payouts/limit endpoint to show available and used payout quota

[2.7.0] - 2018-06-14

Changed

  • end query parameter (date-time) in GET /payments/anomalies becomes treated as exclusive
  • transactionId renamed to paymentId in GET /v2/payments/{id} response
  • transactionId renamed to paymentId in POST /v2/payments/new response
  • transactionId renamed to paymentId in GET /v2/payments/{limit}/{offset}: response
  • transactionId renamed to paymentId in regular payment notification body
  • query parameter transactionId renamed to btcTxId in GET /v2/payouts

Deprecated

  • transactionId field in GET /v2/payments/{id} - paymentId should be used instead
  • transactionId field in POST /v2/payments/new - paymentId should be used instead
  • transactionId field in GET /v2/payments/{limit}/{offset}: - paymentId should be used instead
  • transactionId field in regular payment notification body - paymentId should be used instead
  • transactionId query parameter in - GET /v2/payouts - btcTxId should be used instead

[2.6.0] - 2018-05-17

Deprecated

  • GET /payouts is now GET /deprecated-payouts
  • POST /payouts is now POST /deprecated-payouts

Added

  • new payout mechanism: POST /payouts and POST /payouts/approve

Changed

  • GET /payouts returns updated format

[2.5.1] - 2018-05-07

Added

  • /anomalies/{anomalyId} endpoint
  • anomalyId to anomaly response JSON

[2.5.0] - 2018-05-07

Added

  • paid and paidBtc attributes to payment responses and notifications
  • notificationType to regular and anomaly notifications
  • merchantTransactionId to anomaly notifications

[2.4.0] - 2018-04-26

Added

  • Internal fixes

[2.3.0] - 2018-04-13

Added

  • Anomaly notifications
  • New anomaly view
  • Payment explorer

[2.2.1] - 2018-03-13

Added

  • Payout functionality in API
  • Optional comment field for GET /payouts and POST /payouts
  • GET /estimate-payout/fiat-to-btc endpoint
  • GET /estimate-payout/btc-to-fiat endpoint

[2.1.0] - 2018-02-28

Added

  • Payout functionality in admin panel

[2.0.1] - 2018-02-02

Changed

  • Expiration time for payments is now 30 minutes instead of 15