Send money to a CLABE

Money Out sends funds from a Monato source instrument to a destination instrument. If the destination belongs to a Monato account, Fincore routes it internally through the same operation. See Internal transfers.

Flow

1. Register the recipient

Get the destination bank id from Retrieve SPEI participants, then register the CLABE with Register instrument. Send customer_id if the instrument should belong to a Business Unit. Retrieve SPEI participants returns 401 if the bearer token is missing, expired, invalid, or not valid for the environment, and 500 for an unexpected server error.

curl -X POST https://apicore.stg.finch.lat/v1/clients/$CLIENT_ID/instruments \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "source_bank_id": "9d84b03a-28d1-4898-a69c-38824239e2b1",
    "client_id": "c2d1d1e3-3340-4170-980e-e9269bbbc551",
    "type": "RECEIVER",
    "rfc": "XAXX010101000",
    "alias": "Supplier ABC",
    "virtual_clabe": {
      "destination_bank_id": "3054ff18-32a0-478d-b9fe-b5261f9a6e1f",
      "account_number": "12345678901",
      "clabe_number": "123456789012345678",
      "holder_name": "Jane Doe"
    }
  }'

The response id is your destination_instrument_id. You can list instruments with List instruments (filter by customer_id, instrument_number, bank_id or instrument_name; paginate with page and per_page) and read one with Retrieve instrument.

Before sending production funds to a new account, you can confirm ownership with Penny Validation.

2. Create the transaction

Endpoint: POST /v1/transactions/money_out. Use the same endpoint for SPEI transfers and internal Monato transfers.

curl -X POST https://apicore.stg.finch.lat/v1/transactions/money_out \
  -H "Authorization: Bearer $TOKEN" \
  -H "Idempotency-Key: $IDEMPOTENCY_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "c2d1d1e3-3340-4170-980e-e9269bbbc551",
    "source_instrument_id": "709448c3-7cbf-454d-a87e-feb23801269a",
    "destination_instrument_id": "d3fdb481-2058-46c8-807d-4eaf866ae1ec",
    "transaction_request": {
      "external_reference": "1234567",
      "description": "Supplier payment",
      "amount": "1.95",
      "currency": "MXN"
    }
  }'

{
  "id": "16811ee8-1ef9-4dd4-8d84-9c2df89cf302",
  "bankId": "9d84b03a-28d1-4898-a69c-38824239e2b1",
  "clientId": "c2d1d1e3-3340-4170-980e-e9269bbbc551",
  "externalReference": "1234567",
  "trackingId": "20250306FINCHVLIKQ5SKUM",
  "description": "Supplier payment",
  "amount": "1.95",
  "currency": "MXN",
  "category": "DEBIT_TRANS",
  "subCategory": "SPEI_DEBIT",
  "transactionStatus": "INITIALIZED",
  "audit": {
    "createdAt": "2025-03-06 11:57:55.408000-06:00",
    "updatedAt": "2025-03-06 11:57:55.408000-06:00",
    "deletedAt": "None",
    "blockedAt": "None"
  }
}

subCategory shows how the transfer was routed: SPEI_DEBIT for an external transfer, INT_DEBIT for an internal transfer to a Monato account.

metadata is optional in standard Money Out responses. When Money Out is used for a 0.01 MXN Penny Validation, the response can include metadata.dataCep. See Validate a bank account.

Retry safely with Idempotency-Key

Always send an Idempotency-Key in production. It is optional, must be a UUID v5, and is kept for 24 hours. Reuse the same key with the exact same body for safe retries. See Idempotency for key generation.

Handle the status

The synchronous response confirms that Fincore accepted the request. It is not the final state. The final status arrives through the status update webhook and reports.

Webhooks are the primary signal. Use the read operation to reconcile a specific transaction, not as a polling loop.

curl https://apicore.stg.finch.lat/v1/clients/$CLIENT_ID/transactions/$TRANSACTION_ID \
  -H "Authorization: Bearer $TOKEN"

High-value review and trusted instruments

Transactions above $500,000.00 MXN are held for a manual operator review before they are sent to SPEI. If you pay the same trusted recipients repeatedly, add their instruments to a whitelist so those transactions skip the review. The threshold and the bypass apply to outbound SPEI payments. Whitelisting changes only the review step; every other Money Out rule still applies.

Add an instrument with Add an instrument to the trusted whitelist. There is no request body.

curl -X POST https://apicore.stg.finch.lat/v1/clients/$CLIENT_ID/instruments/$INSTRUMENT_ID/whitelist \
  -H "Authorization: Bearer $TOKEN"

{
  "id": "8f14e45f-ceea-467a-9f0a-1b2c3d4e5f60",
  "instrumentId": "d3fdb481-2058-46c8-807d-4eaf866ae1ec",
  "clientId": "c2d1d1e3-3340-4170-980e-e9269bbbc551",
  "instrumentWhitelistStatus": "ACTIVE",
  "audit": {
    "createdAt": "2026-09-21T13:03:36.194761-06:00",
    "updatedAt": "2026-09-21T13:03:36.194761-06:00"
  }
}

All of these are checked when you add an instrument. A rule failure returns 400 with FAILED_PRECONDITION and error code 20-E4120.

Debit-card destinations

Use the same Money Out flow for debit-card destinations when the feature is enabled for your integration. See Send money to a debit card and Register instrument.

Errors

{
  "code": 9,
  "message": "API Error",
  "details": [
    {
      "reason": "FAILED_PRECONDITION",
      "domain": "CORE",
      "metadata": {
        "error_detail": "The account does not have sufficient funds.",
        "http_code": "400",
        "error_code": "10-E4120"
      }
    }
  ]
}

See the Error catalog for the error shape and other messages.

Refunds

Refunds apply to a payment you received, not to a Money Out you sent. See Refund a received payment.