Nvio CLABE Bitso Transfer®

To send MXN to another Nvio CLABE, complete the following HTTP request using the appropriate body parameters:

POST https://api-stage.bitso.com/v3/withdrawals

Body Parameters

Parameter Name	Fixed value	Example value	Required / Optional
`asset`	"mxn"		Required
`currency`	"mxn"		Required
`method`	"bt"		Required
`network`	"bt"		Required
`protocol`	"nvio-clabe"		Required
`amount`		"100"	Required
`clabe`		"710969000000326856"	Required
`origin_id`		"NvioclabeBT1234"	Optional
`notes`		"Payment concept"	Optional
`numeric_ref`		"1234567"	Optional

The following object exemplifies the body parameters included in the HTTP request:

{
  "asset": "mxn",
  "currency": "mxn",
  "method": "bt",
  "network": "bt",
  "protocol": "nvio-clabe",
  "amount": "100",
  "clabe": "710969000000326856",
  "origin_id": "NvioclabeBT1234",
  "notes": "Payment concept",
  "numeric_ref": "1234567"
}

A successful withdrawal of funds returns the response object shown below:

{
    "success": true,
    "payload": {
        "wid": "6fea2a2ae1573ff46ea9e9699081a7f7",
        "status": "pending",
        "created_at": "2026-06-24T13:59:05+00:00",
        "currency": "mxn",
        "method": "bt",
        "method_name": "Bitso Transfer",
        "amount": "100.00",
        "asset": "mxn",
        "network": "bt",
        "protocol": "nvio-clabe",
        "integration": "bt",
        "details": {
            "origin_id": "NvioclabeBT1234",
            "email": null,
            "phone": null,
            "refcode": null,
            "recipient_name": null,
            "recipient_ref": "snvk",
            "notes": "Payment concept",
            "emoji": ""
        }
    }
}

Webhook Notifications

Nvio CLABE Bitso's withdrawal and funding services provide webhooks that send real-time status data about withdrawal and funding events in a Bitso account.

To consume the webhook, subscribe to funding and withdrawal with Create webhook subscriptions. See Managing Subscriptions.

The webhook delivers the following JSON objects that represent the withdrawal and funding:

{
  "event": "withdrawal",
  "payload": {
    "wid": "6fea2a2ae1573ff46ea9e9699081a7f7",
    "status": "complete",
    "created_at": "2026-06-24T13:59:05+00:00",
    "currency": "mxn",
    "method": "bt",
    "method_name": "Bitso Transfer",
    "amount": "100.00",
    "asset": "mxn",
    "network": "bt",
    "protocol": "nvio-clabe",
    "integration": "bt",
    "details": {
      "origin_id": "NvioclabeBT1234",
      "client_withdrawal_id": "NvioclabeBT1234",
      "refcode": "snvk",
      "recipient_ref": "togb",
      "notes": "Payment concept",
      "concepto": "Payment concept",
      "fecha_operacion": "20260624",
      "beneficiary_name": "Bob",
      "beneficiary_clabe": "710969000000288208",
      "beneficiary_bank_code": "90710",
      "numeric_ref": "0001"
    }
  }
}

For a description of each field in the withdrawal details object, see Withdrawal details fields.

{
  "event": "funding",
  "payload": {
    "fid": "5c2b62095ef7d530c4d701fcd342c421",
    "status": "complete",
    "created_at": "2026-06-24T13:59:05+00:00",
    "currency": "mxn",
    "method": "bt",
    "method_name": "Bitso Transfer",
    "amount": "100.00",
    "asset": "mxn",
    "network": "bt",
    "protocol": "nvio-clabe",
    "integration": "bt",
    "details": {
      "sender_clabe": "710969000000448297",
      "sender_name": "Sender Name",
      "sender_bank": "90710",
      "sender_rfc_curp": "XAXX010101000",
      "receiver_clabe": "710969000000326856",
      "receive_clabe": "710969000000326856",
      "concepto": "Payment concept",
      "numeric_reference": "1234567",
      "operation_date": "2026-06-24"
    }
  }
}

For a description of each field in the deposit details object, see Funding details fields.

For a detailed description of the JSON object the webhook delivers, see funding and withdrawal.

Tracking Your Withdrawal

The payload returned by the create withdrawal call includes the variable wid, which stores the transaction's identifier. This ID can help you track your withdrawal.

To retrieve a specific transaction, send the following HTTP call, which returns detailed information on a user's funds withdrawal:

GET https://api-stage.bitso.com/v3/withdrawals/{wid}

If you do not specify a withdrawal identifier, then it lists all your withdrawals. Visit Listing Withdrawals to learn other ways to filter your search using query parameters.

The following response object exemplifies the details retrieval for a specific withdrawal:

{
    "success": true,
    "payload": [
        {
            "wid": "6fea2a2ae1573ff46ea9e9699081a7f7",
            "status": "complete",
            "created_at": "2026-06-24T13:59:05+00:00",
            "currency": "mxn",
            "method": "bt",
            "method_name": "Bitso Transfer",
            "amount": "100.00",
            "asset": "mxn",
            "network": "bt",
            "protocol": "nvio-clabe",
            "integration": "bt",
            "details": {
                "origin_id": "NvioclabeBT1234",
                "email": null,
                "phone": null,
                "refcode": "snvk",
                "recipient_ref": "togb",
                "notes": "Payment concept",
                "emoji": "",
                "fecha_operacion": "20260624",
                "concepto": "Payment concept",
                "beneficiary_name": "Bob",
                "beneficiary_clabe": "710969000000288208",
                "beneficiary_bank_code": "90710",
                "numeric_ref": "0001"
            },
            "legal_operation_entity": {
                "name": "Nvio Pagos Mexico",
                "country_code_iso_2": "MX",
                "image_id": "nvio"
            }
        }
    ]
}

