Peanut

  • Name: Peanut
  • URL: https://peanut.me/
  • Category: consumer stablecoin payments app / self-custodial remittance infrastructure / smart-account wallet
  • Summary: Peanut is a consumer-facing global payments app built around digital dollars, especially USDC, for cross-border peer-to-peer transfers, payment links, and local bank cash-out. Its official materials emphasize self-custodied ERC-4337 smart accounts, biometric passkeys, low-friction transfers without mandatory KYC for core flows, and cash-out rails across Latin America, which makes it better cataloged as a self-custodial global money app and remittance layer rather than as a simple wallet or generic crypto payment link tool.
  • What it does:
    • Lets users send and receive digital dollars globally through an app-based peer-to-peer payment flow
    • Supports payment links so funds can be sent to recipients before they have an account
    • Offers local bank cash-out and fiat conversion flows across Latin American corridors including Argentina, Brazil, Mexico, Colombia, Peru, and Bolivia
    • Uses self-custodied ERC-4337 smart accounts with biometric passkeys instead of seed-phrase-first wallet UX
    • Supports crypto deposits from exchanges and wallets, plus card spending and QR-payment features according to the project’s own product description
    • Maintains a public GitHub surface spanning smart contracts, SDK, API, and UI repos, which is a meaningful signal that the product is more than a closed mobile app shell
  • Key claims:
    • Peanut’s llms.txt says the product offers “instant global peer-to-peer payments in digital dollars” and explicitly highlights self-custodied accounts, payment links, and local bank cash-out
    • The llms-full.txt file says funds sit in ERC-4337 smart accounts, account access is secured by biometric passkeys, and core send/receive flows do not require KYC
    • The same llms-full.txt file says bank connections trigger a one-time identity check via Persona, while Peanut receives only a pass/fail result rather than storing user documents itself
    • Peanut’s support surface positions the product around verification, passkeys, payments, deposits, and account recovery, which reinforces that it is trying to abstract stablecoin infrastructure into a mainstream money app
    • The public GitHub organization lists contracts, SDK, API, and UI repos, and the contracts repo plus SDK repo show Peanut ships an actual protocol/tooling layer underneath the consumer app
    • The smart-contract repo references deployed contracts and a bug-bounty program, while the SDK repo describes the core function as sending tokens through cryptographically secure links
  • Whitepaper: No canonical Peanut whitepaper or litepaper surfaced in this pass. The clearest current source of truth is Peanut’s own llms.txt / llms-full.txt files, help center copy, and public GitHub organization plus contract/SDK repos; see ../whitepapers/peanut-primary-sources-2026-04-27.md.
  • Sources:
  • Last reviewed: 2026-04-27 UTC