# Ecosystem Participants ## **Payment-realated Projects** * Those projects are the direct user of our protocol. It integrates our protocol to implement crypto payment collection and other related services. * Those projects incur transaction fees during the usage process. * Those projects receive the pfToken minted by the protocol. * Those projects must be PID holders and meet certain other PID validation requirements. * Those projects need to pre-create their own wallet address in the PLP system. ## **Merchant** * The merchant is the direct user of the gateway. They use the gateway to accept crypto payments. * The merchant has their own account and fund account within the gateway. * The merchant can withdraw their funds from the gateway. * The merchant uses the wallet addresses allocated by the gateway to receive crypto payments. ## **Customer** * The customer is the direct user of the merchant. * The customer is the source of requests for wallet address allocation from the gateway. * The customer’s identity verification needs to be completed by the merchant. ## **Web3 User** * Web3 users can participate in liquid staking to provide liquidity for the fast redemption of pfUSDT and enjoy a share of transaction fees and platform revenue. * Ordinary users can perform a fast exchange between pfUSDT and USDT through the liquid staking pool. * Ordinary users can stake Polyflow Governance Tokens to earn platform revenue. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.polyflow.tech/payment-liquidity-pool-plp/ecosystem-participants.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.