Skip to main content

Create Cash Topup

Path Parameters

driverId
string
required
UUID of the driver (v4 format)

Body Parameters

collectionPointId
string
required
UUID of the collection point where cash is being deposited
collectedByUserId
string
required
UUID of the staff/operator collecting the cash
amount
string
required
Deposit amount as a decimal string (e.g., “150.00”)
currency
string
default:"CUP"
ISO 4217 currency code (3 characters). Defaults to “CUP”
notes
string
Optional notes for the cash collection record
description
string
Optional description for the transaction (e.g., “cash topup at desk”)
metadata
object
Free-form metadata object (e.g., {"source": "window-3"})

Response

success
boolean
Indicates if the operation was successful
message
string
Response message
data
object
Created cash collection record
This creates a pending cash collection record and transaction. The wallet is not credited until the topup is confirmed.

Confirm Cash Topup

Path Parameters

ccrId
string
required
UUID of the CashCollectionRecord to confirm (v4 format)

Body Parameters

comment
string
Optional confirmation comment (max 500 characters, e.g., “Billetes verificados y contados”)

Response

success
boolean
Indicates if the operation was successful
message
string
Response message
data
object
Confirmed cash topup details
This operation is irreversible. It applies the credit to the wallet, creates a wallet movement record, and marks the cash collection record and transaction as completed.

Get Driver Wallet Balance

Path Parameters

driverId
string
required
UUID of the driver (v4 format)

Response

success
boolean
Indicates if the operation was successful
message
string
Response message
data
object
Driver wallet balance information

Get Wallet Movements

Path Parameters

walletId
string
required
UUID of the wallet (driver_balance.id, v4 format)

Query Parameters

page
number
default:"1"
Page number for pagination
limit
number
default:"10"
Number of items per page
transactionId
string
Filter by transaction UUID
from
string
Start date filter in ISO-8601 format (e.g., “2025-01-01T00:00:00Z”)
to
string
End date filter in ISO-8601 format (e.g., “2025-12-31T23:59:59Z”)
Search term to filter movements
sortBy
enum
default:"createdAt"
Field to sort by
  • createdAt - Sort by creation date
  • amount - Sort by transaction amount
sortDir
enum
default:"desc"
Sort direction
  • asc - Ascending order
  • desc - Descending order

Response

success
boolean
Indicates if the operation was successful
message
string
Response message
data
array
Array of wallet movement records
meta
object
Pagination metadata

Block Driver Wallet

Path Parameters

driverId
string
required
UUID of the driver (v4 format)

Body Parameters

reason
string
Reason for blocking the wallet (max 250 characters, for audit/traceability)
comment
string
Additional comment (max 500 characters, e.g., “Bloqueo preventivo hasta resolver disputa #D-1234”)

Response

success
boolean
Indicates if the operation was successful
message
string
Response message (indicates if wallet was already blocked - idempotent)
data
object
Wallet status change information
This operation is idempotent. If the wallet is already blocked, it returns success without making changes.

Unblock Driver Wallet

Path Parameters

driverId
string
required
UUID of the driver (v4 format)

Body Parameters

reason
string
Reason for unblocking (max 250 characters, e.g., “Disputa resuelta”)
comment
string
Additional comment (max 500 characters, e.g., “Se validó identidad del conductor y se cerró el ticket”)

Response

success
boolean
Indicates if the operation was successful
message
string
Response message (indicates if wallet was already active - idempotent)
data
object
Wallet status change information
This operation is idempotent. If the wallet is already active, it returns success without making changes.

Build docs developers (and LLMs) love