/v1/payment-schedules/{id}/servicing-authorizationsA schedule's debit authorisations
The merchant's signed permissions to debit this schedule — the legal evidence that taking the money was allowed — newest first, with the channel and address the request went to, the amount and frequency authorised, the exact words the customer was shown, the three consents, when and from what IP it was accepted, and why it was closed. ?limit= caps the page. Anything pending whose window has closed is retired to expired before the answer is built, so a pending row here is genuinely still pending. These are PERMISSION records, not money: for the instalments and what has been collected reach for get_payment_schedules_id_payments.
Access class: workspace.
Send request
Use the documented inputs to call this endpoint directly.
Parameters
Values are applied to the request and the example on the right.
Responses
the action's answer
{
"data": [
{
"acceptedAt": "string",
"acceptedIp": "string",
"acceptedUserAgent": "string",
"achAuthorizationAccepted": true,
"amountMinor": 1,
"authorizationText": "string",
"cancelledAt": "string",
"closedReason": "string",
"consentToDebit": true,
"contactChannel": "string",
"contactTarget": "string",
"counterpartyId": 1,
"createdAt": "string",
"currency": "string",
"detail": {},
"expiresAt": "string",
"facilityId": 1,
"frequency": "string",
"id": 1,
"revokedAt": "string",
"scheduleId": 1,
"sourceReference": "string",
"status": "string",
"termsAccepted": true,
"updatedAt": "string"
}
]
}a refusal: {"error": "<what a person needs to read>"}. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.
{
"error": "string"
}