Reap company primary sources — 2026-08-13

Project status in this pass

• This pass was about deciding whether Reap deserves a separate companies/ note rather than only a projects/ note.
• Answer: yes. The current primary materials show a named company-and-affiliates boundary operating KYB/KYC, accounts, cards, payments, expense controls, webhook truth, and regional licensing posture.

Primary-source snapshots

1) Privacy policy

• URL: https://reap.global/resources/info/privacy-policy
• Key excerpt:
  • The policy says: Reap Technologies Limited and our affiliated companies (collectively, "Reap").
  • This is the cleanest current legal-entity anchor surfaced in this pass.
  • The same policy shows Reap collecting identity, company, billing, transaction, and recipient information across its sites and services, which reinforces that the company boundary is doing more than publishing marketing copy.

2) Terms of use

• URL: https://reap.global/resources/info/terms-of-use
• Key excerpt:
  • The website terms bind use of the Reap website to Hong Kong law and HKIAC arbitration in Hong Kong.
  • The page repeatedly treats Reap and its affiliates as the relevant operating party around the public website and referenced products and services.
  • This does not fully map every affiliate, but it does confirm a legal-and-operational shell rather than a purely anonymous brand page.

3) About page

• URL: https://reap.global/resources/company/about-reap
• Key excerpt:
  • Reap says it is building stablecoin-powered financial infrastructure and that it has distilled its experience and technology into proprietary API solutions enabling other businesses to create payment solutions.
  • The page says Reap was founded in 2018 and that leadership helped build a global team of 200+ across eight markets.
  • This matters because the company note is not only about a consumer product brand; it is about a multi-market operating organization packaging payments infrastructure for other businesses.

4) Business Account page

• URL: https://reap.global/products/business-account
• Key excerpt:
  • Reap markets one stack combining Business account, corporate cards, stablecoin payments and expense management.
  • The page says onboarding is 100% online KYB, most companies are approved in 3 business days, and the FAQ says Reap is a licensed financial technology company, regulated across Hong Kong and Mexico. Reap is not a bank.
  • The same page says users can fund in USDC or USDT, then issue corporate cards, pay suppliers in local currency, and manage expenses from one stablecoin balance.
  • This is strong evidence that the practical dependency is a company-run treasury, onboarding, and workflow shell rather than only a card API.

5) Cards page

• URL: https://reap.global/products/cards
• Key excerpt:
  • Reap says users can collateralize an account with USDC, USDT, or fiat and get a 1:1 credit line whose collateral becomes spending power.
  • The page emphasizes spend limits, approval workflows, merchant-type / location / time-of-day controls, mobile-wallet support, ATM access, and risk tooling such as 3D Secure and Visa Risk Manager.
  • This confirms the operator boundary sits in card policy, collateral handling, and spend-control workflow, not just in generic wallet marketing.

6) Docs introduction

• URL: https://docs.reap.global/introduction.md
• Key excerpt:
  • Reap describes itself 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.

7) Accounts overview

• URL: https://docs.reap.global/accounts/overview
• Key excerpt:
  • An account is the unit of spending in Reap: every card is issued against an account, authorizations are evaluated against account balance, and settlement clears debt on the account.
  • The docs define availableBalance = assets - liabilities and distinguish direct funding from prefund programs.
  • This is strong evidence that Reap operates a ledger and settlement control plane, not just a thin card veneer.

8) Webhooks overview

• URL: https://docs.reap.global/webhooks/overview
• Key excerpt:
  • Reap sends signed HTTP POST webhooks with HMAC-SHA256 verification and retries non-2xx outcomes with exponential backoff over roughly 48 hours.
  • Event types span company and user application status, deposits, account status, card status, and card-transaction lifecycle updates.
  • That makes Reap part of the authoritative callback-truth surface customers inherit.

Working conclusion

Reap now clearly clears the bar for a separate companies/ note. The useful question is not only how do Reap accounts, cards, deposits, and reconciliation objects behave? but also which named operator runs KYB/KYC, licenses, accounts, webhook truth, card-policy workflow, and the stablecoin-to-fiat treasury shell around them? In this pass, the answer is visibly company-shaped: Reap Technologies Limited and affiliated companies operating the broader Reap shell.