Unimoni Qatar API integration & OpenData services

1. Bank Account Transfer API

Outbound remittance to a beneficiary IBAN/account number across Unimoni's network of more than 150 correspondent banks. We expose POST /transfers/bank with sender token, beneficiary block and amount, plus a webhook that mirrors the in-app status timeline (initiated → funded → in-transit → credited / failed). Used by payroll providers to reconcile bulk salary remittances every cycle.

2. Cash PickUp API

Generate and track cash-pickup transfers redeemable across the XPRESS Money / partner agent network. The endpoint returns a reference number, expected payout location and KYC requirements for the receiver. Useful for HR teams handling unbanked beneficiaries and for NGO disbursement portals.

3. Mobile Wallet Transfer API

Push funds into wallets such as bKash, Easypaisa, M-Pesa-style rails and similar mobile money systems available through Unimoni's payout partners. The API surfaces the wallet provider list, eligibility per corridor and final settlement status — ideal for gig-economy platforms paying contractors abroad.

4. FX Rate Calculator API

Read the same multi-currency rates the in-app Currency Exchange Rate Calculator displays. GET /fx/quote?from=QAR&to=INR&amount=5000 returns the indicative rate, payout amount and rate timestamp; downstream rate-monitor jobs poll it on a schedule and write to BI dashboards.

5. Transfer History & Statement Export

Paginated transaction history with date-range and rail filters, exportable as JSON, CSV or a signed PDF statement. Used by accountants for monthly closing and by individual senders who need a tax-style record of remittances out of Qatar.

6. Branch & Agent Locator Feed

Structured directory of Unimoni branches and partner agents (Doha Festival City, Al Khor Mall and other locations), with geo-coordinates, opening hours and offered services. Consumed by mall-discovery apps, HR onboarding portals for new expats, and B2B partner-routing logic.

Scenario A — Payroll vendor reconciles bulk remittances

An HR-tech vendor running monthly salary disbursements for blue-collar workers in Qatar needs to confirm that every salary transfer succeeded. We wire the transfer-history API into their reconciliation engine. Each pay-cycle, a job calls GET /transfers?from=2026-04-01&to=2026-04-30&rail=BANK,CASH,WALLET, joins the response with the internal payroll ledger, and flags any non-CREDITED state for ops follow-up. Maps to OpenFinance "account information" access patterns.

Scenario B — Treasury dashboard tracking QAR-INR corridor

A South-Asian SME with Qatar-based subsidiaries polls GET /fx/quote every five minutes for QAR→INR and QAR→PHP, stores the curve in BigQuery, and triggers a Slack alert when the rate beats a threshold. This complements OpenBanking treasury feeds with one of the corridors most relevant for GCC outbound flow.

Scenario C — NGO field-disbursement workflow

An NGO disbursing emergency cash to unbanked beneficiaries uses the cash-pickup endpoint to issue a reference number per recipient, then watches the webhook for the "PICKED_UP" event. Each redemption is mapped to a case file with timestamp, payout city and partner-agent code, satisfying donor reporting and AML/CFT obligations under Qatar Law No. 20 of 2019.

Scenario D — Compliance-grade statement export

A migrant worker preparing residency / loan documents needs a clean PDF statement of one year of remittances. The signed PDF endpoint produces a Unimoni-branded statement with the Qatar Central Bank licence note, listing every transfer, fee, FX and payout corridor — a use case that mirrors the OpenBanking "statement download" pattern but for outbound remittance.

Scenario E — Branch / agent feed for a mall-discovery app

A Qatar lifestyle app surfacing services at Doha Festival City, Al Khor Mall and other Unimoni locations consumes GET /branches?near=lat,lng&service=remittance and renders pins on a map with hours and offered rails. New branch openings (such as the November 2023 Al Khor Mall launch) flow through automatically without engineering changes.

1) Account login & token refresh

// Sender authentication (pseudocode)
POST /api/v1/unimoni-qa/auth/login
Content-Type: application/json

{
  "identifier": "+9745xxxxxxx",
  "credential": "<mpin_or_otp>",
  "device_id": "io.thoughtbox.unimoni:DEVICE_HASH"
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_...",
  "expires_in": 1800,
  "kyc_level": "FULL",
  "remittance_limit_qar": 50000
}

