Connect stc pay BH wallet, card and remittance data to your stack — under a CBB-aligned consent model
stc pay BH is a Central Bank of Bahrain-licensed Ancillary Services Provider that processed more than 30 million transactions worth over BHD 1 billion in 2025 across local Fawri/Fawri+ transfers, wallet-to-wallet payments, prepaid Mastercard cards and remittances spanning 60+ corridors. We deliver authorized OpenBanking-style APIs and runnable source code that surface every structured record the user already sees in the app — balances, transfers, statements, card spend, cashback events and salary disbursements — into your reconciliation, ERP or analytics stack.
What we deliver
Deliverables checklist
- OpenAPI 3.1 specification covering auth, balance, statement, transfer initiation and remittance status
- Protocol analysis report — OAuth + OTP login, device-binding, header signing and TLS pinning behaviour
- Runnable Python and Node.js reference clients for login, statement export and Fawri+ initiation
- Postman collection plus pytest/Jest test harness with Bahraini-Dinar (BHD) edge cases
- Compliance pack — CBB Open Banking checklist, consent text templates and 12-month retention policy
Engagement & pricing
- Source code delivery from USD 300 — pay only after you accept the build
- Pay-per-call hosted endpoints — no upfront fee, billed on successful API responses
- NDA & data-residency options for regulated banks, exchange houses and ERP vendors
- Optional sandbox seeded with synthetic stc pay BH-shaped fixtures (no live PII)
- Included: 30 days of bug-fix support and one schema-drift refresh
Data available for integration
Each row below maps a real surface inside the stc pay BH app to a structured payload that we can deliver. Fields are derived from the public app description, in-app screens and the CBB Open Banking technical specification, then normalised into JSON for downstream consumption.
| Data type | Source surface | Granularity | Typical use |
|---|---|---|---|
| Wallet balance | Home tab → Account widget | Real-time, BHD with 3-decimal precision | Cash-position dashboards, treasury reconciliation |
| Card transactions | Cards → Platinum/Elite/Elite Metal statement | Per-authorisation, MCC, FX, cashback % | Expense reporting, cashback accrual, fraud signals |
| Fawri / Fawri+ transfers | Local Transfers → Bank list | Per-transfer, IBAN, BIC, reference, status | Bank reconciliation, supplier payment matching |
| stc pay P2P transfers | Send → stc pay number | Per-transaction, instant, zero-fee | Customer support tooling, refund automation |
| International remittances | Send Abroad → Corridor & rail | Per-corridor (60+), FX rate, fee, MTCN | Compliance/AML reviews, corridor margin analytics |
| Bill payments | Bills & Payments → Biller list | Per-bill, telecom + utility + gift card | Recurring-bill insights, cash-flow forecasting |
| Salary disbursements | Business → WPS Salary Transfer | Bulk file, employee-level, retry status | HR / payroll ERP sync, WPS audit logs |
| Offers & cashback events | Offers tab | Per-event, merchant, % cashback | Loyalty programme attribution, marketing ROI |
Typical integration scenarios
1 · Corporate treasury reconciliation
A Manama-based trading group operates 14 stc pay business wallets to pay regional vendors. We expose the /wallet/balance and /wallet/statement endpoints and stream day-end JSON into Oracle NetSuite, mapping each Fawri+ outflow to the supplier ledger. The OpenFinance pattern lets the treasury team close books without manual CSV exports from the app.
2 · Cross-border remittance dashboards
An exchange house aggregates outbound flows across Mastercard Move, Terra Pay and the new Alipay corridor. Our remittance API returns FX rate, corridor fee and end-state per transfer; the partner builds a CBB Rule Book-aligned dashboard that monitors corridor margin and AML triggers in near real time.
3 · WPS payroll ERP sync
A logistics firm with 380 employees pushes monthly salaries through stc pay's WPS-compliant payroll service. The /payroll/batch endpoint accepts the same CSV the HR team uploads in-app, returns a batch ID, and emits webhooks for per-employee success/failure — fully PISP-style under the CBB Open Banking Framework.
4 · Fintech cashback aggregator
A Bahraini personal-finance app surfaces stc pay's 2/3/4% non-BHD card cashback alongside other GCC wallets. Our /cards/cashback read endpoint feeds normalised cashback events with merchant, MCC and award timestamp so the aggregator computes effective yield per card tier.
5 · KYC & risk control sync
A regulated lender consumes stc pay statement and remittance signals to score thin-file applicants under the CBB consumer-credit rules. We expose 12-month transaction histories and a derived cash_inflow_volatility field so risk models stay within the consent boundary set by the customer.
Technical implementation
Three short snippets below show the contract shape we typically ship: a customer login that mirrors stc pay's OTP flow, a statement export that returns a paginated wallet ledger, and a webhook for card-spend cashback events. All endpoints sit behind mutual TLS with HMAC-signed headers similar to the patterns documented for stc pay's payment-gateway acquirer integrations.
API 1 — Customer login (OAuth + OTP)
POST /api/v1/stcpay-bh/auth/login
Content-Type: application/json
X-Client-Signature: HMAC-SHA256(...)
{
"msisdn": "+9733xxxxxxx",
"device_id": "a3f1-...-9c2e",
"otp_channel": "sms"
}
200 OK
{
"session_id": "sess_01HZK...",
"challenge": "otp_required",
"expires_in": 90
}
API 2 — Wallet statement export
POST /api/v1/stcpay-bh/wallet/statement
Authorization: Bearer <ACCESS_TOKEN>
{
"wallet_id": "stcp_973xxxxxxx",
"from_date": "2026-04-01",
"to_date": "2026-04-30",
"type": ["FAWRI_PLUS","P2P","CARD","REMIT"],
"page": 1, "page_size": 100
}
Response (truncated):
{
"currency": "BHD",
"balance": "182.450",
"items": [
{"id":"txn_01H...","ts":"2026-04-21T08:14:11Z",
"type":"FAWRI_PLUS","amount":"-25.000",
"to_iban":"BH67BMAG00001299123456",
"ref":"FWP-Q31S","status":"settled"}
],
"next_page": null
}
API 3 — Card cashback webhook
POST https://your-app.example/webhooks/stcpay-cashback
X-Stcpay-Event: card.cashback.awarded
X-Stcpay-Signature: t=1714...,v1=...
{
"event_id": "evt_2j0L...",
"card_tier": "elite_metal",
"txn_id": "txn_01H...",
"merchant": "Apple Online",
"mcc": "5732",
"fx_amount": {"value":"129.00","currency":"USD"},
"cashback": {"value":"5.160","currency":"BHD","rate":"0.04"}
}
// Recommended: idempotent handler, 5xx triggers retry with jitter.
Compliance & privacy
Bahrain-specific regulation
Every delivery is mapped to the CBB Bahrain Open Banking Framework, which has been authoritative since October 2020 and was amended on 1 September 2024 to require explicit customer consent, AISP/PISP licensing, API performance reporting and disclosures by service providers. We also reference Bahrain's Personal Data Protection Law (PDPL, Law No. 30 of 2018) for storage, retention and cross-border transfer of stc pay user data.
Operational guardrails
- Authorised access only — customer or merchant-issued credentials, never scraped
- Tokens kept in the client tenant; we never persist long-lived stc pay secrets server-side
- Consent journal & revocation API per the CBB 2024 amendment
- Logging compatible with WPS audit and AML transaction monitoring
- Optional GDPR / PSD2 mapping when EU-based parties are involved
Data flow / architecture
A typical pipeline keeps the stc pay BH client untouched while exposing a clean integration surface to the partner system.
- stc pay BH mobile client — original Android/iOS app continues to run on the user's device, signed with stc pay BH's certificate.
- Protocol-aware ingestion gateway — our reference deployment terminates OAuth + OTP, refreshes session tokens, and normalises payloads into a stable JSON schema.
- Storage & consent ledger — encrypted store (PostgreSQL or your data lake) holding statements, transfers and cashback events alongside the consent record per CBB rules.
- Partner API / analytics output — REST endpoints, webhooks and CSV/PDF exports feed into ERP, BI, AML or KYC systems with row-level audit and replay.
Market positioning & user profile
stc pay BH serves both Bahraini residents and the country's large expatriate workforce, with an Android-first install base on Google Play (package com.vivacash.sadad) and a parallel iOS build on the App Store. Roughly 60% of Bahrain's population already prefers cashless payments, contactless card transactions grew from 31.9 million in 2020 to 168.9 million in 2024, and stc pay sits in the same top-tier wallet bracket as BenefitPay and Max Wallet by Credimax. On the corporate side, more than 100 SMEs and enterprises run WPS-compliant payroll through stc pay BH, which makes the integration story relevant for HR-tech, ERP vendors, exchange houses and regional banks operating across the Bahrain–Saudi–UAE corridor.
Screenshots
Tap any thumbnail for a full-resolution view. Screens illustrate where the integration data is captured inside the live stc pay BH app.
Similar apps & integration landscape
Teams that integrate stc pay BH typically need a unified view across the wider GCC and South-Asian wallet ecosystem. The apps below appear in the same searches and category as stc pay BH; we treat them as part of the integration landscape rather than competitors.
BenefitPay
Bahrain's national wallet operated by BENEFIT Company, handling roughly 85% of EFTS volume. Customers who hold both wallets often need consolidated Fawri+ ledgers across BenefitPay and stc pay BH.
BPay (Arab Financial Services)
Multi-purpose digital wallet for consumers, merchants and corporates. Pairs naturally with stc pay BH for merchants accepting both rails who want a single settlement export.
Max Wallet by Credimax
Card-issuer-driven wallet from Credimax. Cardholders frequently use Max Wallet alongside stc pay BH for cashback stacking, so card-spend APIs are commonly merged.
BFC Pay
BFC's wallet specialising in remittance pricing. A natural reference point when benchmarking stc pay BH's 60+ corridor remittance API against alternatives.
Tarabut
Regional account-aggregation platform built on the CBB Open Banking Framework. Useful when partners want bank-account context to sit next to stc pay wallet flows.
PayTabs
Bahrain-headquartered acquirer / payment gateway. Merchants reconciling PayTabs settlements alongside stc pay BH consumer-side data benefit from a shared schema.
urpay
Saudi wallet from STC Group's sister entity. Cross-border travellers between Saudi and Bahrain often hold urpay and stc pay BH together for combined statement views.
mada Pay
Saudi national-scheme mobile payment. Useful when a merchant accepts both mada Pay and stc pay BH and wants unified reconciliation across the GCC.
SNB QuickPay
Saudi National Bank's instant-pay product. Adjacent to stc pay BH for inbound Saudi-to-Bahrain remittance flows captured in the same dashboard.
Apple Pay & Google Pay (Bahrain)
Tokenised card rails layered on top of stc pay BH cards. Apple Pay and Google Pay receipts often arrive separately and can be merged with stc pay card transaction APIs for a single cashback view.
About us
OpenFinance Lab is an independent studio specialising in mobile-app interface integration and authorised API delivery for fintech, e-commerce, OTA and OTT clients. Our team has shipped Open Banking, UPI, Fawri+ and cross-border remittance integrations for banks, exchange houses and SaaS platforms, and we are familiar with CBB, SAMA, CBUAE and PSD2 expectations.
- Protocol analysis, OpenAPI design and language-native SDKs (Python, Node.js, Go)
- Reverse engineering for auth chains, header signing and TLS pinning
- Delivery includes runnable code, OpenAPI, Postman, tests and docs
- Source code delivery from USD 300 — pay only after acceptance
- Pay-per-call hosted endpoints with usage-based billing, no upfront fee
Contact
Send us your stc pay BH integration scope (read endpoints, transfer initiation, payroll, remittance, etc.) and any sandbox or merchant credentials you already hold. We will reply with a fixed-price quote and timeline.
NDAs available on request. We do not store or resell user data and cannot bypass Central Bank-mandated controls.
Engagement workflow
- Scope confirmation — pick the data surfaces you need (balance, statement, Fawri+, remittance, payroll).
- Protocol analysis & OpenAPI design (2–5 business days).
- Build, sandbox validation and consent-journal wiring (3–8 business days).
- Docs, Postman collection, tests and CBB-aligned compliance pack (1–2 business days).
- Acceptance & payment — first delivery typically 5–15 business days end-to-end.
FAQ
Which stc pay BH data can you actually surface through APIs?
Is the integration aligned with the Central Bank of Bahrain Open Banking Framework?
How long does delivery take and what does it cost?
Do you store user credentials or transaction data?
📱 Original app overview (appendix)
stc pay BH (package com.vivacash.sadad) is the mobile wallet operated by stc pay Bahrain B.S.C. (Closed) and stc pay Bahrain Remittances B.S.C. (Closed), licensed by the Central Bank of Bahrain as an Ancillary Services Provider and Money Changer respectively. The official tagline is "Most rewarding way to pay! One app to send, spend and save smarter."
- stc pay Cards — instantly issued in-app, contactless via Apple Pay and Tap & Go, security controls, worldwide acceptance and cashback on every purchase (Platinum, Elite, Elite Metal tiers with 2% / 3% / 4% on non-BHD spend).
- International transfers — fast online transfers to 20+ countries with competitive rates, sending to bank accounts, cash pickup locations and mobile wallets across 60+ corridors via Mastercard Move, Hello Paisa, Terra Pay, Ria, EzRemit and Alipay.
- Local transfers — Fawri/Fawri+ transfers to any Bahraini bank in a few steps, plus instant zero-fee transfers to any stc pay number.
- Bills & payments — pay telecom and utility bills, buy digital gift cards and more without queues.
- Salary transfers — WPS-compliant payroll for companies, with scheduling and tracking; over 100 corporates already onboarded.
- Offers & promotions — cashback, discounts and prize draws.
Recent milestones include the 2025 launch of the Alipay corridor (a first for Bahrain), processing of more than 30 million transactions worth over BHD 1 billion in 2025, and a publicly announced 2026 plan for regional expansion and AI-powered personalisation.