422 and nothing is saved; data.next_cutoff_date is the next cut-off date (message comes in Spanish):{
"status_code": 422,
"code": "OUTSIDE_CUTOFF_DATE",
"message": "Hoy no es fecha de corte: esta lista no se guardó. Súbela el lunes 19/10/2026 hasta las 4:00 p. m.",
"data": { "next_cutoff_date": "2026-10-19" }
}duplicates (207 response). To force it, resend it with confirm: true and an idempotency_key:resolution: sum if it's another debt (added to the pending amount) or replace if it corrects an earlier request (replaces the pending amount). With replace, also send expected_previous_amount with the previous_amount we returned. Without resolution, the record goes back to duplicates.confirm: true is enough: nothing is added.idempotency_key is safe: the amount isn't added twice.not_ready_to_send: saved charges that wouldn't go into today's bank file because of the enrollment status, with the reason.recently_charged: people the bank already charged in the last 7 days, with that charge's date and amount. The new charge still goes out; check whether it's the same one.{
"status_code": 202,
"message": "Charge record(s) processed successfully",
"data": {
"processed": 2,
"total": 2,
"duplicates": [],
"not_ready_to_send": [],
"recently_charged": [],
"warnings": []
}
}