Docs

Fincore · Get started

Fincore

Monato's API for payment operations in Mexico. Receive SPEI deposits, send money to CLABE accounts and debit cards, and assign dedicated CLABEs.

Fincore is Monato’s API for payment operations in Mexico. It connects your systems with SPEI and Monato internal rails through a single integration model.

What you can build

Capability Use it for
Receive money Receive SPEI deposits into your Monato accounts and get webhook notifications.
Send money to a CLABE Send SPEI transfers to bank accounts.
Send money to a debit card Use the same Money Out operation with a 16-digit debit card as the destination.
Internal transfers Move money book-to-book between Monato instruments without SPEI. New integrations should use Money Out; routing is automatic.
Validate a bank account Send $0.01 MXN and receive CEP ownership data through webhooks.
Private accounts Assign dedicated CLABEs to customers, products or collection flows.
Business units Model sub-accounts as independent legal entities with their own RFC and CLABE.
Reports Download generated transaction reports and account statements.

Start building

  • Quickstart: get a token, find your Centralizing Account, register a recipient and send your first Money Out.
  • Concepts: clients, accounts, instruments and Business Units.
  • API reference: every endpoint and webhook event with its schema.
  1. Create an API token.
  2. Retrieve your Centralizing Account.
  3. Register webhooks for MONEY_IN, STATUS_UPDATE, CEP and REPORT as needed.
  4. Register destination instruments.
  5. Send Money Out with an idempotency key and validate the status webhook.
  6. Receive and test Money In with a real or controlled inbound SPEI flow.
  7. Reconcile both Money Out and Money In from webhooks and reports.

Money Out and Money In are the two critical payment flows to validate before going live. Money In is inbound and your system does not start it, but your integration must still persist, classify, accept or reject, and reconcile each event reliably.

How it works

Most payment operations are asynchronous. The synchronous Money Out response only confirms that Fincore accepted the request. The final transaction state and inbound Money In events arrive through webhooks and reports.

Step What you do Where
1 Get credentials and create a bearer token Quickstart
2 Retrieve your Centralizing Account and the bank catalog Concepts
3 Register recipients as instruments Send money to a CLABE
4 Send Money Out Send money to a CLABE
5 Receive and test Money In Receive money
6 Receive asynchronous status events Webhook events
7 Reconcile outcomes and errors Reports, Error catalog

Conventions

Convention Detail
Request casing Request bodies use snake_case.
Response casing Most responses use camelCase.
IDs UUID strings, for example client_id, account_id, instrument_id and customer_id.
Amounts Strings with two decimals, for example "5000.00".
Currency MXN.
Dates Mexico City local time (UTC-6). Most timestamps carry an explicit -06:00 offset; a few omit it. See Timestamps and timezone.

Do not log or expose CLABEs, card numbers, secrets or webhook tokens in client-facing systems.

Environments

The public reference uses the staging base URL:

Text
https://apicore.stg.finch.lat

Production credentials and the production base URL are provided during onboarding.