Send a banking API transfer

Destructive

This tool moves real money. It validates the destination account before sending, and executing the transfer requires a confirmation code sent to your email. Without that code the operation is not sent.

These tools are enabled on request and only work for users with Tilopay banking API credentials. They are not part of the default MCP access: Tilopay enables the group case by case. Requires: Credenciales del API bancario de Tilopay registradas por Tilopay para ese usuario.

Sensitive

baas_send_transfer

Sends a transfer from the merchant's bank account. Default method: SINPE Móvil (destination by phone). For a transfer to an account use accountType=IBAN. The Banca Cliente portal sends the authorization code to the merchant's email and applies its limits; the merchant answers the code and it is confirmed with baas_confirm_transfer.

API operation: POST /api/public/v1/transactions/payments — see the operation page

Parameters

Parameter	Type	Required	Description
`amount`	number	yes	Amount to transfer
`currency`	string	yes	ISO 4217 currency (CRC, USD)
`contactName`	string	—	Name of the saved contact (looks up their phone/IBAN)
`destinationAccountType`	string (PHONE \| IBAN)	—	PHONE = SINPE Móvil (default), IBAN = account transfer
`destinationAccountValue`	string	—	E.164 phone or destination IBAN (if contactName is not used)
`destinationName`	string	—	Recipient name (if not validated via contact)
`detailReference`	string	—	Payment description (if omitted, one is generated)
`assignmentId`	string	—	Banking API context (optional)
`allowDuplicate`	boolean	—	Solo true cuando el usuario confirmó literalmente que quiere repetir una transferencia idéntica reciente (por ejemplo 'sí, es otra'). Nunca lo pongas por tu cuenta.

Returns

{ result: { payment, clientReference, detailReference, destinationName, destinationAccount } }

Sends a transfer from a merchant's BaaS account: payment = the created payment with its payment_id and status; clientReference and detailReference = references for reconciliation; destinationName and destinationAccount = who and which account it was sent to. It validates the destination account beforehand and requires a confirmation code by email.

Last verified: 2026-10-07 · Owner: equipo-integraciones

View as raw Markdown