4 ms·

If I understand this correctly, your clients are people like lenders (e.g someone who lends money to Uber drivers who want to buy a car) who need assurances abo

by abraae 5y ago

If I understand this correctly, your clients are people like lenders (e.g someone who lends money to Uber drivers who want to buy a car) who need assurances about the their customer's status, e.g whether they truly were an Uber driver for the last 2 years. So with your system the driver will supply you with their Uber credentials, and you will log into Ubers system on their behalf, extract key information such as the number of rides they have done, and pass that info back to your client. Like open banking as you say. I hope I have that right, I initially thought that an API for payroll meant that you offered a service that paid people and handled taxes in Latin America. (Just my worldview since we are in the HR business). However I now understand that you are in fact an API to extract data from any number of payroll systems. Just thought I would share that with you as I found it initially confusing, but that's probably on me, and your messaging may well be perfectly on target. Good luck going forward and I hope for your success.

pierre62360 5y ago
You are perfectly right, your description is perfectly on point, even though our description confused you at first. To be honest, I'm not too much a fan of Payroll API too, but it seems it is the term that is now coined in the US for what we are doing (see that article from a16z: https://a16z.com/2020/10/20/payroll-apis/ https://a16z.com/2020/10/20/payroll-apis/) If you happen to have an another idea about a very quick way to describe what we are doing (less than 10 words), that would be great !
- abraae 5y ago
  That is an interesting article indeed. I see that after the headline, they immediately revert to talking about "payroll-connected APIs". They use this phrase 3 or 4 times, then they switch back to "payroll APIs" towards the end. All in all I don't know that "payroll-connected API" is any better for you - quite a mouthful and sounds way more techy. Personally I would like "Payroll verification API" but maybe that's just because we're having this discussion and that fancy will disappear like dust in the wind by the end of the day. It might also preclude you from getting into some of the juicier areas that a16z are talking about (i.e. things that are > just verifiying data), but of course you can always change your tagline :) FYI this area is of interest as we briefly explored automating some nasty govt systems using selenium or similar (aka RPA). We would run the robot in a VM that was torn down at the end of every session for security. We presented the UI to the user via guacamole - then once they had entered their credentials, the robot took over. Interesting but not the path we took in the end.
  - pierre62360 5y ago
    You're right, "connected" can add more clarity. For the automation of some govt systems, you didn't try a "proper" reverse engineering where don't use selenium, but rather uncover the private APIs of the govt ?

by abraae 5y ago

pierre62360 5y ago

You are perfectly right, your description is perfectly on point, even though our description confused you at first. To be honest, I'm not too much a fan of Payroll API too, but it seems it is the term that is now coined in the US for what we are doing (see that article from a16z: https://a16z.com/2020/10/20/payroll-apis/ https://a16z.com/2020/10/20/payroll-apis/) If you happen to have an another idea about a very quick way to describe what we are doing (less than 10 words), that would be great !

abraae 5y ago
That is an interesting article indeed. I see that after the headline, they immediately revert to talking about "payroll-connected APIs". They use this phrase 3 or 4 times, then they switch back to "payroll APIs" towards the end. All in all I don't know that "payroll-connected API" is any better for you - quite a mouthful and sounds way more techy. Personally I would like "Payroll verification API" but maybe that's just because we're having this discussion and that fancy will disappear like dust in the wind by the end of the day. It might also preclude you from getting into some of the juicier areas that a16z are talking about (i.e. things that are > just verifiying data), but of course you can always change your tagline :) FYI this area is of interest as we briefly explored automating some nasty govt systems using selenium or similar (aka RPA). We would run the robot in a VM that was torn down at the end of every session for security. We presented the UI to the user via guacamole - then once they had entered their credentials, the robot took over. Interesting but not the path we took in the end.
- pierre62360 5y ago
  You're right, "connected" can add more clarity. For the automation of some govt systems, you didn't try a "proper" reverse engineering where don't use selenium, but rather uncover the private APIs of the govt ?