(Sulfah) is a SAMA-licensed consumer microfinance platform operating in Saudi Arabia,
offering short-term personal financing from SAR 1,000 to SAR 25,000 with payback periods
of 3 to 18 months. Beyond borrowing, also runs a peer financing marketplace where
individuals fund other individuals and receive monthly returns — making it one of the few
Saudi fintech platforms that serves both borrowers and retail investors under one licence.
For developers and product teams building financial aggregation tools, lending analytics,
or personal finance apps in the Saudi market, accessing 's structured loan data is a
high-value integration challenge. The borrower's contract, installment schedule, profit
breakdown, and investor positions live in 's own systems — not in a bank — and
require an authorized interface integration path to reach, separate from SAMA Open Banking
AIS which only covers the linked bank account's cash movements.
OpenBanking Studio delivers exactly this integration: a runnable build covering the full
data surface, joined with SAMA AIS bank-side movements on a shared loan reference,
with an OpenAPI specification, protocol report, and automated tests included.
--------------------
SUPPORTED API FEATURES
--------------------
The API integration built by OpenBanking Studio surfaces the following data domains
from the app's real product screens and pricing infrastructure:
Loan application data — amount (SAR 1,000–25,000), tenure (3–18 months), and
application status as it moves through approval stages
Loan contract and T&C acceptance — e-signed contract records with accepted
terms version and timestamp, suitable for compliance archiving and audit trails
Cost-of-credit breakdown — Sharia-compliant pricing fields captured exactly as
computes them: processing fee (1%), VAT on fee (15%), profit amount, APR
(max stated 89.59%), and total repayment per loan
Installment schedule — per-installment records including due date, amount, and
payment status (DUE / SCHEDULED / PAID / LATE) across the full repayment timeline
Disbursement event data — funding timestamp and bank account reference matched
to the borrower's linked account via SAMA AIS consent
Borrower profile and eligibility flags — fully electronic onboarding data with
no salary transfer or guarantor requirement, supporting KYC reuse and pre-qualification
Marketplace investor positions — per-investment records, expected monthly returns,
and repayment status of funded loans for the investor side of the platform
------------
Integration Routes
------------
Three authorized access paths are supported, combined to match each use case:
Authorized interface integration of the app — the primary route for all
loan ledger, contract, cost-of-credit, and investor position data
SAMA Open Banking AIS consent — regulated bank-side consent for disbursement
credits and monthly installment debits, joined to the app data on a shared
loan reference
User-consented session export — narrowest scope, useful for one-off
reconciliation or single-account history pulls
--------------------
USE CASES & APPLICATIONS
--------------------
[1] Lending Marketplace Aggregation
Pull a consenting borrower's contract and full installment schedule
Show total indebtedness across multiple Saudi lenders before offering refinance
Compare contracted APR and cost-of-credit across peer platforms
Enable affordability pre-checks using live schedule and repayment data
[2] Personal Finance and Cash-Flow Management
Reconcile disbursement credits against the borrower's bank feed
Correctly categorize monthly installment debits in budget tracking views
Display the loan's full remaining schedule inside a unified financial dashboard
Trigger cash-flow alerts when upcoming installment dates approach
[3] Investor Portfolio Aggregation
Aggregate a marketplace lender's positions alongside other holdings
Track expected monthly returns and actual repayment status per funded loan
Build a single portfolio-level number across Saudi fintech investment products
Monitor the health of funded loan cohorts by status distribution
[4] Compliance, Audit, and Contract Lifecycle Management
Archive e-signed contracts with accepted terms version and acceptance timestamp
Maintain a full cost-of-credit record — fee, VAT, profit, APR — per loan
Support PDPL-compliant data handling with consent scope and timestamp logging
Sync contract lifecycle state for regulatory reporting and audit readiness
[5] Collections, Dunning, and Receivables Analytics
Pull per-installment due dates and amounts for collections workflow triggers
Flag LATE-status installments for dunning logic without manual reconciliation
Forecast cash inflows from active loan books using the full schedule object
Join bank-side debit data with the contracted schedule to verify settlement
--------------------
BENEFITS & ADVANTAGES
--------------------
Complete loan ledger access — not just bank movements
Both the app-side contract and schedule and the bank-side cash events are
delivered as one joined object, eliminating the manual alignment work that
arises when two data feeds are consumed separately.
Sharia-compliant pricing modelled correctly
Processing fee, VAT on fee, and profit are mapped into a normalized
cost-of-credit schema — never mis-labelled as conventional interest — so
downstream systems handle Murabaha-style pricing without data model errors.
Figures captured as computes them
The cost block (principal, APR, installment, total repayment) is derived
from the app's own outputs, not recomputed independently, so consumers see
the borrower's actual contracted figures.
Dual-side integration under one loan reference
Interface integration handles the lender's systems; SAMA AIS consent handles
the bank account — both keyed to the same loan identifier so reconciliation
is one lookup, not a cross-feed join.
Investor marketplace data included in the same spec
The financing marketplace positions, expected returns, and funded-loan
repayment status are a second object set in the same OpenAPI specification,
covered by the same authorized session route.
Consent and PDPL compliance built into the design
Every access is authorized and logged with scope and timestamp; consent
expiry and revocation are handled in the sync design rather than discovered
when a feed goes quiet.
Maintenance coverage for front-end changes
The app ships updates regularly; the engagement includes scheduled checks
that re-validate captured flows whenever updates its client, so the
integration does not silently degrade between delivery and production use.
OpenBanking Studio offers two engagement models for the integration:
Source Delivery — from $300
Receive the full runnable source code, OpenAPI/Swagger specification covering
all loan and investor objects, protocol and auth-flow report, automated tests
for cost-of-credit math, and interface documentation. Payment is due after
delivery, once the build runs as described. Typical cycle: one to two weeks.
Pay-Per-Call Hosted
OpenBanking Studio hosts the endpoints; you pay per API call with nothing
upfront. Access the same data surfaces — loan application, contract,
cost-of-credit, installment schedule, disbursement event, and investor
positions — without managing the integration infrastructure.
Both paths include the consenting test account setup and access arrangement as
part of the engagement, not as a prerequisite before work begins.
(Sulfah) holds some of the most detailed per-borrower financial state in the
Saudi consumer microfinance market: Sharia-compliant cost-of-credit breakdowns,
e-signed contracts, full installment schedules, and a peer financing marketplace
that serves retail investors alongside borrowers — all under a SAMA consumer
microfinance licence and PDPL-governed data access rules.
For product teams building lending aggregators, personal finance tools, investor
dashboards, or compliance infrastructure in the Saudi market, the integration
from OpenBanking Studio delivers the complete data surface through an authorized,
consent-based path, joined with SAMA Open Banking AIS bank-side movements, with
no guesswork about field names or pricing logic.
To scope your integration and start the engagement, visit:
https://openbankingstudio.com/.html
Tell us the app and what you need from its data. The access path, consenting test
account, and authorizations are arranged as part of the work. Delivery in one to
two weeks. Payment from $300 only after it runs as described.
--------------------
2026 OpenBanking Studio — authorized app interface integration and API delivery
and Sulfah are marks of their owner. This is an independent integration
assessment, not affiliated with or endorsed by the app.
--------------------