Cowrie Research

cashramp

4 min read

Cashramp

  • Name: Cashramp
  • URL: https://cashramp.co/
  • Category: African local-rail and stablecoin settlement company / agent-network operator / merchant and business-payout workflow company
  • Tags: ethereum-ecosystem
  • Summary: Cashramp belongs in companies/ because the practical dependency is not a neutral onramp primitive. A named operator decides which African countries and payment methods are live, which agents are admitted to the network, how quotes and escrowed liquidity are routed, how KYC and virtual-account issuance work, and what webhook or dashboard state merchants and businesses trust as settlement truth. The business shell now also spans Accrue-branded payout, account, and card packaging, which makes the entity boundary more useful than a narrow ramp API note.
  • What it does:
    • Operates a peer-to-peer agent network where agents escrow stablecoins, publish local-currency availability, and complete collections or payouts for users
    • Exposes three merchant integration paths — Hosted Ramp, Direct Ramp, and Onchain Ramp — that all rely on the same company-run routing, quoting, and settlement machinery
    • Supports bank-transfer and mobile-money rails across a wide African corridor set, with the docs describing 30+ countries and live method discovery through API queries rather than a fixed static list
    • Provides a GraphQL API for quotes, deposits, withdrawals, customers, payment methods, transaction queries, and webhook-backed lifecycle handling
    • Issues virtual USD ACH accounts with KYC and terms-of-service workflow tied to account activation and status transitions
    • Markets a broader Accrue business stack around USD and EUR accounts, local collections, cross-border payouts, vendor payments, wallet payouts, and virtual cards, which makes the operator shell broader than one consumer onramp page
  • Key claims:
    • The main site describes Cashramp as a peer-to-peer agent network that enables Africans to make seamless cross-border payments, says agents escrow stablecoins with Cashramp, and says the platform automatically assigns users to agents for payout or collection flows
    • The payment-rails docs say Cashramp supports 30+ countries across Africa with mobile-money and bank-transfer rails, and explicitly warn integrators to query live payment-method data for the authoritative available set, which is a strong signal that Cashramp itself is the live routing and availability control plane
    • The Direct Ramp docs describe a pure API integration for converting African currencies to USD stablecoins and vice versa, emphasizing real-time quotes, multiple rails, and Cashramp settlement infrastructure rather than a neutral protocol layer
    • The integration guide shows authenticated GraphQL access through Cashramp-managed Bearer tokens and a company-hosted API endpoint at api.useaccrue.com, which reinforces that this is a named operator boundary with credential and environment control
    • The virtual-bank-account docs say Cashramp can request USD ACH virtual accounts, charges a non-refundable KYC fee, emails customers KYC and ToS links, and controls account states such as requested, pending, active, and freezing, all of which are clearly operator-governed workflow rather than protocol behavior
    • The webhooks docs make Cashramp the source of truth for payment-request lifecycle, onchain withdrawal status, onchain deposit receipt, and chargeback initiation, which matters because downstream merchants and apps will often treat those webhook states as authoritative
    • The Accrue business site markets one-company packaging for USD/EUR accounts, local collections, cross-border payouts across Africa, stablecoin rails, and virtual cards, showing that the entity boundary is broader than a single onramp widget or corridor API
  • Whitepaper: No classic standalone company whitepaper is the important artifact here. The useful primary materials are the Cashramp site, payment-rails and integration docs, virtual-account and webhook docs, and the broader Accrue business site. The earlier source bundle remains ../whitepapers/cashramp-primary-sources-2026-05-07.md.
  • Sources:

Internal linkages

Protocol / company boundary

  • There is not a very useful standalone Cashramp protocol boundary doing most of the analytical work.
  • The important surface is the company-run shell around agent admission, corridor coverage, quote selection, KYC workflow, virtual-account issuance, webhook truth, and payout execution.
  • That is why this note belongs in companies/: the practical question is who operates the local-rail and stablecoin settlement network businesses inherit, not whether there is a neutral lower-layer primitive underneath it.

Control surface

  • Practical leverage sits in country and payment-method coverage, agent admission and liquidity availability, quote and assignment logic, KYC and ToS workflow, virtual-account issuance, chargeback handling, webhook truth, and which collection or payout paths Cashramp exposes to merchants and Accrue-branded business users.

  • The sticky dependency is operational memory: once a business relies on Cashramp for African corridor access, webhook-backed payment state, agent-network execution, and account or card packaging through the wider Accrue shell, the dependency is on the named operator graph more than on any one API mutation.

  • Read Cashramp as a regional money-movement operator first, and as an onramp or stablecoin API second.

  • Last reviewed: 2026-08-11 UTC

Graph View

Backlinks