> ## Documentation Index > Fetch the complete documentation index at: https://docs.velafi.com/llms.txt > Use this file to discover all available pages before exploring further. # Changelog > A complete history of VelaFi API releases — new endpoints, updated workflows, webhook additions, and documentation improvements across all versions. This page tracks every significant change to the VelaFi API platform, including new endpoints, workflow updates, webhook additions, and documentation improvements. Review this changelog whenever you upgrade your integration or want to take advantage of new features. Changes are listed in reverse chronological order. *** ## 2026-09-18 — Pix - Woovi Liveness * Renamed: [`POST /v2/merchant/woovi/liveness`](https://docs.velafi.com/api-reference/merchant/get-woovi-liveness-url): get the liveness URL for a Pix - Woovi activation (provided by Avenia). *** ## 2026-09-14 — Argentine Alias and CVU Lookups * New [`GET /v2/merchant/check/alias`](https://docs.velafi.com/api-reference/beneficiary/check-alias): resolve an Argentine alias to its CBU/CVU, status and account holders. * New [`GET /v2/merchant/check/cvu`](https://docs.velafi.com/api-reference/beneficiary/check-cvu): look up the holder CUIT and name for a CVU or CBU. *** ## 2026-09-07 — Fee Breakdown on Order Detail * [`GET /v2/order/detail`](https://docs.velafi.com/api-reference/order/retrieve-a-specific-order) now includes `orderFeeDetail` for fiat-to-crypto and crypto-to-fiat orders, with `grossAmount`, `netAmount` and `feeLines`. * For fiat-to-fiat orders, it includes `onRampOrderFeeDetail` and `offRampOrderFeeDetail`. *** ## 2026-05-28 — Sandbox Crypto Deposit Simulator * New sandbox-only endpoint `/v2/platform/test/crypto/deposit` adds test crypto funds to a merchant. See [Sandbox Testing Tools](https://docs.velafi.com/docs/sandbox.md#sandbox-testing-tools). *** ## 2026-04-23 — Order Failure Details * [`GET /v2/order/detail`](https://docs.velafi.com/api-reference/order/retrieve-a-specific-order) now returns `failCode` and `failReason` for fiat-to-crypto and crypto-to-fiat orders. *** ## 2026-04-22 — Remarks on Crypto Withdrawals * [`POST /v2/assets/withdraw`](https://docs.velafi.com/api-reference/crypto-wallet/create-crypto-withdrawal) accepts an optional `remark`. * `GET /v2/assets/withdrawalOrders` returns it. *** ## 2026-04-17 — Payment Template Metadata * New [`GET /v2/payments/templates/metamessage`](https://docs.velafi.com/api-reference/beneficiary/get-payment-templates-metamessage): field-level metadata for a payment method template. *** ## 2026-02-28 — Order Expiry Timestamp * [`GET /v2/order/detail`](https://docs.velafi.com/api-reference/order/retrieve-a-specific-order) returns `orderExpireTimestamp` while an order is awaiting its crypto deposit (`orderStatus` `32`). *** ## 2026-02-05 — Sandbox Fiat Deposit Simulator * New sandbox-only endpoint `/v2/platform/test/deposit` simulates a bank deposit to a merchant's activated fiat account. See [Sandbox Testing Tools](https://docs.velafi.com/docs/sandbox.md#sandbox-testing-tools). *** ## 2026-01-17 — Quote IDs * [Crypto quotes](https://docs.velafi.com/api-reference/quote/get-user-quote-for-crypto-fiat.md) (`GET /v2/user/crypto-quote`) and [fiat quotes](https://docs.velafi.com/api-reference/quote/get-user-quote-for-fiat-fiat.md) (`GET /v2/user/fiat-quote`) accept an optional `createQuoteId` parameter and return `quoteId`. * `POST /v2/order/fiat_to_crypto`, `POST /v2/order/crypto_to_fiat` and `POST /v2/order/fiat_to_fiat` accept `quoteId`. *** ## 2026-01-08 — Virtual Accounts * New [`POST /v2/merchant/virtual/accounts`](https://docs.velafi.com/api-reference/merchant/create-multiple-virtual-account): create a virtual account under an activated fiat account. * New [`GET /v2/merchant/virtual/addfunds`](https://docs.velafi.com/api-reference/merchant/get-multiple-virtual-account): list a merchant's virtual accounts. *** ## 2025-12-12 — Bank Order ID on Order Detail * [`GET /v2/order/detail`](https://docs.velafi.com/api-reference/order/retrieve-a-specific-order) now returns `bankOrderId` for fiat-to-crypto and crypto-to-fiat orders. *** ## 2025-12-01 — Fiat Flow Records * New [`GET /v2/merchant/fiat/flows`](https://docs.velafi.com/api-reference/merchant/get-a-list-merchant-fiat-flow): ledger of fiat balance movements for a merchant. *** ## 2025-11-18 — Guides and API Reference Updates This release delivers broad documentation improvements covering the merchant onboarding workflow, a brand-new Limits guide, and updated API reference pages for merchant limit management. ### Guides > [accordion] 1. Step-by-Step Guide > > Updated the onboarding workflow description to improve clarity and reflect the latest merchant setup process. > [accordion] 2. Creating Your Merchant > > Updated the KYC/KYB merchant creation process, including clearer guidance on verification steps and requirements. > [accordion] 3. Activate Merchant Account > > Updated the merchant account activation flow with a clearer explanation of fiat account activation requirements. > [accordion] 4. Limits — New Guide > > Added a new guide introducing merchant limit levels, approval criteria, and instructions on requesting limit upgrades. ### API Reference > [accordion] 5. Account — Get Account Details > > Updated the API response structure to include merchant limit information and related fields. > [accordion] 6. Merchant — Create Merchant > > Updated the KYC/KYB workflow for merchant creation. Added improved API request and response examples. > [accordion] 7. Merchant — Get a List of Merchants > > Updated API fields related to merchant limits, including limit status and approval/rejection reasons. > [accordion] 8. Merchant — Activate Merchant Account (Individual) > > Updated the activation flow for individual merchants' fiat accounts. > [accordion] 9. Merchant — Activate Merchant Account (Business) > > Updated the activation flow for business merchants' fiat accounts with refined workflow requirements. > [accordion] 10. Merchant — Get a List of Merchant Accounts > > Updated API response fields related to merchant account limits and limit status tracking. > [accordion] 11. Merchant — Upgrade Merchant Limit > > Updated the merchant limit upgrade process with revised approval logic and enhanced parameter definitions. *** ## 2025-06-13 — KYC/KYB Merchant Creation Workflow This release transitions the merchant creation workflow to the KYC/KYB model and introduces the Activate Merchant Account endpoint. > [!NOTE] > > Endpoints released before **2025-06-13** will remain functional temporarily but are scheduled for deprecation. Migrate to the new KYC/KYB flow as soon as possible to avoid disruption. > [card] Workflow Update: Merchant Creation > > The merchant creation process has been updated to adopt the KYC/KYB model. Refer to the **Creating Your Merchant** guide for the updated steps and verification requirements. > [card] API Update: Create Merchant Endpoint > > The `create merchants` API endpoint has been updated to align with the new KYC/KYB process. Update your integration to use the revised request schema. > [card] New Guide: Activate a Merchant Account > > A new guide step covers activating fiat accounts once a merchant entity is successfully created, ensuring the merchant is fully operational for fiat transactions. > [card] New Endpoint: Activate Merchant Account > > A new API endpoint enables merchants to activate their fiat account after initial merchant setup is complete. This is required before the merchant can process fiat transactions. *** ## 2025-05-08 — Funding Records Webhook Fields and Transfer Endpoint This release enhances the Funding Records Message Push webhook with richer payer information and adds an internal fund transfer endpoint. ### Funding Records Message Push Webhook The webhook payload now includes two new fields to provide more detailed funding record information for better tracking and management of fund sources. **payerName** `string` Name of the entity sending funds. **payerAccount** `string` Bank account of the entity sending funds. ### New Endpoint: Internal Fund Transfer Added the `POST /v2/merchant/transfer` endpoint for initiating internal fund transfers between accounts. ```http theme={null} POST /v2/merchant/transfer ``` *** ## 2025-04-14 — Pending Fund System This release introduces the Pending Fund system — a new payment method, three new API endpoints, and a dedicated webhook for real-time event notifications. ### New Payment Method: VelaFi Pending Fund (ID: 70) When creating an order via API, you can now select **VelaFi Pending Fund** (payment ID `70`) as the payment or receiving method. Using preloaded funds enables faster transaction processing by bypassing external transfer confirmation delays. ### New API Endpoints **1. Retrieve Pending Fund** Query your **Pending Fund account** balance and status via API. You can also preload funds into the account to avoid delays from external transfer confirmation during live transactions. **Location:** API Reference → Merchant **2. Claim Pending Fund** Withdraw available balances from the **Pending Fund account** to a specified payment method at any time. This provides flexible, on-demand fund management. **Location:** API Reference → Merchant **3. Retrieve Funding Records** Fetch detailed records of all **Pending Fund-related activities** — including deposits, withdrawals, usage, and refunds — for full traceability and financial transparency. **Location:** API Reference → Merchant ### New Webhook: Funding Records Message Push > [card] Funding Records Message Push > > Receive real-time webhook notifications for Pending Fund events. Each notification delivers structured transaction data to your endpoint, improving operational automation and fund monitoring. > > **Location:** Webhooks This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.