BOSS Money Transfer. Send Cash — API integration & OpenFinance services

Authentication & session module

Mirrors the BOSS Money mobile authorization handshake — device registration, OTP verification, refresh-token rotation, and biometric step-up. Output: a stable bearer-token client that downstream services can call without re-running the in-app login each time.

Transaction history API

Returns historical sends with paging, date filters, and corridor filters. Each row carries send_amount, receive_amount, fx_rate, fee, payout_method, and status so accounting tools can ledger-match without screen scraping.

Quote & rate API

Pulls live exchange rates, fee tables, and promotional pricing (e.g. the $0-fee first-three-transfers and Mexico free-transfer offers). Use case: rate-comparison dashboards and dynamic pricing engines for affiliate platforms.

Payout status & reversal feed

Subscribes to delivery state changes — "in transit", "available for cash pickup", "deposited", "refunded" — and emits webhooks so support agents see the same status as customers in the BOSS Money app.

Top-up / mobile recharge module

Lists carriers, denominations, and bonus offers (double or triple balance promos) and submits airtime / data recharge requests, with receipt records that can be reconciled against settlement reports.

Beneficiary & corridor catalog

Exposes saved recipients (name, payout method, payout currency, country) and the list of supported corridors and partner banks, so external CRMs can pre-fill the same send form the consumer app shows.

1. Diaspora-focused fintech consolidating multiple remittance accounts

A multi-rail neobank wants its U.S.-based migrant customers to see BOSS Money sends alongside Wise, Remitly, and Xoom transfers in one feed. We deliver an authorized BOSS Money client that pulls historical sends and subscribes to payout-status webhooks, then normalizes records into a shared remittance_event schema for the host platform.

2. Compliance team running periodic sanctions re-screening

A licensed money-transmission affiliate must re-screen recipients against OFAC SDN updates. Our integration exports beneficiary records and recent send pairs, ships them through an OFAC API, and writes hits back to a case-management system, with an audit log keyed to BOSS Money transaction IDs.

3. Telecom partner reconciling airtime top-ups

Carrier partners (Telcel, Movistar, Tigo, MTN, Claro, Digicel, Airtel, Viva, Natcom) need daily settlement files. We build a top-up extraction job that pulls recharge receipts, joins them with carrier-side CDRs, and emits a reconciled CSV to S3 — flagging any "promo bonus" rows that should not bill against settlement.

4. Accounting export for small business owners on H-1B / E-2 visas

Family-business operators sending recurring payments abroad want a clean ledger for tax filing. We deliver a CLI / web button that pulls the prior tax year's BOSS Money transfers, attaches FX rates and fees, and exports QuickBooks-compatible CSV plus a printable PDF statement.

5. Customer-support copilot with live transfer state

An outsourced contact center needs to answer "where is my money?" without VPN access to BOSS Money admin tools. We expose a thin internal API that, given a phone number plus consent token, returns the last 30 days of sends with the same payout-status text customers see in the app — reducing ticket-handling time on instant and same-day transfers.

Deliverables checklist

• OpenAPI / Swagger specification for every endpoint we publish
• Protocol & auth-flow report (token rotation, OTP, device binding)
• Runnable source code in Python or Node.js (your choice)
• Postman collection, integration tests, and load-test profile
• KYC / AML / OFAC handling notes and data-retention guidance
• Hand-over session and 30-day issue support window

Engagement models

• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction.
• Pay-per-call API billing — call our hosted endpoints and pay only per successful response, no upfront fee. Ideal for usage-based budgets.
• Optional add-ons: managed hosting, SLA-backed uptime, alerting on protocol drift.

Sample stack

Python 3.11 + FastAPI for the authorization client, Postgres for transaction caching, Redis for rate-limit and idempotency keys, Cloudflare or AWS WAF in front, optional Temporal for retryable payout-status workflows. Drop-in adapters for Node.js, Go, or Java are available.

Login & token refresh

POST /api/v1/boss-money/auth/login
Content-Type: application/json

{
  "phone": "+1XXXXXXXXXX",
  "otp": "482910",
  "device_id": "<stable-uuid>"
}

200 OK
{
  "access_token": "eyJ...",
  "refresh_token": "rft_...",
  "expires_in": 1800,
  "user_id": "usr_98712"
}

Transfer history query

GET /api/v1/boss-money/transfers
  ?from=2026-01-01&to=2026-04-28
  &corridor=US-MX&status=delivered
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "items": [{
    "transfer_id": "trf_4f8a",
    "send_amount": "350.00",
    "send_currency": "USD",
    "receive_amount": "5985.00",
    "receive_currency": "MXN",
    "fx_rate": "17.10",
    "fee": "1.99",
    "payout_method": "cash_pickup",
    "partner": "Elektra",
    "status": "delivered",
    "created_at": "2026-04-22T14:31:02Z"
  }],
  "next_cursor": "eyJv..."
}

Payout-status webhook

POST /your-callback/boss-money/events
X-Signature: sha256=...
Content-Type: application/json

{
  "event": "transfer.status_changed",
  "transfer_id": "trf_4f8a",
  "previous_status": "in_transit",
  "current_status": "delivered",
  "occurred_at": "2026-04-22T14:33:11Z"
}

# Verify HMAC, then upsert into the local
# remittance_event table.

About our studio

We are an independent technical studio specializing in App interface integration and authorized API integration. Our engineers come from licensed money-transmitter operations, payment-gateway teams, and protocol-analysis backgrounds, with deep experience across remittance, digital banking, and cross-border payouts. We have shipped end-to-end integrations against more than a dozen consumer fintech apps, and we know the operational rhythm of OFAC re-screens, NMLS audits, and Reg-E disclosures.

• Remittance, digital banking, insurtech, and cross-border clearing
• Mobile protocol analysis (Android & iOS) and authorized client SDKs
• Custom Python / Node.js / Go libraries with full test harnesses
• End-to-end pipeline: protocol analysis → build → validation → compliance hand-over
• Source code delivery from $300 — runnable API source code and documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted API endpoints and pay only for the calls you make, with no upfront fee

Contact

To request a quote or share your BOSS Money integration scope (transfer history, payout-status webhooks, top-ups, beneficiary book, or a combination), open our contact page below. We typically reply within one business day with a fixed-price proposal or a pay-per-call estimate.

Open contact page →

Engagement workflow

1. Scope confirmation: which BOSS Money data (transfers, payouts, top-ups, beneficiaries) and which destination corridors.
2. Protocol analysis & API design (2–5 business days, complexity-dependent).
3. Build & internal validation against authorized accounts (3–8 business days).
4. Documentation, samples, and test cases (1–2 business days).
5. Delivery & hand-over; typical first drop is 5–15 business days. Carrier or partner approvals may extend timelines.

FAQ

What do you need from me?

How long does delivery take?

How do you handle compliance?

Can you also integrate Remitly, Xoom, or Wise?