Dofied API integration services (B2B cash receipts & doPay)

Deliverables checklist

• OpenAPI / Swagger specification for every exposed Dofied endpoint
• Protocol report covering login, token refresh, receipt POST, invoice GET, and doPay webhook
• Runnable source for receipt-history and supplier-invoice APIs (Python, Node.js, or Go)
• Excel / JSON / PDF export pipelines for daily collection reports
• Automated tests, replay fixtures, and Postman collection
• Compliance guidance referencing the Iraq Electronic Payment Services Law (5-year record retention, AML reporting fields)

API example: receipt history (pseudocode)

POST /api/v1/dofied/receipts.list
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "representative_id": "rep_30421",
  "client_id": null,
  "from_date": "2026-03-01",
  "to_date":   "2026-03-31",
  "method":    ["cash", "doPay"],
  "page":      1,
  "page_size": 100
}

200 OK
{
  "page": 1,
  "total": 482,
  "items": [
    {
      "receipt_id": "rcpt_8821",
      "invoice_ref": "INV-2026-00471",
      "client_id":   "clt_9120",
      "amount_iqd":  1250000,
      "method":      "cash",
      "collected_at":"2026-03-04T09:14:22+03:00",
      "rep_id":      "rep_30421",
      "geo":         {"lat": 33.31, "lng": 44.36}
    }
  ]
}

API example: doPay webhook bridge

POST /webhook/dofied/dopay
X-Dofied-Signature: sha256=...

{
  "event":       "payment.captured",
  "provider":    "ZainCash",
  "receipt_id":  "rcpt_8842",
  "amount_iqd":  500000,
  "settled_at":  "2026-03-04T11:02:08+03:00",
  "status":      "captured",
  "auth_ref":    "ZC-9930-AABC"
}

→ Verify HMAC, idempotency-check receipt_id, push to ERP staging.
→ On failure: 5xx + retry; we ship a dead-letter queue spec with the SDK.

API example: supplier invoice sync (pseudocode)

GET /api/v1/dofied/invoices?supplier_id=sup_77&status=open
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "items": [
    {
      "invoice_id":   "INV-2026-00471",
      "supplier_id":  "sup_77",
      "client_id":    "clt_9120",
      "issued_at":    "2026-02-22",
      "due_at":       "2026-03-24",
      "amount_iqd":   1750000,
      "balance_iqd":  500000,
      "status":       "partial"
    }
  ]
}

1. Daily AR posting into ERP

A wholesale distributor runs Dofied across 40 sales reps. Every evening our integration calls receipts.list for the day, joins receipts to the matching invoice_ref via invoices?status=open, and posts a single AR journal batch into SAP B1 or Odoo. Cash and doPay are tagged with separate sub-ledgers.

OpenData mapping: Dofied receipt feed becomes the canonical "collection event" entity — equivalent to an OpenBanking transactions resource scoped to the merchant's own collections.

2. Real-time treasury dashboard

Finance wants live cash-on-hand by representative. We subscribe to the doPay webhook and poll receipts every 5 minutes; data lands in a Postgres staging table and powers a Metabase board showing cash held in the field, expected bank deposit by EOD, and exception receipts (no matching invoice).

OpenData mapping: Mirrors an OpenFinance "balances" resource at the representative level — useful where banks do not yet expose merchant cash-deposit feeds.

3. AML & structuring detection

Under Iraq's 2024 Electronic Payment Services Law, providers must keep records 5 years and run AML screening. We feed Dofied receipts into a rules engine that flags split deposits (e.g., five 9.5M IQD receipts from one client in 24 h), unusual geo, or off-route collections.

OpenData mapping: Authorised data extraction with provenance — every flagged receipt links back to the original Dofied record for examiner review.

4. Supplier portal & invoice presentment

A FMCG supplier wants its retailers to log into a portal and see invoices already mirrored by Dofied. We expose an invoices.byClient API and a download endpoint that produces a stamped PDF receipt mirroring the in-app print/upload feature.

OpenData mapping: The same B2B presentment pattern that PSD2-style OpenBanking applies to retail accounts.

5. Sales-rep performance & route optimisation

Combining receipt geo, timestamps, and route assignments yields per-rep collection velocity, average dwell time per client, and missed-stop alerts. Output goes to a BI layer (BigQuery + Looker Studio) and a route-planning tool that re-sequences tomorrow's runs.

OpenData mapping: Movement & activity data extraction — analogous to logistics OpenData feeds, scoped strictly to the merchant's own field force.

About us

We are an independent technical studio focused on App interface integration and authorised API integration. Our engineers come from payment gateways, banking middleware, and protocol-analysis backgrounds, with multi-year experience across MENA, South Asia, and European fintech. For a project like Dofied that means we already know the shape of CBI-supervised data, the realities of dual-app (rep + client) flows, and the operational habits of Iraqi field-sales teams.

• Protocol analysis & authorised data extraction (no credential cracking, no detection evasion)
• API design, OpenAPI documentation, SDKs in Python / Node.js / Go
• ERP, BI, and AML connector engineering
• Cross-border treasury and reconciliation pipelines
• Source code delivery from $300 — runnable code plus documentation; pay after delivery
• Pay-per-call API billing — access our hosted endpoints, no upfront fee

Contact

Send us your target tenant scope (which screens / data) and we will scope the Dofied integration in writing within one business day:

Contact page

For NDAs, sandbox onboarding, or compliance documentation, mention "Dofied" in the subject line and we will route accordingly.

Engagement workflow

1. Scope confirmation — list the Dofied screens / data classes in play (receipts, invoices, doPay, master data).
2. Authorisation — we collect written sign-off from the tenant owner (supplier / distributor) and any required CBI-related notices.
3. Protocol analysis & API design (2–5 business days).
4. Build, internal validation, and replay-test against a real tenant snapshot (3–8 business days).
5. Docs, Postman collection, and handover (1–2 business days).
6. Typical first delivery: 5–15 business days; complex cross-border or multi-tenant rollouts can extend.

FAQ

What do you need from me to start?

Can you also handle Dofied Clients (the companion app)?

How do you handle Iraq's 5-year retention rule?

Do you charge upfront?