request_ref_conflict: The requestRef was used for a different payment
A payment (POST /owner/v1/human/payments) reuses a requestRef already recorded on this budget for a payment with a different payee, amount or parent stream. A requestRef names one payment: a retry with the same values pays once, and different values are refused. Nothing was paid (fail closed).
Other routes that key a retry on requestRef answer the same reason:
- a stream open (
POST /owner/v1/budgets/{id}/streams) whoserequestRefalready opened a stream with anotherserviceNode, cap or rate (the samerequestRefunder another parent opens a separate stream): 409{"error": "state", "reason": "request_ref_conflict", "detail": "…"}, with noerrorDetail; - a payment authorization (
POST /owner/v1/streams/{id}/payment-authorizations) whoserequestRefwas used for another payee or amount, or already holds a reservation for another amount: 409 withreasonrequest_ref_conflictanderrorDetail.codestate_conflict; - the connector's delegation tool, whose
requestRefalready delegated to another serviceNode or cap: a refused tool result withreasonrequest_ref_conflict.
What to do
- Use a new
requestReffor a different payment. - To retry the earlier payment, send exactly the same payee, amount and parent stream.
On the wire
HTTP 409, error type state_error, errorDetail.param requestRef.
{
"error": "state",
"errorDetail": {
"type": "state_error",
"code": "request_ref_conflict",
"message": "requestRef already used for a different payment (fail closed)",
"param": "requestRef",
"doc_url": "…/developers/human-payments.md#request-ref-conflict",
"fix": "use a new requestRef for a different payment"
}
}
See human payments and all error codes.