Latest Articles

When a crypto withdrawal in an orchestration is blocked because the destination address has no Travel Rule information, the orchestration stays PROCESSING and now reports the travel_rule_info_required sub-status with awaiting_action_from set to AWAITING_ACTION_FROM_CLIENT. Add the information with Put Crypto Destination Address and the withdrawal proceeds on its next retry. Subscribe to the new orchestration.status_details.travel_rule_info_required webhook to be notified. See the Webhook Integration Guide.

Create Crypto Withdrawal Fee accepts optional identity_id and memo to select the saved destination address, as Create Crypto Withdrawal does. For PTC customers, once enforcement applies to your account, quoting an above-threshold withdrawal to an address without valid Travel Rule metadata returns the same 403 Travel Rule Information Required as the withdrawal.

Travel Rule: Inline beneficiary ignored on crypto withdrawals for PTC customers: Once enforcement applies to your account, the beneficiary field on Create Crypto Withdrawal is accepted but ignored; only the travelrule_metadata saved on the destination address counts. PTE customers are unaffected.

Travel Rule: $30 sandbox threshold: Sandbox applies PTC Travel Rule checks from $30 USD-equivalent, so you can test with small sandbox balances. Production stays at $3,000. See the Travel Rule developer guide.

Put Crypto Destination Address now accepts an optional memo, and it is returned by Put and List Crypto Destination Addresses. The field applies to Stellar (text memo up to 28 bytes), XRP Ledger (destination tag from 0 to 4294967295), and Cosmos (text memo up to 256 bytes). The Dashboard shows the same field when you add a withdrawal address on those networks.

New identity.tax_documentation.status_changed webhook notifies you when an identity's tax documentation status changes. Use the Get Event API to retrieve the identity_tax_documentation_status_change object.

PayPal USD (PYUSD) is live on Stable (EVM-compatible Layer 1, chain ID 988) for deposits, withdrawals, and transfers. See PYUSD on Main Networks and PYUSD on Test Networks for token and Supply Control contract addresses, and Assets and Blockchains for supported networks and required confirmations.

Added documentation for partner-collected W-9, W-8BEN, and W-8BEN-E tax forms, including Submit Tax Documentation and Get Tax Documentation. The documentation also covers the TAX_DOCUMENTATION Identity requirement, its associated reason codes, Paxos Trust Company (PTC) population scope, business-member exemption, and January 1, 2027 enforcement date.

The EDD document workflow now emits richer events and exposes per-document upload status.

• The identity_documents_required event object now includes a documents array carrying each requested document's document_type, required flag, and explanation — covering both required and optional documents. The flat required_documents array is deprecated.

• New identity.documents_accepted and identity.documents_denied webhooks signal the outcome of an EDD review and return the identity_edd event object.

• List Identity Documents now returns a per-document status (NOT_STARTED, PENDING_UPLOAD, REJECTED_UPLOAD, COMPLETED_UPLOAD), a required flag, and an upload_link. The top-level pending_documents field is deprecated.

See the updated Enhanced Due Diligence guide.

The List Orchestrations endpoint now supports an updated_at timestamp range filter (updated_at.lt, updated_at.lte, updated_at.eq, updated_at.gte, updated_at.gt), mirroring the existing created_at filter.

Setting an updated_at range orders results by updated_at ascending (oldest change first) and returns a page cursor keyed to that ordering, so you can page forward from your last checkpoint instead of re-polling every non-terminal orchestration.

• created_at and updated_at are mutually exclusive. Setting both returns a 400.

• updated_at ordering is ascending only. Combining updated_at with order=DESC returns a 400.

• Preserve the updated_at filter on every follow-up request that supplies a page_cursor.

See Incremental Polling by Update Time for the recommended polling loop.

The List Identities endpoint now supports three new filters that match against an identity's active status_details.requirements:

• requirement_types — filter by requirement type (ID_VERIFICATION, DOCUMENT_VERIFICATION, SCREENING_CHECK, COMPLIANCE_CHECK, ENHANCED_DUE_DILIGENCE, MEMBERS, KYC_REFRESH, TAX_DETAILS_VERIFICATION).

• requirement_statuses — filter by requirement status (PENDING, FAILED).

• requirement_awaiting_action_from — filter by which party must act (CLIENT, PAXOS).

Each is a repeated query parameter. An identity is returned only when it has at least one active requirement satisfying all requirement_* filters that are set. See the Identity Lifecycle guide for more on requirements.

Added API reference documentation for the User Audit Logs API, which retrieves a log of actions performed by human users in the Paxos Dashboard, with filtering by method, path, domain, time range, and status code. Requires the user_audit_logs:read_audit_log scope.

Global Dollar (USDG) is live on Mantle (chain ID 5000) for deposits, withdrawals, and transfers. See USDG on Main Networks and USDG on Test Networks for token and Supply Control contract addresses, and Assets and Blockchains for supported networks and required confirmations.

The Monitoring Addresses, Statements, and Payments APIs are no longer available. Their legacy API references and Dashboard guides have been removed. Use the Rewards Engine API and the Rewards Engine Dashboard guides instead.

Access to the Dashboard Fund button and the Create Sandbox Deposit endpoint is now limited to USD and Paxos-issued stablecoins (USDP, PAXG, PYUSD, USDG) for new Sandbox accounts. Depositing fake crypto balances for other assets is no longer available by default. To fund a Sandbox account with test crypto, use the Fund Sandbox with Test Crypto guide, which covers the Paxos Testnet Faucet, public network faucets, and Paxos-deployed ERC-20 test token contracts on Ethereum Sepolia.

Following the April 2026 deprecation, the API is now in read-only mode until complete removal. Only Get and List remain available for historical lookups. To convert stablecoins, use the Orchestrations API, or see the migration guide.

Create Fiat Account now returns more specific error details when payment instructions fail validation. The 400 response detail field now identifies the exact field and the constraint it violated, making it easier to correct the request without trial and error. See Invalid Payment Instructions for the error format and field reference.

Added three sandbox-only endpoints so partners can self-service test KYC-refresh workflows without needing Paxos to force a refresh on their behalf:

• Sandbox Start KYC Refresh (POST /identity/identities/{identity_id}/kyc-refresh) — starts a KYC refresh workflow for an eligible identity.

• Sandbox Force Start KYC Refresh (POST /identity/kycrefresh/force-start) — force-starts a refresh, bypassing eligibility checks.

• Sandbox Reset KYC Refresh (POST /identity/kycrefresh/reset) — resets the KYC refresh state for an identity.

All three require the identity:write_identity scope and are available in sandbox only.

Updated the Complete Onboarding guide to clarify that Account Openers must provide a valid government-issued ID and Proof of Residential Address, consistent with compliance policy. Both documents were previously listed as required only for Beneficial Owners, Authorized Users, and Persons with Management Control.