Payroll status
curl --request GET \ --url https://api.ztlpay.io/api/v2/payroll/7c628b2e-9094-4bf8-af23-1d517c6fc4f5/status \ --header 'Authorization: Bearer <token>'Retrieves latest payroll status.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Id received when creating the payroll
Example
7c628b2e-9094-4bf8-af23-1d517c6fc4f5Responses
Section titled “Responses”Payroll status
The initial payroll status indicates if the payroll was accepted, and if it needs to be signed before it will be executed in the bank
object
object
Same identifier as when creating a transaction
The timestamp of the most recent internal update to the payroll status.
UnsignedThe user must approve the payroll.InProgressThe transaction is ongoing.CompletedThe transaction/salary has been paid out.RejectedThe transaction has been rejected.CancelledThe transaction has been cancelled.CustomerActionRequiredThe payroll requires further action from the user.
PartlySignedIndicates that the payments needs additional signing. This requirement may be set up for the bank account.SmsConfirmationRequiredThe user needs additional confirmation with responding SMS received. Only used by a few banksInsufficientFundsThe payment has been stopped by the bank due to lack of funds
Example
{ "transactions": [ { "timestamp": "2025-12-30 06:43:45.569610 +00:00", "payrollStatus": "Unsigned", "payrollStatusReason": "PartlySigned" } ]}Bad Request
object
INVALID_CONSENTConsent is invalidAUTHENTICATION_TEMPORARY_UNAVAILABLEAuthentication service is temporary unavailable, most likely due to user already has started another concurrent authentication processUNSUPPORTED_PRODUCT_BY_BANKProduct is not supported by bank
Unique RequestId, please provide this Id in case of support requests
The underlying reason for the error
Example
{ "failure": "INVALID_CONSENT", "ztlRequestId": "3a797348-ef0c-4f52-b821-fdfcdb98c4d9", "message": "Invalid Bban"}Forbidden
object
Unique RequestId, please provide this Id in case of support requests
The underlying reason for the error
Example
{ "ztlRequestId": "3a797348-ef0c-4f52-b821-fdfcdb98c4d9", "message": "Invalid account"}Headers
Section titled “Headers”Unique RequestId, please provide this Id in case of support requests
Example
3a797348-ef0c-4f52-b821-fdfcdb98c4d9Not found
object
Unique RequestId, please provide this Id in case of support requests
The underlying reason for the error
Example
{ "ztlRequestId": "3a797348-ef0c-4f52-b821-fdfcdb98c4d9", "message": "Invalid account"}Headers
Section titled “Headers”Unique RequestId, please provide this Id in case of support requests
Example
3a797348-ef0c-4f52-b821-fdfcdb98c4d9Internal server error
object
Unique RequestId, please provide this Id in case of support requests
The underlying reason for the error
Example
{ "ztlRequestId": "3a797348-ef0c-4f52-b821-fdfcdb98c4d9", "message": "Invalid account"}Headers
Section titled “Headers”Unique RequestId, please provide this Id in case of support requests
Example
3a797348-ef0c-4f52-b821-fdfcdb98c4d9Service unavailable
object
Unique RequestId, please provide this Id in case of support requests
The underlying reason for the error
Example
{ "ztlRequestId": "3a797348-ef0c-4f52-b821-fdfcdb98c4d9", "message": "Invalid account"}Headers
Section titled “Headers”Unique RequestId, please provide this Id in case of support requests
Example
3a797348-ef0c-4f52-b821-fdfcdb98c4d9