Dama Mobile API integration (cannabis OpenBanking / LeafLink)

Authentication & session layer

We reproduce Dama Mobile's two-factor and biometric login flow so your backend can obtain a valid user session without shipping the mobile app itself. Auth tokens are refreshed on schedule, and step-up challenges (OTP, device fingerprint) are surfaced as explicit API events rather than hidden inside a WebView.

Used by operators who run reconciliation jobs overnight or who need service-account-style access for their ERP.

Transaction history API

Paginated access to the full transaction ledger per account, with filters for posting date, status, counterparty, memo and transaction type (ACH, wire, mobile deposit, cash pickup, internal transfer). Output ships as normalized JSON, CSV or an Excel bundle for month-end close.

Concrete use: automated reconciliation against dispensary POS and METRC seed-to-sale data.

Balance & multi-account sync

Real-time balance snapshots and historical closing balances per account and per partner bank. Multi-entity groups (holdco, cultivator, retail LLC) are returned as a tree so operators can feed consolidated cash-position reports into Treasury systems.

Concrete use: daily 15-minute cash-position refresh for CFO dashboards.

Mobile check deposit (RDC)

Programmatic submission of check front/back images with MICR extraction, amount validation and funds-availability tracking. Mirrors the in-app RDC flow including duplicate detection and the $100,000 electronic deposit ceiling referenced in Dama's public guidance.

Concrete use: scanning station integrations at retail counters that push deposits into Dama in near real time.

Transfers & client payment requests

Endpoints for intra-account transfers, approved external partner ACH, and outbound payment requests to clients with memo lines and due dates. Includes webhook events for approval, settlement and return codes so your AR system can auto-apply receipts.

Concrete use: wholesale cannabis operators collecting from retailers on 15/30-day terms.

Cash pickup scheduling

Create, amend and cancel armored-courier pickups; inspect pickup windows, driver ETA, and deposit receipts. Returns event-style records that align with BSA/SAR documentation requirements for cash-intensive MRBs.

Concrete use: dispatcher tools that optimize pickup routes across multiple retail locations.

1 · Dispensary daily close reconciliation

Business context: a multi-location dispensary group needs to reconcile till counts against Dama deposits and ACH receipts at end of day.

Data & APIs: transaction history + cash pickup orders + mobile check deposit records, filtered by business date.

OpenFinance mapping: exposed as an ISO 20022-flavored /accounts/{id}/transactions endpoint so the group's accounting platform (QuickBooks, NetSuite, Sage Intacct) consumes it through the same schema it already uses for traditional banks.

2 · Wholesale AR and client payment requests

Business context: a cultivator invoicing retailers on 30-day terms wants automated reminders and cash application.

Data & APIs: client payment request creation, status webhooks, and transaction matching by memo/invoice number.

OpenFinance mapping: aligned with Request-to-Pay patterns emerging in US OpenBanking discussions, using webhook events for payment.request.created, .accepted, .settled.

3 · BSA / SAR supporting evidence

Business context: compliance teams supporting FinCEN 2014 marijuana-related SAR reporting need a defensible, time-stamped ledger for every MRB dollar.

Data & APIs: transactions with status and counterparty, cash pickup chain-of-custody, device & session metadata.

OpenFinance mapping: output is immutable and append-only, exported nightly to a write-once storage tier, consumable by the compliance team via signed download URLs.

4 · CFO treasury dashboard across partner banks

Business context: a holdco operates across OMB, First Option and Dart via Dama, plus one traditional bank, and wants a single live cash view.

Data & APIs: balance sync across all Dama accounts on a 15-minute cadence; normalized into a common account tree.

OpenFinance mapping: data is published via the same Apideck-style unified accounting/ERP API the Dama Financial platform already uses with its 30+ connector network, so it can be joined to Plaid or Finicity feeds for the traditional bank.

5 · Armored-courier operations integration

Business context: a cannabis operator with weekly cash pickups needs to feed Dama's cash logistics state into its own dispatch and insurance tools.

Data & APIs: create / amend / cancel cash pickup; poll pickup state; receive deposit-confirmation webhooks.

OpenFinance mapping: an event-sourced pipeline (pickup.scheduled, .in_transit, .deposited) so operations teams can alarm on SLA breaches.

Login & 2FA handshake

POST /api/v1/dama/session
Content-Type: application/json

{
  "username": "ops@dispensary-holdings.example",
  "password": "<hashed-client-side>",
  "device": { "id": "d-7f2c", "platform": "server-agent" },
  "mfa": { "channel": "totp", "code": "482913" }
}

// 200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_live_9f2...",
  "expires_in": 1800,
  "entities": [
    { "id": "ent_1001", "legal_name": "Green Leaf Retail LLC", "partner_bank": "OMB" },
    { "id": "ent_1002", "legal_name": "Green Leaf Cultivation LLC", "partner_bank": "Dart" }
  ]
}

Transaction statement query

GET /api/v1/dama/entities/ent_1001/transactions
  ?from=2026-03-01&to=2026-03-31&type=ACH,RDC,CASH_PICKUP
Authorization: Bearer <ACCESS_TOKEN>

