Skip to main content

Changelog

Keep up to date with Paxos Platform changes.


We deploy new features, fix bugs, and update the documentation on a regular basis. Use this record to review recent and upcoming changes to the Paxos Platform, including breaking changes.

✉️ Question? Contact us: Crypto Brokerage | Commodities Settlement | Help Desk

🔔 Subscribe: RSS | Atom | JSON

Upcoming Changes

  • v1 API, v2 API Add optional field secondary_activity_status parameter to List Transfers, Get Transfer, Get Activities, and Get Activity API endpoints. This field is used to support new transfer processes and features. The changes are planned to be rolled out no earlier than May 8, 2024.

Breaking Changes

  • Funding: Paxos is upgrading its wallet infrastructure, impacting customers' crypto deposit addresses for BTC, ETH, BCH, LTC and all ERC20 tokens. This planned change is part of our commitment to continuous product and security improvements. Users will be required to retrieve the new crypto deposit address via the UI or CreateDepositAddress API no earlier than February 15, 2024, and no later than June 13, 2024. Old deposit addresses will come with a deprecated warning until June 13, 2024. After this date they will no longer be supported.
  • FIX: In the upcoming weeks, Paxos plans to begin updating the FIX infrastructure to improve performance, reliability and security for FIX connections. This change enables multiple FIX connections for a single account and improves TLS certificate management, among other changes. All existing FIX users are required to migrate to the new infrastructure no later than May 4, 2024. See the migration guide or contact your Paxos Representative for details.

  • v2 API: Add new attribute compatible_crypto_networks to the Create Deposit Address and List Deposit Addresses API responses. This field contains the compatible networks with the created or already existing deposit address.

  • v2 API: Add Insufficient Funds 403 error response to Create Fiat Withdrawal endpoint.

  • v2 API: Add new Fiat Transfer APIs which allow for automatic funding and withdrawal of fiat in a Paxos account.

  • v1 API, v2 API: Update REST Transfer API Rate Limit to 20 requests per second.
    • /v1/transfers/peer
    • /v1/transfers/profile
    • /v1/crypto-withdrawals
    • /v2/transfer/internal
    • /v2/transfer/crypto-withdrawals

  • v1 API, v2 API: The address1, city and province fields are no longer explicitly marked as required in the MailingAddress object. The v1 API CreateBankAccount endpoint and the v2 API Create Fiat Account and Update Fiat Account endpoints will continue to validate these fields if they exist.

  • FIX: Add SelfMatchPreventionID (tag 2362) to prevent matching against an opposite side order submitted by the same Crypto Brokerage customer. If this tag is not submitted, an order that matches against another order submitted by the same customer will cancel the original resting order.

  • Sandbox: PYUSD trading pairs are available in the Sandbox environment for REST and FIX users. All relevant endpoints support PYUSD-based trading pairs (for example, BTC:PYUSD and ETH:PYUSD among other). Contact your Paxos Representative for details.

  • v2 API: Add optional field self_match_prevention_id to Create Order. This field is used to prevent matching against an opposite side order submitted by the same Crypto Brokerage customer. If this field is not submitted, an order that matches against another order submitted by the same customer will cancel the original resting order.

  • Docs: Correctly identify the markets, transfer_type, account_id and tax_year query parameters as required to reflect actual API behavior. Auto-generated and other clients relying on the OpenAPI spec file may require updates.

  • Reconciliation Reporting: As part of reconciliation reporting improvements, we are incrementally rolling out a few changes to the Profile Balances Report.
    • The report no longer lists assets in ordered asset order. New order will be balance_at time (start time then end time) first, and asset alphabetical second.
    • The report now shows assets as long as there is one transaction that happened in history, even if no transactions in the asset were reported during the reporting period. Previously, assets with balances would show up in the report only if there was a transaction in the reporting period or if the asset was pre-configured to show up in the report regardless of transaction history.

  • Docs: Content updates and fixes.
    • Clarify HRQ Quickstart TIP text to state a single Quote Execution default maximum size is $50K USD. Previously the TIP stated $100K USD.
    • Update Stablecoin Conversion > Assets to reflect that a conversion uses the lowest maximum precision.

  • v2 API: Enable HRQ users to buy and sell PYUSD using the Create Quote Execution endpoint. Allow all HRQ users to retrieve PYUSD using the List Quotes endpoint.
  • v2 API: Add PYUSD to the List Historical Prices endpoint.
  • v1 API: Enable PYUSD withdrawal. All PYUSD withdrawals debit USD balance only. Enable USD deposit auto-conversion to PYUSD withdrawal.
  • v2 API: Enable PYUSD withdrawals using the Transfers API with the option to debit USD balance. Add values asset=PYUSD and balance_asset=USD to the Create Crypto Withdrawal request.
  • Wallet UI: Enable PYUSD withdrawals. All PYUSD withdrawals debit USD balance only. Enable USD deposit Auto-Transfer to PYUSD withdrawal.
  • Docs: Add sourcing and implementation information to the Paxos Documentation.

  • v2 API: Add assets=PYUSD query parameter to List Profile Balances. Add asset=PYUSD path parameter to Get Profile Balances. Add ”asset”: “PYUSD” to Create Sandbox Deposit request body schema. Add PYUSD to properties base_asset, quote_asset, commission_asset and rebate_asset for the List Executions, List Quotes, List Quote Executions, Create Quote Execution and Get Quote Execution endpoints. About PYUSD.

  • Docs: Add Held Rate Quotes Quickstart guide, Ledgering Strategy and Orders & Quotes FAQ best practice guides.

  • V2 API: Add a default of 100 results to the limit query parameter and restrict the maximum page limit to 1,000 for the Paxos v2 API List Deposit Addresses service. Learn more.

  • v1 API: Add new schema IntrabankDepositInstructions and new field PaxosBankAccount to the GetProfileDepositInstructions endpoint. IntrabankDepositInstructions includes fields memo_id, beneficiary_name account_number, and type. PaxosBankAccount:intrabank is a generic IntrabankDepositInstructions that populates whenever any of the other intrabank type fields (for example, cbit) are populated (the respective existing fields will also be populated and supported). Future intrabank networks will be contained in intrabank only.

  • v1 API: CreateBankAccount endpoint and CustomerBankAccount schema have a new optional field: IntrabankWithdrawalInstructions.
    • This generalizes the existing intrabank withdrawal instructions into a single field. Clients may specify the new IntrabankWithdrawalInstructions (which consist of beneficiary_name, account_number, and CustomerBankAccount.Type) as an alternative to existing network-specific intrabank details (account_number can be a wallet address for networks like CBIT).
    • CustomerBankAccount will fill in IntrabankWithdrawalInstructions IN ADDITION TO the existing intrabank withdrawal instructions in responses. Future intrabank networks will only be supported via IntrabankWithdrawalInstructions (as opposed to their own field). The Type field on IntrabankWithdrawalInstructions will differentiate the network types.
    • Existing network-specific instructions are deprecated, but will continue to work.

  • Docs: Add FIX overview, onboarding, certification and best practices documentation.

  • v2 API: Add error code MARKET_CONDITIONS_PREVENTED_EXECUTION to Create Order response.
  • FIX: Add additional detailed failure reason (tag 58) Market conditions have invalidated this order.

  • Docs: Enable RSS, Atom and JSON feeds for the Paxos Changelog.

  • Docs: Add new parameter precisions to Orders, Precision and Rounding best practice guide.

  • Docs: Add crypto brokerage and stablecoin and overview pages. Add Crypto Brokerage Orders, Precision and Rounding best practice guide.

