Reap

• Name: Reap
• URL: https://reap.global/
• Category: modular fintech infrastructure / stablecoin card-and-wallet control plane / compliance and ledger API
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Reap is a modular card-and-wallet control plane. The useful part is not cards + wallets as product copy. It is the single operator surface for onboarding, ledger state, deposit approval, card controls, and reconciliation once stablecoin balances need to become card spending power.
• What it does:
  • Lets partners create user- or company-owned spending accounts that back card programs and track available balance as assets minus liabilities
  • Supports multichain stablecoin deposit funding, with docs explicitly covering supported assets on Ethereum and Solana in production plus sandbox test assets on Ethereum Sepolia and Solana Devnet
  • Exposes KYC/KYB onboarding, user/company application workflows, account creation, card issuance, freeze/unfreeze, 3DS challenge handling, shipping, and reconciliation APIs
  • Provides webhook events for deposit lifecycle changes, account/card status changes, and card transaction lifecycle updates so integrators can stay in sync without polling
  • Uses a unified versioned REST API with bearer-key auth and a required Reap-Version header
  • Supports both direct stablecoin-funded accounts and prefund-style projects that allocate virtual assets from a master collateral account
  • Documents debt-clearing and reconciliation flows that burn virtual assets against outstanding card debt, which shows the platform is managing settlement logic rather than only exposing a wallet or card façade
• Key claims:
  • The docs introduction describes Reap as “Modular fintech infrastructure. Cards, wallets, compliance, and payments via a single API.”
  • The introduction says partners can launch card programs, onboard users with built-in compliance, accept stablecoin deposits across multiple chains, and track everything in a unified ledger
  • The accounts overview says an account is the unit of spending in Reap, every card is issued against an account, every authorization is evaluated against an account balance, and balance is computed as availableBalance = assets - liabilities
  • The accounts overview also distinguishes direct stablecoin deposits from prefund virtual-asset allocation models, which is a strong clue that Reap is a financial control plane rather than only a deposit API
  • The deposits guide says supported tokens sent to deposit addresses move through PENDING, CONFIRMED, and APPROVED states, with webhook notifications at creation and each status change
  • The supported-assets page documents production support for USDC and USDT on Ethereum and Solana and notes active expansion of supported chains and tokens
  • The webhooks docs describe a signed event system with HMAC verification, exponential retry over roughly 48 hours, and events spanning KYC/KYB, deposits, account state, and card transactions
  • The reconciliation API explicitly clears outstanding card debt by burning submitted virtual assets, which shows Reap is handling settlement and ledger semantics, not just issuing cards
• Whitepaper: No canonical standalone Reap whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official docs corpus, especially the introduction, account/deposit guides, webhook docs, and versioned API reference; see ../whitepapers/reap-primary-sources-2026-04-30.md.
• Sources:
  • https://reap.global/
  • https://docs.reap.global/
  • https://docs.reap.global/llms.txt
  • https://docs.reap.global/introduction.md
  • https://docs.reap.global/quickstart
  • https://docs.reap.global/accounts/overview
  • https://docs.reap.global/accounts/deposits
  • https://docs.reap.global/accounts/supported-assets
  • https://docs.reap.global/api-reference/introduction
  • https://docs.reap.global/webhooks/overview
  • https://docs.reap.global/api-reference/reconciliations/reconcile-outstanding-card-debt

Internal linkages

• Best upward reads: gnosis-pay, rain, and openpayd.

Control surface

• Authority sits in onboarding approval, account and ledger policy, deposit approval, card issuance, prefund versus direct-deposit mode, and reconciliation logic.

• The useful distinction is that Reap turns stablecoin balances into spendable card-state inside one hosted ledger and compliance surface.

• Read it as modular fintech middleware, not as a new wallet substrate or a payment rail.

• Last reviewed: 2026-06-01 UTC