# Payflow > Onchain Social Payments Payflow enables users to send and receive cryptocurrency through social platforms like Farcaster, ENS, and Lens using social identifiers. Payflow helps Web3 users send cryptocurrency payments directly through social platforms by connecting social identities with payment infrastructure. Users can transfer funds using social handles instead of wallet addresses, create payment flows for collecting funds, and access cross-chain payments across multiple networks. Payflow reduces payment fragmentation by integrating with Farcaster, ENS, and Lens social graphs. - Type: Project - Sector: Payments - Status: Acquired - Founded: 2024-07-01 - Profile: https://thegrid.id/profiles/payflow ## Products - [Pay Flow](https://thegrid.id/profiles/payflow): Payflow implements social payment infrastructure through account abstraction wallets, enabling cryptocurrency transactions via social identifiers across Farcaster, ENS, and Lens platforms. The system supports cross-chain payments across multiple networks with various tokens while maintaining non-custodial wallet architecture. (Social Payments, Live, Main Product) ## Links - [Main](https://payflow.me) - [Documentation](https://payflowlabs.notion.site/Payflow-FAQs-20593cf7734e4d78ad0dc91c8e8982e5) - [Twitter / X](https://x.com/payflowme) - [Farcaster](https://warpcast.com/payflow) - [GitHub](https://github.com/sidrisov/payflow) ## Legal This data is provided under two licensing models. Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation. Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service. The following applies to both licensing models. - All data is provided AS IS with no guarantees of accuracy. - The Grid does not provide investment, legal, or tax advice, and - a project's presence in The Grid's data does not imply endorsement. - [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers - [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service. - [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service. - [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services. - [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures ## Optional - [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model - [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships - [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type - [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types - [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP