History of Changes
2026-11-03
Added Test Account Validations. In the testing environment, a set of test CLABEs returns each account validation result on demand: COMPLETED, every error.code in Failed validations, and a validation that stays in PROCESSING.
2026-10-26
US external account create and update now limit the street lines. The update schema wraps the existing address fields under address; the endpoint already required that. See Create an external account and Update an external account.
2026-10-23
Updated Pay-in Keys and the pay-in key conflict messages in the OpenAPI contract.
2026-10-21
A returned Colombian ACH payout appears as an ACH pay-in. The pay-in reference describes that refund the same way. Inbound COP stays Bre-B or PSE. See Product Overview and Payment Flow.
2026-10-19
Copied the generated Unified Payments OpenAPI as-is after PAG #660. Third-party co_pse.third_party.phone is required. See [email protected]. A PSE pay-in intent create rejected for invalid parameters returns 400 invalid_field instead of 503 ramp_not_available. No manual OAS edits.
2026-10-02
Retrying Events and the retry endpoints in the Webhooks API state that webhook events are stored for 60 days after creation and then deleted. The retry window is unchanged: only events from the last 60 days can be previewed or retried. Removed the obsolete note that retry covers events created on or after 20 March 2025.
2026-09-22
Copied the generated Unified Payments OpenAPI as-is after PAG #614 / #621. Third-party CO_ACH document_id is validated by document_type. Use NIT only for a legal person: prefer 9 digits without the verifier; 10 digits are accepted and the last digit is omitted. Put the same company name in given_name and family_name. Failures return 400 invalid_field. No manual OAS edits.
Colombia Payment Flow documents the per-type rules.
2026-09-11
Copied the generated Unified Payments OpenAPI as-is after PAG #600. When co_breb.beneficiary_key is present, id is required. key and external_ref remain optional. When omitted, treat the pay-in as a first-party deposit recorded before this snapshot existed. No manual OAS edits.
Removed the SPEI incoming remittance event types (spei_incoming_remittance, spei_incoming_remittance_beneficiary, and spei_incoming_remittance_sender) from the deprecated Getting Started — Webhooks article.
Removed the Sandbox IP addresses from the webhook allowlist. Sandbox is no longer an environment; Stage and Production remain.
Retargeted product webhook guides to the Webhooks section and the Webhooks API reference for subscription, signatures, and allowlisting.
2026-09-10
Copied the generated Unified Payments OpenAPI as-is after pay-in GET and webhook payloads published co_breb.beneficiary_key (id, key, external_ref). Match id to the pay-in key. When omitted, treat the pay-in as a first-party deposit recorded before this snapshot existed. No manual OAS edits.
2026-09-09
Colombia Pay-in Keys create accepts co_breb.key_type: ALIAS only. PHONE, EMAIL, and USER_IDENTIFICATION return 400 invalid_field. The published schema is CoBrebPayinKeyType. Payout CoBrebKeyType is unchanged.
CO_BREB pay-ins include optional co_breb.beneficiary_key (id, key, external_ref) when the destination key was snapshotted. Match id to the pay-in key. When omitted, treat the pay-in as a first-party deposit recorded before this snapshot existed.
Copied the generated Unified Payments OpenAPI as-is (no manual OAS edits).
2026-09-08
Added Unified Payments Colombia Pay-in Keys documentation:
- Identity is
co_breb.beneficiary(NATURAL_PERSON/LEGAL_PERSON). - Create returns
ACTIVEsynchronously. Statuses areACTIVEandINACTIVE. Delete returns204. - List requires
type. Optional filters:external_ref,document_id,key. - Idempotency conflict is
400 idempotency_key_already_used. Duplicate document is409 identifier_already_linked. - Natural- and legal-person examples.
Copied the generated Unified Payments OpenAPI as-is (no manual OAS edits).
2026-09-03
Corrected the origin_id character set documented for ARS, MXN, USD wire, and PIX withdrawals. These methods accept the dash character, -. Because the maximum length is 40 characters, you can use a UUID as the idempotency key. The dash remains unsupported for the other withdrawal methods, such as SEPA transfers.
Corrected the names of the identifier query parameters of the method GET /v3/withdrawals. The method accepts wids and origin_ids. Previously, the article listed them in their singular form, wid and origin_id, which the method does not accept as query parameters.
2026-09-02
Added the Webhooks section and the Webhooks API reference. The subscription API documented in Getting Started — Webhooks is deprecated.
2026-09-01
Added the Mexican Account Validation section and the Account Validation API reference.
2026-07-22
In the article Create Mock Deposits in MXN, removed the fields pending_deposit and pending_withdrawal from the sample balance response.
2025-05-05
Deprecated the query parameter clabe_type in the method GET /spei/v1/deposits .
2025-04-22
Added the stage and sandbox IP addresses to the list provided in the Webhooks articles.
2025-04-22
Enhanced the definition of the amount property to indicate whole numbers only in the articles Withdrawing COP.
2025-04-22
Enhanced the description of the disconnected failed withdrawal error by adding the link to Banxico's Connection Monitor, article Withdrawing MXN
2025-04-21
Enhanced the description of the properties returned in refund deposits, article List Deposits Made (Multiple CLABEs).
2025-04-09
For cryptocurrencies, the Webhook funding event and the GET /fundings method added the property sending_address to the details object.
2025-04-09
Added the article Backward-Compatible API Updates , which specifies the API changes BItso considers to be backward compatible.
2025-03-20
Webhooks articles added the section, Best Practices for Using Webhooks.
2025-03-19
The endpoint GET /spei/v1/deposits added the following response body parameters:
payment_id: Deposits linked to a one-time payment now include this property in thedetailsobject.multiclabe_validation_error: Failed deposits linked to a created CLABE or to a one-time payment now report the reason for failing in thisdetailsobject property.
2025-03-14
Introduced Nonce v2 for enhanced request reliability and security, reducing rejected valid requests for high-traffic users.
2025-03-05
The method GET /fundigs/ deprecated the query parameter txds and released a new one that provides a similar functionality: fids.
2025-02-29
Added the Create a Static QR Code endpoint to the Pix Payments API.
2025-02-12
Added the following error to the Reasons for Failed Withdrawals table in Withdrawing MXN:
El participante no está conectado al sistema bancario (The receiving party is not connected to the banking system)
2025-01-21
The methods GET /spei/v1/deposits and GET spei/v1/withdrawals added the query parameter timezone, which enables reporting transaction creation time according to the given timezone.
2025-01-09
The Multi-CLABEs API endpoint for setting limits added the ability to configure maximum limits. This endpoint's article was renamed and expanded to include the new ability, Set Deposit Limits.
2025-01-02
The endpoint https://api-stage.bitso.com/v3/fundings/{fid-fid-fid} was deprecated and removed from the documentation.
2024-12-10
The account creation process for wiring digital dollars modified the states a created account can have. The PENDING state was eliminated. An account can be in one of the three following states: STARTED, ACTIVE, or REJECTED.
2024-11-13
Added the endpoint Receive a One-Time Payment to the Multi-CLABEs API.
2024-11-5
Added the procedure to create mock refund deposits in MXN.
2024-10-25
Added the endpoint Retrieve A QR Code Pay-In to the Pix Payments section.
2024-10-23
Added the parameter origin_id to the request body of BRL withdrawals.
2024-10-21
Added the endpoint Filter Your MXN Withdrawal Search.
2024-10-17
Added the endpoint Set a Deposit Minimum Limit to the Multi-CLABEs API.
2024-10-15
Added the Guide Managing Business Customers via API for USDC Money Transmitters.
2024-10-09
Deposits in BRL made via a dynamic QR code are now reported to the webhook. Added the payload delivered to the article Webhooks.
2024-10-09
Previously created accounts are no longer supported in BRL withdrawals. Updated the article Adding a Receiving Account to indicate it.
2024-10-09
The response body in the withdrawal preview for refunds (reversed withdrawals) added the object property collectable_question , which is used in the Bitso application logic.
2024-10-07
Added the article Understand Bitso's Auth Mechanism.
2024-09-27
The endpoint GET /spei/v1/deposits added the query parameters only_refunds and tracking_key, article List Deposits Made.
2024-09-25
USDC Withdrawals over Polygon, USDC Withdrawals over Stellar, and USDC Withdrawals over Solana had the following updates:
- The POST
/withdrawal/and GET/withdrawal/{wid}methods changed the names of the following parameters in their response body:transactionHash→tx_hashaddress→withdrawal_addressaddressTag→destination_tag
- The GET
/withdrawal/{wid}method added the objectlegal_operation_entityto its response body.
2024-09-18
USDC Withdrawals over Stellar had the following update:
- The POST
/withdrawal/method changed the name of the following parameter in its request body:addressTag→destination_tag
2024-08-28
The document Listing Fundings, which explains how to use theGET /fundings/method, specified that you could only use three identifiers in the path parameters list. Such a constraint is currently non-existent in the code; you can use several.
2024-08-28
The document Listing Withdrawals, which explains how to use theGET /withdrawals/method, specified that you could only use three identifiers in the query parameters. Such a constraint is currently non-existent in the code; you can use several.
2024-08-28
The query parameters list of the GET /withdrawals/ method added currency.
2024-08-14
We republished the documentation for USDC Withdrawals over Polygon since Bitso supports the transaction again. In the new implementation, the request body parameter chain changed its value from MATIC to POLY.
2024-08-05
The GET /funding_details method, which enabled users to retrieve their account's funding data for the specified currency, was deprecated and its documentation was removed. The article Retrieve Your Destination Address was updated to eliminate the endpoint as a search option.
2024-01-24
The USD wiring service endpoint POST /v3/payments/usd/bridge/external-accounts for bank account registration changed the address parameter from optional to required.
2023-12-01
The notifications service callback URL can now accept both upper and lowercase letters. The article Webhooks eliminated the callout that warned about avoiding uppercase letters in the URL.
Updated 1 day ago