GuidesAPI ReferenceChangelog
Changelog

v1.0.23

destination.amount now returns net amount

The Transactions API now returns the actual net amount credited or received on the destination.amount field, replacing the previous gross/expected amount for deposits and withdrawals.

GET All Transactions

https://developer.1money.com/reference/list_transactions

  • destination.amount now reflects the net amount credited or received (after fees), not the previous gross/expected amount
  • Applies to fiat deposits (FIAT_IN), fiat withdrawals (FIAT_OUT), and crypto withdrawals (CRYPTO_OUT)
  • Conversions, internal transfers, and crypto deposits are unchanged
  • Historical records have been backfilled to the new (net) value so past transactions reflect the updated numbers
  • source.amount and fee are unchanged

GET Transaction By ID

https://developer.1money.com/reference/retrieve_transaction

  • Same semantic change — destination.amount returns the net amount credited or received
  • Historical records retrieved by ID also reflect the backfilled value
  • All other fields (source.amount, fee, amount_type, etc.) are unchanged

⚠️ Breaking Change: destination.amount now returns the net amount

Any integration that computed destination.amount - fee to derive the net amount will need to be updated.

Why: The previous behavior required clients to subtract fee from destination.amount to derive the actual credited/received amount, and this derivation was inconsistent between SendAmount and ReceiveAmount withdrawal flows. Returning the net amount directly provides a single, unambiguous value that matches what the recipient actually received.

Migration: Use destination.amount directly as the net amount — do not subtract fee. If the gross amount is still required, use source.amount for withdrawals, or destination.amount + fee for deposits. Webhook payloads are not affected: withdrawal webhooks do not carry an amount field, and deposit webhooks already reported the net amount.