Provd logo
COUNTERPARTY INTELLIGENCE FOR AFRICAN P2P PLATFORMS

Blunt risk models approve the wrong trades. And block the right ones.

African P2P platforms lose volume twice: once to fraud and once to the legitimate traders they turn away out of caution. Provd gives exchanges, wallets, and OTC desks network-backed counterparty scores so they can confidently approve more good trades, and precisely reject the bad ones. One API call. Decisions backed by signals no single platform can generate alone.

Two-factor approval illustration representing secure verification
Capabilities

Counterparty trust scoring

Score every counterparty using cross-platform dispute history, wallet activity, hashed payment identifiers, and repeat-risk patterns, so you know exactly who to approve, not just who to block.

Deployment

Built into your approval decision

Integrate Provd at the exact point where your platform decides to approve, review, or hold a trade. Responses include a score, reason flags, and a recommended action your operators can act on immediately.

Operators

For growth teams and risk teams

Designed for exchanges, wallets, and OTC desks that want to expand volume without expanding fraud exposure. Provd gives both sides of the business, revenue and risk, a shared, evidence-backed decision layer.

Designed for partners

The infrastructure layer connecting Africa's P2P ecosystem.

REQUEST LIFECYCLE

How a single API call changes your approval decision.

01
Query
Ingest
Before a trade releases, your platform sends counterparty identifiers, wallet address, hashed phone, payment rail, and trade context. Nothing raw leaves your environment.
02
Analyse
Evaluate
Provd scores the counterparty against network-wide dispute history, linked identifiers, and cross-platform fraud signals, intelligence your platform alone could never generate.
03
Score
Respond
Your platform receives a precision score, reason flags, and a recommended action, so you approve the trades you should, and only hold the ones that warrant it.
SIGNAL COVERAGE

Signals that separate good counterparties from bad ones.

Provd sits between trade intent and fund release. Each signal category contributes to a score that tells your platform not just whether a counterparty is risky, but how confident you can be approving them.

INPUT 01Non-Delivery Fraud
Dispute and fraud history
Prior non-delivery, reversals, and operator-reviewed cases from across the network feed directly into the score.
EVALUATION: Case linkage, repeat outcomes, and dispute velocity
INPUT 02Payment Reversal
Payment rail behavior
Rail-specific patterns across M-Pesa, bank transfers, and stablecoin payouts reveal timing anomalies and reversal habits invisible to a single platform.
EVALUATION: Reversal patterns, rail mismatches, and timing anomalies
INPUT 03Platform Migration
Cross-platform identity linkage
Wallets, hashed phone values, and other identifiers are matched to prior outcomes across partners, without ever exposing raw PII.
EVALUATION: Hash reuse, wallet linkage, and identity graph joins
INPUT 04Coordinated Networks
Entity network graph
Connected accounts and wallets are evaluated together. A counterparty with clean history but fraudulent neighbours gets flagged, not approved.
EVALUATION: Cluster analysis, shared infrastructure, and graph proximity
INPUT 05Social Engineering
Shared partner intelligence
Every connected platform contributes signals back to the network. The more partners, the harder it becomes for bad actors to move between desks undetected.
EVALUATION: Partner-fed outcomes and cross-platform fraud indicators
API

One call. Precision you couldn't build alone.

The API is designed for synchronous approval checks. Send trade context before release and use the response in your approval, review, or escalation path.

Your platform sends trade context. Provd returns a score, flags, and a recommended action, letting you approve confidently, not conservatively.

Python
POST /v1/counterparties/score
# Python example
import httpx

client = httpx.Client(
    base_url="https://api.provd.io",
    headers={"Authorization": f"Bearer {PROVD_API_KEY}"}
)

response = client.post("/v1/counterparties/score", json={
    "wallet_address": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
    "phone_hash": "sha256:a3f8c2d4e5b6...",
    "payment_rail": "mpesa",
    "country": "KE",
    "chain": "celo",
    "context": {
        "trade_type": "p2p_sell",
        "amount_usd": 500,
        "desk_id": "ke-p2p-desk-1"
    }
})

score = response.json()
print(f"Counterparty Score: {score['counterparty_score']}")
print(f"Risk Level:  {score['risk_level']}")
print(f"Flags:       {score['risk_flags']}")
print(f"Action:      {score['recommended_action']}")
Deployment

Start with one workflow. Scale across every corridor.

Provd integrates at the point of approval, one endpoint, no pipeline rebuild. Start with a single desk or corridor and expand as your volume and partner network grow.

Pilot / Early Access
Early access
Free or low-cost
  • Score counterparties in one live approval workflow
  • Validate precision against your existing thresholds
  • Measure the trades you were blocking that you shouldn't have been
  • Available to design partners and early evaluators
Read quickstart
Starter
Counterparty scoring
$199–$399/mo
  • One API call per trade, before release
  • Score, risk level, reason flags, and recommended action
  • Single desk, corridor, or approval flow
  • For operators ready to move from manual review to precision scoring
View API reference
Growth / Enterprise
Operations and network intelligence
$999–$1,500/mo · Custom
  • Full review and dispute workflow support
  • Coverage across multiple desks, rails, and markets
  • Partner network intelligence, contribute and consume shared signals
  • Enterprise onboarding, governance alignment, and custom terms
Talk to sales
AUDITABILITY
Every approval decision is explainable.
Provd logs the signals behind every score. Your risk and operations teams can review exactly why a counterparty was approved, flagged, or held, making every decision auditable, defensible, and improvable.
Risk reviewCase evidenceOperator decisionsInternal audit
DATA HANDLING
  • Identifiers are hashed client-side before leaving your environment.
  • Network signals are shared without any raw PII crossing platform boundaries.
  • Aggregated intelligence stays separated from user-facing application data.
  • Provd sees patterns, never personal data.

See what your current thresholds are missing.

Open the playground to run a live counterparty score, or read the quickstart to integrate Provd into your first approval workflow in under an hour.