Validate Due-Date Charge (COBV)
Validates a due-date charge (cobv) by its txid and returns it in the same shape as the cob validation, with the calendar carrying dueDate and validAfterDueDays instead of an expiration in seconds.
It answers only for cobv. Which route answers is what tells a caller the kind of charge a txid names, and the Pix API depends on that distinction: among the violations of GET /rec/{idRec} it lists a txid that does not match a charge compatible with ativacao.tipoJornada, with the example of a CobV txid against JORNADA_3.
Path Parameters
- Type: stringtxidrequired
Transaction identifier (txid) of the due-date charge to validate. Must be 26-35 lowercase alphanumeric characters [a-z0-9]
Responses
- application/json
- application/json
- application/json
- application/json
- application/json
- application/json
- application/json
Request Example for get/api/cobv/{txid}/validate
curl http://localhost:8080/api/cobv/txid12345678901234567890123456/validate \
--header 'Authorization: Bearer YOUR_SECRET_TOKEN'
{
"txid": "string",
"status": "ACTIVE",
"revision": 1,
"calendar": {
"createdAt": "2026-09-16T19:14:18.660Z",
"expiration": 1,
"dueDate": "2026-09-16",
"validAfterDueDays": 1
},
"amount": {
"original": "string",
"changeMode": 1,
"cashWithdrawal": {
"withdrawal": {
"cashAmount": "string",
"changeMode": 1,
"agentModality": "AGTEC",
"cashierIspb": "string"
},
"change": {
"cashAmount": "string",
"changeMode": 1,
"agentModality": "AGTEC",
"cashierIspb": "string"
}
}
},
"key": "string",
"location": {
"id": "string",
"url": "string"
},
"payerRequest": "string",
"additionalInfo": [
{
"name": "string",
"value": "string"
}
]
}