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.

  • v2 API: Add parameter last_kyc_refresh_date to the Identity API for setting the timestamp the Identity last underwent periodic refresh.

  • v2 API: Add Deactivate Profile endpoint to the Profile API.
  • v2 API: Remove the unused value RANSOMWARE from the institution_details.institution_sub_type enum on the Identity API.

  • v2 API: Add enum value TRAVEL_RULE_REJECTED to the secondary_statuses parameter for List Transfers and Get Transfer responses. TRAVEL_RULE_REJECTED may be used as a query parameter for List Transfers.
  • Breaking Change: The Paxos v1 API has reached its end of life. Paxos no longer supports the v1 API. The v2 API fully supports all current API use cases.

  • v2 API: Add include_deactivated query parameter to the Get Profile endpoint to enable retrieving a deactivated Profile.

  • Reconciliation Reporting: We're enhancing our reconciliation reports with two new fields: OrchestrationID links all related transactions within a single end-to-end flow. OrchestrationRuleID identifies which automation rule triggered the transaction set. These additions make it easier to track multi-step transactions and map them to their triggering rules, improving audit trails and simplifying reconciliation processes for treasury and enterprise payment operations.

  • v2 API: Add Paxos Transfers to enable asset movement between two Entities belonging to the same Organization or to a different Organization on the Paxos platform.
  • v2 API: Add Update Profile to allow changing the nickname of an existing Profile.
  • v2 API: The identity_id parameter is now optional with Create Fiat Account. Those with 3rd-Party integrations initiating transfers on behalf of their end users must continue to use the parameter.

  • v2 API: Enable optional business_description parameter for the Create Identity, Update Identity, Get Identity and List Identities endpoints.
  • v2 API: Add REAL_ESTATE and OTHER_SOURCE_OF_WEALTH to the customer_due_diligence.source_of_wealth enumeration on the Identity APIs.

  • 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