Operating Model

Operating Model

Broker as a Service has two characteristics that shape every integration: compliance is enforced at the person level, and balances are settled through a debt/credit model that consolidates at end of day.


Persons, not users

The compliance unit is the person, identified by their tax ID (legalId / CUIT), not the user record. Operational limits are assigned to the person and are shared across companies: if the same person operates through more than one platform, their limits are counted globally.

A user record belongs to one company and points to a person. When personal data cannot be retrieved automatically from a regulator at onboarding, the person record may remain incomplete: query and complete it explicitly.

ConceptIdentified byScope
PersonlegalId (CUIT)Global, shared across companies
Userid / numberId / externalIdSingle company

USD deposits are converted to ARS at the MEP rate to be counted against the person's limits.


Deposit limits and source of funds

Every person has a yearly deposit ceiling in ARS. GET /broker/v1/api/compliance/person/{legalId}/limits returns the pieces:

FieldMeaning
govLimitBaseline yearly deposit limit Manteca applies to every person.
verifiedLimitExtra headroom granted on top of govLimit (e.g. after a source-of-funds document is validated). 0 if none.
totalYearlyDepositedNet ARS deposited so far this year (USD at MEP rate; withdrawals credited back).

The applicable ceiling is govLimit + verifiedLimit: the two add up, they are not mutually exclusive. A person is within limits while:

totalYearlyDeposited ≤ govLimit + verifiedLimit

When totalYearlyDeposited exceeds govLimit + verifiedLimit, Manteca flags the person internally and further deposits/operations for that person are blocked with PERSON_DEPOSIT_LIMIT (403). The way to lift the ceiling is to raise verifiedLimit, which Manteca does after reviewing and validating a source-of-funds document for the person.

There is no dedicated boolean/endpoint that returns "source of funds required": you derive it yourself from the fields above (remaining headroom = govLimit + verifiedLimit − totalYearlyDeposited).

What counts as a source-of-funds document

The document has to show where the person's money comes from, carry their name, and state an amount and the period it covers. Any of these works:

  • The person's last three payslips.
  • Their most recent income tax return.
  • A statement of income issued and signed by a certified accountant.
  • Evidence of a specific inflow: the sale of a property or of securities, or a loan received.

These are not accepted on their own, because they identify the person or their tax status without evidencing income:

  • An identity document.
  • A bank statement.
  • A certificate of tax registration.

Send one file per upload. If the evidence spans several documents (three payslips, for instance), merge them into a single file first: a partial upload is reviewed as what it is and rejected. Local equivalents of these documents are accepted; ask your integration contact if you are unsure whether a specific one qualifies.

Submitting it

Same two-step upload as the identity documents, with docType: "FUNDS". associatedId is the person's legal ID (CUIT) and associatedSubId their numberId; both are required.

Step 1: get the upload URL. Call POST /broker/v1/api/compliance/documentation/uploadUrl.

curl -X POST https://api.manteca.dev/broker/v1/api/compliance/documentation/uploadUrl \
  -H "md-api-key: $MD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
      "associatedId": "23123456789",
      "associatedSubId": "100037043",
      "docType": "FUNDS",
      "fileName": "proof-of-funds.pdf"
  }'
{ "url": "https://storage.example.com/upload-target?signature=abc123" }

Step 2: upload the file to the signed URL. PUT the raw file binary directly to the url from Step 1. Do not include the md-api-key header: this request goes straight to the storage behind the signed URL, not to the Manteca API. Set Content-Type to match the file format.

curl -X PUT 'SIGNED_URL_FROM_STEP_1' \
  -H "Content-Type: application/pdf" \
  --data-binary '@/path/to/proof-of-funds.pdf'

The review is manual. When the document is validated, verifiedLimit goes up by the amount compliance grants for it, which raises the ceiling to govLimit + verifiedLimit; read it back with GET /broker/v1/api/compliance/person/{legalId}/limits. A rejected document leaves verifiedLimit untouched.

Dólar MEP caps for companies

On top of the deposit ceiling, a company has a monthly and a yearly cap, in USD, on what it buys through Dólar MEP. The same limits endpoint returns them as monthlyLimit and yearLimit, next to what was bought so far (monthlyOperated, yearlyOperated). These four fields are not returned for an individual. See Onboarding a company → Operating as a company.


Debt and credit model

Broker balances move through a company-level ledger rather than being pre-funded per operation:

OperationEffect
BuysRun against a company-level ARS/USD overdraft (debt).
SellsCredited to the user's balance, which can hold both assets and ARS/USD.
End of dayA settlement empties users' fiat balances into company credit; settlement against your company is then performed on the net balance.

Because purchases draw on company debt, reconciliation and settlement happen at the company level — track both the per-user balances and the company accounting summary.


Operating against overdraft

Without overdraft, the flow is simple: deposit funds, create the order and track it via webhooks, and optionally withdraw the proceeds.

When operating with overdraft — letting the user confirm an operation before the funds are available — the usual flow is:

  1. The user confirms a buy (say, 10,000 ARS of Dólar MEP). Block those 10,000 ARS on your side, even though nothing executed yet.
  2. Send the creation request to Manteca. If creation fails for any reason, refund the blocked funds to the user on your side.
  3. Within a few seconds, the execution webhook arrives with the amount actually traded in details.operatedAmount — creation returns an estimate, which is not necessarily what ends up being operated. Reconcile the difference against the initial 10,000 ARS: settle the overdraft with Manteca for the operated total, and re-credit the unused funds to the user.

Reference

For endpoint contracts, see the API Reference.


Did this page help you?