Update the Key Improvements in V2, API Comparison, and Migration Considerations sections to include the endpoint changes
Payroll V2 introduces an enhanced version of the SingleView Payroll APIs, with updated endpoint URLs, improved request and response structures, clearer response and error handling, and better performance.
This page outlines the key differences between Payroll V1 and V2 to help developers understand the changes and prepare their integrations for the updated APIs.
Payroll V2 covers the following operations:
Payroll V2 introduces updated endpoint URLs for payroll operations. Integrations using V1 must be updated to use the corresponding V2 endpoints.
Service | V2 | V1 |
|---|---|---|
Process Payroll |
|
|
Payroll Enquiry |
|
|
Cancel Payroll |
|
|
Payroll V2 introduces an improved structure for request and response payloads, making payroll information more consistent and easier to process.
Developers should review the updated payload formats and adjust their request-building and response-parsing logic accordingly.
V2 provides improved clarity in transaction responses and error details, helping developers identify processing statuses, understand failures, and implement appropriate error-handling logic.
Use the Payroll Enquiry API to retrieve updated payroll transaction statuses where supported.
Payroll V2 includes performance optimizations designed to make API interactions more efficient and provide a smoother integration experience.
Feature | Payroll V1 | Payroll V2 |
|---|---|---|
Endpoint URLs | V1-specific endpoint paths | Updated V2 endpoint paths |
Request structure | Included excessive objects | Enhanced payload structure |
Response structure | Inconsistent response format | Improved and streamlined response structure |
Error handling | No error handling | Clearer error details and response handling |
Performance | Speed | Improved performance |
Before migrating an existing integration from V1 to V2, review the following:
New integrations should use Payroll V2. Existing V1 integrations should be reviewed and updated to accommodate the new endpoint URLs and revised request and response structures before switching to V2.
Refer to the individual API reference pages for the latest specifications, mandatory fields, status definitions, and applicable bank-specific requirements.