manafa | منافع API integration services (SAMA debt crowdfunding · OpenFinance)

1. Investor account & KYC bridge

Programmatic registration, login token refresh, and a structured handoff for KYC artefacts (national ID, bank IBAN, declared income tier). Use case: a wealth-management dashboard onboards a client into manafa in the same flow that opens their main brokerage account, then mirrors the resulting investor ID into a unified CRM record.

2. Opportunity discovery API

Paginated list of currently open SME debt-crowdfunding opportunities with sector, tenor, target amount, profit rate, current funding progress, and remaining capacity. Use case: a robo-advisor matches each opportunity against client risk policy and surfaces a short-list inside the advisor's own app.

3. Subscription & cash-flow API

Create or read investor subscriptions, retrieve repayment schedules, reconcile distributions against expected cash-flow. Use case: a family-office accounting team imports daily distributions to close their cash book without manual entry.

4. Auto-Invest rule engine adapter

Configure Auto-Invest filters (sector, min rating, max ticket per opportunity, monthly cap), then receive webhook events when a rule fires. Use case: a treasury team caps total Saudi debt-crowdfunding exposure at SAR 250,000 per month across multiple platforms.

5. Statement & reporting export

Time-bounded statement extraction with categorisation (principal returned, profit, fees, withholding) and downloadable Excel/PDF/JSON. Use case: an external auditor generates a quarterly evidence pack for SAMA-aligned reporting.

6. Notification & event hub

Subscribe to lifecycle events: new opportunity published, allocation closed, repayment received, opportunity overdue. Use case: a Slack-native ops bot pings the portfolio manager whenever a tracked SME misses a scheduled installment.

Scenario A — Multi-platform Saudi crowdfunding portfolio dashboard

Business context: A Riyadh family office allocates capital across several SAMA-licensed crowdfunding platforms and needs a single performance view.

Data & APIs: manafa subscription list + repayment schedule + distribution events; combined with parallel feeds from peer platforms.

OpenFinance mapping: Treats manafa as an Account Information Service (AIS) source under the SAMA Open Banking pattern, normalizing balances and cash-flow into a shared schema.

Scenario B — Auto-Invest controlled by external risk engine

Business context: A wealth-tech startup wants to drive Auto-Invest decisions from its own model, not from manafa's built-in filters alone.

Data & APIs: Opportunity feed (read), Auto-Invest rule push, webhook callback for fired rules; risk score computed externally per opportunity.

OpenFinance mapping: Behaves as a Payment Initiation-style flow (PIS analogue), where the third party orchestrates the action and manafa executes it under recorded user consent.

Scenario C — Accounting / ERP cash-book reconciliation

Business context: An SME corporate treasury invests surplus working capital in short-term manafa opportunities and must reconcile inflows against the bank statement.

Data & APIs: Distribution events stream + statement export endpoint mapped to ERP journal lines (account 7210 "investment income", 1210 "principal returned").

OpenFinance mapping: Aligns with PDPL consent records by storing only the categorised cash-flow needed for the ledger, not the underlying investor profile.

Scenario D — Compliance & audit evidence pack

Business context: A licensed advisor must demonstrate to a regulator that a client's allocation respects exposure limits per issuer and per sector.

Data & APIs: Subscription records + opportunity metadata aggregated per period, signed PDF statement attached as evidence.

OpenFinance mapping: Generates an attested data extract; consent revocation under PDPL purges retained extracts on schedule.

Scenario E — Professional-investor eligibility automation

Business context: manafa's "upgrade to Professional Investor" pathway depends on SAMA criteria; an external onboarding stack wants to evaluate eligibility before nudging the user.

Data & APIs: Investor profile read + declared income / asset attestations + status callback when manafa accepts the uplift.

OpenFinance mapping: A consented identity-attribute exchange; the third party never stores raw documents, only a verified status flag.

1. Investor login & token refresh

POST /api/v1/manafa/auth/login
Content-Type: application/json

{
  "investor_ref": "INV-9F2A",
  "device_fingerprint": "<hash>",
  "consent_id": "csnt_2025_04_001"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rft_...",
  "expires_in": 1800,
  "scope": ["opportunities.read", "subscriptions.read", "autoinvest.write"]
}

2. Statement query (fetch monthly cash-flow)

GET /api/v1/manafa/statement?from=2026-03-01&to=2026-03-31
Authorization: Bearer <ACCESS_TOKEN>
X-Consent-Id: csnt_2025_04_001

200 OK
{
  "investor_ref": "INV-9F2A",
  "currency": "SAR",
  "events": [
    {"date":"2026-03-04","type":"profit","amount":182.50,"opportunity_id":"OP-7711"},
    {"date":"2026-03-04","type":"principal","amount":1250.00,"opportunity_id":"OP-7711"},
    {"date":"2026-03-18","type":"fee","amount":-36.50,"opportunity_id":"OP-7711"}
  ],
  "next_cursor": null
}

3. Auto-Invest webhook (rule fired)

POST https://your-app.example.com/hooks/manafa
X-Manafa-Signature: t=1714291200,v1=<hmac-sha256>
Content-Type: application/json

{
  "event": "autoinvest.executed",
  "rule_id": "ai_rule_88",
  "opportunity_id": "OP-9023",
  "amount_subscribed": 5000.00,
  "currency": "SAR",
  "timestamp": "2026-04-28T07:14:11Z"
}

// Verify HMAC, then idempotently upsert into your ledger
// keyed by (rule_id, opportunity_id, timestamp).

Deliverables checklist

• Authorization & protocol-analysis report (token chain, refresh, signature scheme)
• OpenAPI / Swagger specification for the manafa-shaped surface
• Runnable source code (Python / Node.js / Go) for login, opportunities, subscriptions, statements, Auto-Invest
• Webhook receiver template with HMAC verification and idempotency keys
• Test harness with fixtures for repayment schedules and distribution events
• Compliance pack: PDPL consent record templates, retention timers, revocation hook

Engagement workflow

1. Scope confirmation: which manafa flows you need (onboarding, portfolio, Auto-Invest, statements).
2. Protocol analysis & API design (2–5 business days, complexity-dependent).
3. Build & internal validation against fixtures (3–8 business days).
4. Documentation, sample clients, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; SAMA-sandbox approvals may extend timelines.

About our studio

We are an independent technical studio focused on App interface integration and authorized API integration. Team members come from banks, payment gateways, fintech platforms, and protocol-analysis backgrounds. We have shipped end-to-end integrations across financial, e-commerce, travel, and OTT apps, and we work day-to-day inside frameworks such as SAMA Open Banking, PSD2, UPI, and PDPL/GDPR.

• Protocol analysis, data extraction, and OpenData implementation
• Custom Python / Node.js / Go SDKs and test harnesses
• Full pipeline: protocol analysis → build → validation → compliance handover
• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted API and pay only per call, no upfront cost; ideal for teams that prefer usage-based pricing

Contact

To request a quote for the manafa | منافع app, or to submit your own target app and integration scope:

Open the contact page

Typical first response within one business day. NDA templates are available on request before sharing sensitive scope details.