Cash concepts

Operation

An operation is a cash movement that your user completes at a physical location. There are two kinds:

Kind	Purpose	Expires
`cash_in`	The user deposits money at a physical location	3 days after creation
`cash_out`	The user withdraws money at a physical location	60 minutes after creation by default. You can configure it to last longer.

Each operation has an operation_id, a 20-digit reference, a 25-character transaction_id, an amount in MXN, a status, a created_at and an expire_at.

Reference

The reference is a unique 20-digit number. Your user needs it to complete the operation at the physical location, so store it and show it to them. You also use it to look up the operation.

Open reference

Some clients can create cash-in operations without an amount. These are open references: the amount is decided when the user pays at the location. Until then, amount is 0.

Open references expire on the custom date you set during creation. They do not send status webhooks. See Webhook events.

Bulk cash-in

You can create from 1 to 1000 cash-in operations in one request, with a shared expiration date. They are created asynchronously. This is useful for pre-generating payment references to distribute. See Create a cash-in operation.

External user

external_user_id is your own unique identifier for the end user. It is required on every operation. Each user can make up to 5 operations per day. See Limits and expiration. You can also send the user’s phone and an identity document (document_type and document_id).

Status

Status	Meaning
`unpaid`	Initial status. The operation is ready to be paid.
`paid`	The user completed the deposit or withdrawal and all validations succeeded.
`expired`	The expiration window passed. The operation can no longer be completed.
`reversed`	An issue occurred during processing at the physical location and the transaction was voided.

See Operation statuses.

Webhook

Monato sends a webhook to your endpoint when an operation is paid, expires or is reversed. Only one webhook can be active per client. See Webhook events.