Charge
Developing
POST
/{{api_version}}/autodebit/{{merchant_id}}/charge
Creates charge orders for enrolled customers.
See the section here
If the same document repeats within the request, already has a pending charge from another request sent today, or already has an active charge order at the bank (within its retry window), the record isn't saved: it shows up in
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.Request
Body Params application/jsonRequired
Responses
Response Response Example
202 - Accepted
{
"status_code": 202,
"message": "Charge record(s) processed successfully",
"data": {
"processed": 2,
"total": 2,
"duplicates": [],
"not_ready_to_send": [],
"recently_charged": [],
"warnings": []
}
}Modified at 2026-10-02 17:56:45