An individual who interacts with the workforce management system integrated with the API. Users are typically employees or workers within an organization. The RESP API empowers clients to create new user accounts and retrieve or update user information. These actions may include enrolling for on-demand pay, accessing and managing payroll-related information and initiating transfers of funds. It is important to note that the specific functionalities and capabilities available to users can vary depending on the particular implementation.

Currently, while users can have multiple employers, only one can be associated with their on-demand pay options and integrated with our REST API.

An employer represents an organization that uses the integrated workforce management system. Employers can often manage employee profiles, approve on-demand pay requests, generate payroll reports, monitor workforce analytics, and configure pay cycles and schedules. The REST API empowers employers to streamline workforce management tasks and efficiently handle employee compensation and administration.

• The specific details of a pay cycle can vary among clients and organizations. However, a typical pay cycle for clients often follows a regular schedule, such as weekly, bi-weekly (every two weeks), semi-monthly (twice a month), or monthly.
• During a pay cycle, employees' working hours, wages, and other factors relevant to compensation are recorded and processed by their employer. For on-demand pay to work, payroll calculations are performed on a shift-by-shift basis, and employees have visibility and access to their current earned income at that point in the given pay period.

Clients utilizing the REST API may have various types of pay schedules based on their specific needs and requirements. Some common types of pay schedules include:

1. Weekly: Employees are paid weekly, typically every seven days.
2. Bi-weekly: Payroll is processed every two weeks, resulting in 26 pay periods per year.
3. Semi-monthly: Employees receive paychecks twice a month, often on specific dates such as the 15th and the last day of the month.
4. Monthly: Payroll is processed once a month, usually on a fixed date.
5. Customized: Clients may have unique pay schedules tailored to their business needs. These schedules can include irregular intervals or specific dates based on the company's pay policies.

To get started, please refer to the API documentation available on our Getting Started page. It provides step-by-step instructions, code examples, and guidelines for implementing the API endpoints.

The API leverages OAuth 2.0 for authentication. To interact with user-based operations that require an individual's consent, you'll need to obtain access tokens using the authorization grant flow. For non-user-specific operations that involve accessing endpoints such as 'organization search', you will utilize client credentials for authentication.

Read this guide to learn more about getting access tokens and the authorization grant flow.

You can use the user details endpoint provided by the API. It allows you to search for users based on various criteria, such as name, email, or employee ID.

Yes, you can retrieve payroll-related information using the paychecks endpoint. It allows you to fetch user paychecks based on specified parameters, such as user ID and date range.

You can use the transfers endpoint to initiate funds transfers between accounts. Provide the necessary parameters, such as the destination account and the transfer amount.

Yes, you can manage debit and bank cards using the card management endpoint. It enables you to add, update, or remove debit and bank cards for users. However, to add or update Debit Cards from within your application, you must be PCI-E compliant and communicate this with your DailyPay representative.

Yes, the card management functionality provided by the API adheres to PCI-E (PCIE) compliance standards. It ensures the secure handling of card information during tokenization and storage processes.

Yes, the API allows you to customize the user interface (UI) of your application to display available balance and other relevant information to end users. However, DailyPay has some rules for displaying and explaining available balance. You can leverage the API data to design a user-friendly and visually appealing UI.

Yes, we provide testing environments to facilitate API integration and testing. These environments have full API functionality but simulate transfers, which allows you to test an integration without affecting production data.

Yes, compliance and regulatory considerations might apply, such as data privacy, security, and financial regulations. Ensure that your integration follows relevant compliance standards and guidelines to protect user data and comply with applicable regulations.

We provide notifications, release notes, and changelogs on our developer portal to keep you informed about API changes, updates, and new features. Regularly check the portal for announcements or subscribe to our developer newsletter for updates.

Yes, people can have one depository and one card account designated for remainder pay, set when updating a job's paycheck settings. DailyPay will always attempt to send remainder pay to the depository account first.

The remainder is the amount left after deductions for the other specified accounts. Generally speaking, remainder pay is the net_earnings minus total_debited on each paycheck.