v2 API: Add value PROVE to parameter person_details.passthrough_verifier_type on Create Identity and Update Identity request and response for the v2 REST API. Add value PROVE to parameter person_details.passthrough_verifier_type on List Identities and Get Identity response.

  • v1 API: Disable wire deposit instructions for Silvergate. Both GetProfileDepositInstructions and GetCryptoAddressAutoconversionInstructions now return NULL no longer return SEN Deposit Instructions nor Silvergate wire deposit instructions. These endpoints still return SigNet Deposit Instructions and memo IDs.
  • v1 API: Deprecate CreateSenWithdrawal. The endpoint now returns 403 error - Forbidden.

  • Add value FIS to parameter person_details.passthrough_verifier_type on Create Identity and Update Identity request and response for the v2 REST API. Add value FIS to parameter person_details.passthrough_verifier_type on List Identities and Get Identity response.
  • Paxos Retail UI: Reduce Market Order maximum size for BTC and ETH to $25,000. Does not apply to API initiated orders.

  • Sandbox: Require crypto_network on all requests to the Create Crypto Withdrawal and Create Sandbox Deposit v2 API endpoints. Learn more.

  • Production: Return a 500 error only when all requested markets fail to be retrieved for the v2 REST API List Prices service. Any single market that failed to be retrieved is excluded from the response.

  • Production: Return a 500 error only when all requested markets fail to be retrieved for the v2 REST API List Prices service. Any single market that failed to be retrieved is excluded from the response.

  • Ensure results match filtering criteria when viewing paginated results for v2 REST API endpoints List Transfers and List Deposit Addresses.

  • Enable statuses TIN_VERIFICATION_VALID, TIN_VERIFICATION_ERROR and TIN_VERIFICATION_PENDING for parameter tin_verification_status on all Identity v2 REST APIs. The new statuses apply to US-based users and are returned only when tax_details exist.

  • Sandbox: Return a 500 error only when all requested markets fail to be retrieved for the v2 REST API List Prices service. Any single market that failed to be retrieved is excluded from the response.
  • Improve Request samples dropdown UI when multiple examples exist in the v2 REST API Reference Docs.

  • Add metadata[“origin”] = “v1” to Crypto Withdrawal transfers created via the CreateCryptoWithdrawal v1 REST API endpoint. This allows Crypto Withdrawals created via the v1 REST API to be distinguished from those created using the v2 REST API.

  • Update itBit REST API documentation with new End of Life date.
  • Require v2 REST API docs consume most recent specification file.

  • Provide a snapshot_at field in the v2 REST API List Prices response so API consumers can understand the validity of a price and validate the time at which a price was given.

  • Sandbox: Enable parameter group_id for linking the debit and credit legs of an Internal Transfer on the v2 REST API. Add group_id to Create Internal Transfer, List Transfers and Get Transfer responses when the response includes an Internal Transfer. Add query parameter group_ids to List Transfers.
  • Add GroupID to the Profile Transactions Reconciliation Report.
  • Enable statuses TIN_VERIFICATION_VALID, TIN_VERIFICATION_ERROR and TIN_VERIFICATION_PENDING for parameter tin_verification_status on all Identity v2 REST APIs. The new statuses apply to US-based users and are returned only when tax_details exist.
  • Provide a snapshot_at field in the v2 REST API List Prices response so API consumers can understand the validity of a price and validate the time at which a price was given.