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.

Breaking Changes

  • v1 API End of Life Notification: No earlier than November 30, 2024, we are sunsetting the Paxos v1 APIs. This change ensures all Paxos customers are using supported APIs. Customers can begin migrating as most functionality available via the v1 APIs is already available in Paxos v2 APIs. The remaining gaps will be closed by mid Q3, 2024. We recommend you test your integrations in Sandbox during the testing window. See Migrating from v1 to v2 API.

  • v2 API: Add optional crypto_tx_hashes filter to the List Transfers endpoint.
  • v2 API: Add the following document types to Identity Documents APIs: AML_DOCUMENTS, FUND_STRUCTURE_CHART, FUND_MANAGER_REGISTRATION, MEMORANDUM_OF_ASSOCIATION, ORGANIZATIONAL_CHART, FOUNDATION_BY_LAWS, APPOINTMENT_OF_GUARDIAN_EVIDENCE, LEGAL_DOMICILE_OF_BENEFICIAL_OWNERS, GOVERNING_BODY_MEMBER_NAMES.

  • v2 API: Add three new optional fields to the customer_due_diligence object of the Identity API (Create Identity and Update Identity).
  • v2 API: Add new ENUM value GOVERNMENT_BENEFITS to the customer_due_diligence object field source_of_funds in the Identity API (Create Identity and Update Identity).

  • v2 API: Add is_merchant field to the Identity API (Update Identity, Get Identity, List Identities).

  • FIX: Enforce a maximum of 150 messages per second, per session.

  • v2 API: All metadata specified when creating a crypto deposit address is now inherited by deposit activities.

  • 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.

  • v2 API: Add optional is_merchant boolean field to the Create Identity request body and the List Identities, Create Identity, Get Identity and Update Identity responses.

  • Breaking Change: Update 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 Support 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 Support 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.