Integrate mutual funds (FCIs)

Let your users invest in mutual funds (Fondos Comunes de Inversión, FCIs) by amount: they subscribe with ARS or USD and redeem back to it, at the share value the fund sets, without trading at a market price.

At a glance

  • Users: Each user is onboarded in Broker and must be ACTIVE.
  • Funds: Subscriptions use the user's ARS or USD balance in Broker, funded by transfers from a bank account in their own name. Redemptions credit the currency back to that balance. Balances settle through the company-level debt/credit model described in Operating model.
  • Tracking: Subscriptions and redemptions are reported as orders through order-status-update, or poll GET /broker/v1/api/order/{orderAnyId}.

How it works

  1. Onboard the user in Broker and fund their balance (same steps as investments).
  2. Subscribe an amount to a fund. You get an order in PENDING_EXECUTION with the fund's executionTime.
  3. At the fund's cut-off the order executes and order-status-update reports COMPLETED with the shares credited.
  4. To get the money back, redeem an amount. It follows the same lifecycle and credits the currency.
  5. Read the user's position in each fund, and your company's daily net for settlement.

Before you start

  • Broker endpoints live under /broker/v1/api/....
  • Configure webhooks with PUT /broker/v1/api/company. Events without their own URL in webhooks go to generalWebhook. Your endpoint must accept POST over HTTPS, answer 2xx quickly and process deliveries idempotently, since failed deliveries are retried. See Broker webhooks for the signature and the retry schedule.
{
  "notificationInfo": {
    "type": "WEBHOOK",
    "secret": "your-webhook-secret",
    "generalWebhook": "https://your-domain.com/webhooks/manteca",
    "webhooks": {
      "order-status-update": "https://your-domain.com/webhooks/manteca/orders"
    }
  }
}

Webhooks are sent from four fixed IP addresses: allowlist all of them (see Broker webhooks).

1

Pick the fund

Funds are listed among the instruments with type POOL: call GET /broker/v1/api/price/instruments with ?assetType=POOL. The examples use FSTPESA, an ARS fund.

2

Subscribe

Send the amount of currency to invest in againstAmount. against is ARS or USD (ARS if omitted). Set externalId to your own reference so a retry cannot create a second order.

Request POST /broker/v1/api/investment/invest

{
  "userAnyId": "10416",
  "asset": "FSTPESA",
  "against": "ARS",
  "againstAmount": "1000",
  "externalId": "fci-sub-0001"
}

Response (trimmed)

{
  "id": "6841ed090d9408b313cf381e",
  "externalId": "fci-sub-0001",
  "status": "PENDING_EXECUTION",
  "side": "BUY",
  "asset": "FSTPESA",
  "against": "ARS",
  "amount": 330.644094,
  "filledAmount": 0,
  "price": 3.0244,
  "finalClaimInfo": { "asset": "ARS", "total": 1000 },
  "executionTime": "2025-06-06T16:00:00.000-03:00"
}

A subscription is an order with side: "BUY". amount is the estimated number of shares at the current share value (price); the final number is set when the order executes. executionTime is when it executes: requests can be sent at any time of day, and each fund executes them at its daily cut-off.

3

Redeem

Redeem by amount of currency in the same way. The user needs a position in the fund that covers it.

Request POST /broker/v1/api/investment/rescue

{
  "userAnyId": "10416",
  "asset": "FSTPESA",
  "against": "ARS",
  "againstAmount": "1000",
  "externalId": "fci-red-0001"
}

Response (trimmed)

{
  "id": "6841f8c52d8cf7de88003e3a",
  "externalId": "fci-red-0001",
  "status": "PENDING_EXECUTION",
  "side": "SELL",
  "asset": "FSTPESA",
  "against": "ARS",
  "amount": 330.644094,
  "finalClaimInfo": { "asset": "FSTPESA", "total": 330.644094 },
  "executionTime": "2025-06-06T16:00:00.000-03:00"
}

A redemption is an order with side: "SELL": the shares leave the position and, once executed, the currency is credited to the user's balance.

4

Track the operation

Both operations arrive through order-status-update, with the fund as asset:

{
  "eventName": "order-status-update",
  "data": {
    "status": "COMPLETED",
    "order": {
      "id": "6841ed090d9408b313cf381e",
      "externalId": "fci-sub-0001",
      "status": "COMPLETED",
      "side": "BUY",
      "asset": "FSTPESA",
      "against": "ARS",
      "amount": 330.644094,
      "filledAmount": 330.644094,
      "finalClaimInfo": { "asset": "ARS", "total": 1000 },
      "finalCreditInfo": { "asset": "FSTPESA", "total": 330.644094 },
      "executionTime": "2025-06-06T16:00:00.000-03:00"
    }
  }
}
StatusWhat to do
PENDING_EXECUTIONAccepted and scheduled for executionTime. Show it as in progress.
COMPLETEDExecuted. finalCreditInfo is what the user received: shares on a subscription, currency on a redemption.
CANCELLEDCancelled before executing.

Deduplicate webhooks by order id and status. Poll GET /broker/v1/api/order/{orderAnyId} when a webhook is late, or list orders with GET /broker/v1/api/order filtered by externalId, status, asset or a from/to range.

Balances and settlement

The user's position, valued in currency and revalued daily: GET /broker/v1/api/investment/balance/USERANYID (?asset=FSTPESA&against=ARS).

{ "FSTPESA": "1000.00" }

The full balance, with the shares held and the cash in each currency: GET /broker/v1/api/balance/USERANYID.

{
  "userId": "6596e960e140a030749b4e23",
  "balance": { "FSTPESA": "330.644094", "ARS": "0" }
}

Your company's subscriptions, redemptions and net for the day: GET /broker/v1/api/stats/investment/netBalance (?asset=FSTPESA). Settlement with your company runs daily, on the net amount, at the time agreed with Manteca.

{
  "netBalance": { "FSTPESA": "-14127309.073272", "ARS": "-20553511.17" },
  "invest": { "FSTPESA": "33276646.632837", "ARS": "48413461.10" },
  "rescue": { "FSTPESA": "47403955.706109", "ARS": "68966972.27" }
}

Errors

Handle errors by internalStatus, not by HTTP status.

Full list: Errors and controls.

Go deeper


Did this page help you?