For a description of each field in the withdrawal details object, see Withdrawal details fields.

Withdrawal `details` fields

The details object of a withdrawal contains the following fields. For deposit-side equivalents, see Funding details fields.

Field	Type	Presence	Description
`origin_id`	String	Optional	Client-provided idempotency key from the request `origin_id` field.
`client_withdrawal_id`	String	New withdrawals	Client-provided withdrawal identifier; from the request `origin_id` field.
`email`	String	Always	Recipient email. `null` when not provided.
`phone`	String	Always	Recipient phone. `null` when not provided.
`refcode`	String	Always	Bitso-generated reference code for the withdrawal.
`recipient_ref`	String	Always	Short recipient reference identifier.
`notes`	String	Optional	Payment concept from the request `notes` field. Same value as `concepto` on new withdrawals.
`emoji`	String	Always	Emoji associated with the withdrawal. Empty string when not set.
`concepto`	String	New withdrawals	Payment concept; same value as `notes`. From the request `notes` field. Required on new withdrawals. Deposit equivalent: `concepto`.
`fecha_operacion`	String	New withdrawals	Operation date in Mexico City local time, in `YYYYMMDD` format. Deposit equivalent: `operation_date`.
`beneficiary_name`	String	New withdrawals	Beneficiary name for the withdrawal destination. Deposit equivalent: `sender_name` (outbound side).
`beneficiary_clabe`	String	New withdrawals	Beneficiary CLABE; from the request `clabe` field. Deposit equivalent: `receive_clabe`.
`beneficiary_bank_code`	String	New withdrawals	Beneficiary bank code; always NVIO (`90710`). Deposit equivalent: `sender_bank`.
`numeric_ref`	String	New withdrawals	Payment reference; from the request `numeric_ref` field. Omitted when not provided. Deposit equivalent: `numeric_reference`.

Fields marked New withdrawals are included on withdrawals created since 2026-06-24.

Tracking Your Funding

To retrieve a specific transaction, send the following HTTP call, which returns detailed information on a user's funds deposit:

GET https://api-stage.bitso.com/v3/fundings/{fid}

If you do not specify a deposit identifier, then it lists all your fundings. Visit Listing Fundings to learn other ways to filter your search using query parameters.

The following response object exemplifies the details retrieval for a specific funding:

{
    "success": true,
    "payload": [
       {
            "fid": "5c2b62095ef7d530c4d701fcd342c421",
            "status": "complete",
            "created_at": "2026-06-24T13:59:05+00:00",
            "currency": "mxn",
            "method": "bt",
            "method_name": "Bitso Transfer",
            "amount": "100.00",
            "asset": "mxn",
            "network": "bt",
            "protocol": "nvio-clabe",
            "integration": "bt",
            "details": {
                "sender_clabe": "710969000000448297",
                "sender_name": "Sender Name",
                "sender_bank": "90710",
                "sender_rfc_curp": "XAXX010101000",
                "receiver_clabe": "710969000000326856",
                "receive_clabe": "710969000000326856",
                "concepto": "Payment concept",
                "numeric_reference": "1234567",
                "operation_date": "2026-06-24"
            },
            "legal_operation_entity": {
                "name": "Nvio Pagos Mexico",
                "country_code_iso_2": "MX",
                "image_id": "nvio"
            }
        }
    ]
}

For a description of each field in the deposit details object, see Funding details fields.

Funding `details` fields

The details object of a deposit contains the following fields. For withdrawal-side equivalents, see Withdrawal details fields.

Field	Type	Presence	Description
`sender_clabe`	String	Always	Sender's CLABE; the account that originated the deposit.
`sender_name`	String	Always	Sender's name. Withdrawal equivalent: `beneficiary_name` (outbound side).
`sender_bank`	String	New deposits	Sender's bank code; always NVIO (`90710`). Withdrawal equivalent: `beneficiary_bank_code`.
`sender_rfc_curp`	String	New deposits	Sender's RFC or CURP; `"ND"` when neither is available.
`receiver_clabe`	String	Deprecated	Use `receive_clabe` instead.
`receive_clabe`	String	Always	Destination CLABE that received the deposit; from the request `clabe` field. Withdrawal equivalent: `beneficiary_clabe`.
`concepto`	String	Optional	Payment concept; from the request `notes` field. Omitted when `notes` is empty. Withdrawal equivalent: `notes` and `concepto`.
`numeric_reference`	String	Always	Payment reference; from the request `numeric_ref` field. Empty string when `numeric_ref` is empty. Withdrawal equivalent: `numeric_ref`.
`operation_date`	String	New deposits	Operation date in Mexico City local time, in `YYYY-MM-DD` format. Withdrawal equivalent: `fecha_operacion` (`YYYYMMDD`).

Fields marked New deposits are included on deposits created since 2026-06-24.

Webhook Notifications

Tracking Your Withdrawal

Withdrawal details fields

Tracking Your Funding

Funding details fields

Withdrawal `details` fields

Funding `details` fields