The login wrapper mirrors the app's authorization (OTP / MPIN), validates session against Qatar's E-KYC Regulation tiers, and returns a refreshable bearer token usable across the rest of the API surface.

2) Transfer history (statement query)

// Fetch outbound remittance history
POST /api/v1/unimoni-qa/transactions
Authorization: Bearer <ACCESS_TOKEN>

{
  "from_date": "2026-01-01",
  "to_date": "2026-04-29",
  "rail": ["BANK", "CASH", "WALLET"],
  "status": ["CREDITED", "IN_TRANSIT", "FAILED"],
  "page": 1, "page_size": 50
}

200 OK
{
  "items": [{
    "ref": "UQA2604291245",
    "sent_qar": 4500.00,
    "received": { "ccy": "INR", "amount": 102375.00 },
    "fx_rate": 22.75,
    "fee_qar": 18.00,
    "rail": "BANK",
    "beneficiary": { "name_mask": "R**** K****", "country": "IN" },
    "status": "CREDITED",
    "created_at": "2026-04-29T08:12:31Z"
  }],
  "page": 1, "total": 137
}

3) Status webhook

// Subscribed status update (server → your endpoint)
POST https://your-app.example.com/webhooks/unimoni
Content-Type: application/json
X-Unimoni-Signature: t=1714378351,v1=hex(hmac_sha256(body, secret))

{
  "event": "transfer.status_changed",
  "ref": "UQA2604291245",
  "old_status": "IN_TRANSIT",
  "new_status": "CREDITED",
  "rail": "BANK",
  "corridor": "QA-IN",
  "ts": "2026-04-29T08:46:02Z"
}

// On 5xx from your endpoint, retry with exponential backoff
// (1m, 5m, 30m, 2h, 12h) up to 24h.

Errors follow a normalised envelope ({"error_code": "RAIL_UNAVAILABLE", "retryable": true}) so consumers can branch on retryable vs terminal failures without guessing.

Deliverables checklist

• API specification (OpenAPI 3.1 / Swagger) covering login, transfers, FX, branches and webhooks
• Protocol & auth flow report for the Unimoni Qatar mobile app (token chain, signing, retry semantics)
• Runnable source code (Python, Node.js, or Go) with unit and integration tests
• Postman collection and example payloads for each endpoint
• Compliance brief: QCB, AML/CFT (Law No. 20/2019), Personal Data Privacy (Law No. 13/2016), E-KYC mapping
• Operational runbook: monitoring, alerting, incident response

Two engagement models

Source-code delivery — from $300. We hand over the runnable API source code and full documentation. Pay after delivery upon satisfaction. Best for teams who want to host the integration in-house and own the code.

Pay-per-call hosted API. Use our hosted endpoints and pay only for the calls you make. No upfront fee. Best for teams who prefer usage-based pricing and a managed runtime.

Use-case mapping

Tell us which downstream you are wiring to (NetSuite, SAP, Zoho, Looker, Metabase, in-house data lake, payroll engine, NGO case-management) and we will tailor the field mapping rather than ship a generic schema.

About us

We are an independent technical service studio specialising in mobile-app interface integration and authorized API integration. The team brings hands-on experience across mobile applications, remittance, payments and fintech in the GCC, South Asia and Europe. We have shipped protocol-analysis and OpenFinance-style integrations for banking, remittance, e-commerce, hotel and OTT-media apps.

• Remittance, digital banking, FX and cross-border clearing
• Enterprise API gateways, webhook fabrics, security review
• 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

Contact

For quotes, sandbox access requests or to submit your target app and requirements, open our contact page:

Contact page

Engagements are scoped under written authorization or against documented public/authorized APIs. NDAs available on request.

Engagement workflow

1. Scope confirmation: which Unimoni Qatar surfaces (login, transfer, FX, branch) and downstream consumers.
2. Protocol analysis & API design (2–5 business days).
3. Build, internal validation and security review (3–8 business days).
4. Documentation, samples, Postman collection and test cases (1–2 business days).
5. First delivery typically lands in 5–15 business days; third-party approvals may extend timelines.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Can you also cover similar apps?