// 200 OK
{
  "page": 1, "page_size": 100, "has_more": true,
  "items": [
    {
      "id": "txn_87a1",
      "posted_at": "2026-03-02T14:11:05Z",
      "amount": { "value": -12450.00, "currency": "USD" },
      "type": "ACH_OUT",
      "counterparty": "Pacific Glass Co",
      "memo": "INV-4823",
      "status": "SETTLED"
    }
  ]
}

Cash pickup scheduling

POST /api/v1/dama/cash-pickups
Authorization: Bearer <ACCESS_TOKEN>

{
  "entity_id": "ent_1001",
  "location_id": "loc_store_42",
  "requested_window": { "date": "2026-04-28", "slot": "10:00-12:00" },
  "declared_amount": { "value": 84200.00, "currency": "USD" },
  "denominations": { "100": 520, "20": 1600, "coin": 120.00 }
}

// 201 Created
{
  "pickup_id": "pk_5512",
  "state": "SCHEDULED",
  "courier_eta": "2026-04-28T10:35:00-07:00",
  "tracking_url": "/tracking/pk_5512"
}

// Webhook: pickup.deposited
{ "pickup_id": "pk_5512", "state": "DEPOSITED", "bank": "OMB", "deposit_slip": "ds_9921" }

Error handling & retry contract

All endpoints return structured errors: {"code":"MFA_REQUIRED","challenge_id":"ch_...","message":"Step-up required"}. Idempotency is enforced via Idempotency-Key on mutating routes so retries on network partitions never double-schedule a pickup or double-submit a check. Rate limits are exposed through X-RateLimit-* headers, and 5xx responses are retried with jittered exponential backoff in the supplied SDKs.

Abaca

Cannabis banking platform offering compliant accounts, lending and payments. Teams that also hold accounts with Abaca often need unified transaction exports aligned with Dama feeds.

Green Check

Compliance-focused software that sits between credit unions, community banks and cannabis operators. Data enrichment pairs naturally with Dama Mobile transaction integrations.

Hypur

Payments and banking technology used by financial institutions serving high-regulated sectors. Operators frequently reconcile Hypur-initiated ACH with Dama partner-bank statements.

CanPay

Debit-style app connected to a checking account and accepted at hundreds of dispensaries. Receipts flow into the same ledger that Dama Mobile reports on.

Payqwick

Nonbank financial provider for licensed cannabis operators, including cash pickup. Multi-vendor cash logistics benefit from a unified scheduling view alongside Dama's pickups.

Fincann

Advisory network that pairs cannabis operators with cannabis-friendly banks. Operators matched through Fincann are common adopters of Dama Mobile-style API integrations.

Paybotic

Florida-based cannabis payments and cash-access specialist. Reconciling Paybotic-settled batches against Dama transaction history is a frequent integration ask.

Confia

Cannabis banking platform whose customers LeafLink has been migrating onto the Dama Financial stack in 2025. Historical Confia data often needs blending with live Dama feeds.

Synctera (Cannabis Solution)

Banking-as-a-Service platform with a dedicated cannabis program. Operators exploring Synctera typically want parallel data schemas with Dama to keep reporting stable.

LeafLink Pay

LeafLink's own B2B marketplace payments layer, now closely tied to Dama Financial after the 2024 acquisition. Unified views of marketplace payments and Dama banking flows are a natural next step.

Deliverables checklist

• OpenAPI 3.1 specification covering auth, accounts, balances, transactions, deposits, transfers, payment requests and cash pickups
• Protocol & auth flow report (2FA, biometric, token lifecycle, device binding)
• Runnable source code in Python and Node.js; optional Go client
• Integration tests, fixture data, and a sandbox harness
• Compliance guidance: FinCEN 2014 guidance mapping, SAR support fields, data-minimization checklist
• Operational runbook: monitoring, token rotation, incident response

Engagement models

We work under NDA on request and can run a scoped pilot on a single Dama entity before rolling out across a multi-store operator.

Long-tail focus areas

About our studio

We are an independent technical studio focused on App interface integration and authorized API integration. Our team's backgrounds include core banking, payment gateways, mobile protocol analysis, and cloud platform engineering. We ship end-to-end APIs for fintech apps under strict security and compliance constraints, and we have specific experience with MRB-adjacent flows where auditability is as important as uptime.

• Protocol analysis and reverse engineering of mobile banking apps
• OpenAPI-first design with full typed SDKs in Python, Node.js and Go
• Compliance-aware pipelines (FinCEN guidance, CCPA/CPRA, PCI DSS scoping)
• Delivery of source code & documentation or a hosted pay-per-call API
• Transparent scoping: we decline tasks that would bypass an app's security controls

Contact

To request a quote for a Dama Mobile integration — or to submit a different target app and requirements — please use our contact page.

Open contact page

Typical first response within one business day. Include your target app, scenarios, volume estimate and any existing sandbox credentials.

Engagement workflow

1. Scope confirmation: which Dama Mobile flows (auth, balances, transactions, RDC, transfers, payment requests, cash pickups).
2. Protocol analysis and API design: 2–5 business days depending on complexity.
3. Build and internal validation against a sandbox entity: 3–8 business days.
4. Documentation, samples and test cases: 1–2 business days.
5. First delivery typically in 5–15 business days; longer if third-party or partner-bank approvals are required.

FAQ

What do you need from me?

How do you handle compliance?

Can you integrate with my accounting or ERP?

Do you support iOS as well as Android?