> For the complete documentation index, see [llms.txt](https://pay-griffin.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pay-griffin.gitbook.io/whitepaper/about-griffin-payroll.md).

# ABOUT Griffin Payroll

<mark style="color:purple;">**Griffin Payroll**</mark>**&#x20;is Private crypto payroll all-in-one solution for web3 organizations**

![](/files/5gaC3wJU6yKsOY4p9dp2)

**Griffin Payroll** is built for Enabling Web3 organizations to automate crypto payroll system \
in the most private\&handy way.&#x20;

{% hint style="success" %}
***Problem We Solved***
{% endhint %}

&#x20;**M**any people in the Web3 scene are already paid with crypto, and statistics show that the amount of crypto paid as wages is expected to increase. In this context, solutions that make crypto payroll easier are also emerging recently, and examples include *Request.Finance.*&#x20;

&#x20;**H**owever, the biggest problem with all of these services is that all transactions are inevitably transparent due to the characteristics of the existing blockchains. So all the salary amount, timing, and recipient's wallet address used to disclosed.&#x20;

&#x20; **I**n fact, most companies are reluctant to disclose the amount of wages employees receive due to their advantag e in salary negotiations and relationship issues between employees.&#x20;

&#x20;**S**o existing crypto payroll services do not meet the company's needs regarding this privacy issue, and this is one of the biggest reasons why crypto wage payments are not becoming popular.

> <mark style="color:purple;">**GriffinPay**</mark> <mark style="color:green;">solved this problem with</mark> <mark style="color:purple;">Polygon Nightfall</mark>
>
> <mark style="color:purple;">We provide absolutely non-transparent, private crypto payroll transactions.</mark>

![](/files/gNj0FuJmi4bfa6cHshCn)
