Utransfer US: Global Remit API integration (OpenFinance & remittance data)

Why Utransfer data is integration-worthy

Utransfer US sits between US funding sources (ACH-pulled bank accounts, debit funding) and overseas payout rails in seven countries. That position means each transfer record carries unusually rich, end-to-end context: payer KYC anchors, FX execution prices, corridor-level fee structures, and downstream payout confirmations. For an integrator, this is the data backbone needed to power expense reports, family-remittance dashboards, AML monitoring, or aggregated multi-provider remittance views.

Because the app is FinCEN-registered, every record is generated under a regulated audit trail, which makes the resulting API surface attractive for accounting platforms and compliance vendors that need defensible, time-stamped transaction lineage rather than scraped UI text.

Recent product changes (research-derived)

• 2024: Utransfer US launched its US-outbound app on iOS and Google Play, opening with the US→Korea corridor.
• 2025: Roadmap publicly mentions India, Vietnam, and the Philippines as new corridors, with Mexico added and Mexico same-corridor speed reduced to a few minutes.
• Sep 2025 milestone: ~USD 32M cumulative volume, 23k transactions, 20k users; coverage expanded from 25 to 32 US states.
• Onboarding economics: USD 8 welcome credits split across the first two transfers, plus USD 10 dual-sided referrals — both surfaced through API-accessible promo and ledger objects.

1. Authentication & session APIs

Mirror the mobile auth flow: phone-number / email login, OTP verification, device binding, and refresh-token rotation. We hand you a clean OAuth-style client that hides the raw mobile handshake and produces a stable access_token + refresh_token pair for backend use. Typical use: nightly batch ingestion service that holds a per-user token vault.

2. KYC & sender-profile API

Read-only access to verified sender profile attributes — full name, address state (one of the 32 supported US states), document verification status, and limit tier. Use this to drive customer-tier logic, FinCEN CTR pre-screening, or duplicate-payer detection across sister fintech apps.

3. FX quote & corridor pricing

Server-to-server quote endpoint returning a corridor-specific locked rate, expiry, fee breakdown (zero remittance fee, FX spread component), and minimum/maximum amounts. Useful for comparison aggregators that surface Utransfer alongside Wise, Remitly, Xoom, WorldRemit, MoneyGram, and Western Union in a single quote screen.

4. Transfer-history & statement export

Date-ranged transaction list with paging, currency filters, and corridor filters. Exports as JSON, CSV, Excel, or PDF statement for personal-finance dashboards, year-end tax prep, or US senior-care apps tracking remittances on behalf of relatives.

5. Status webhooks & reconciliation

Push notifications on every state change, signed with HMAC and delivered with retry/backoff. Each event carries an idempotency key, normalized status, and the original provider-side status, so your reconciliation engine can ingest without bespoke parsing.

6. Promo & referral ledger

Read access to welcome-credit usage, referral-link redemption, and credit balance. Useful for partner growth dashboards, fraud-pattern detection on referral abuse, or LTV models that need promo-adjusted revenue per cohort.

Scenario A — Diaspora finance dashboard

Business context: A US fintech serving Korean, Mexican, Filipino, and Indian diaspora users wants to consolidate remittance history across multiple providers. Data/API involved: Utransfer transfer-history export, FX quote, recipient directory. OpenFinance mapping: consent-based read of personal financial data, normalised against an internal canonical schema shared with Wise, Remitly, and Xoom feeds.

Scenario B — SMB accounting reconciliation

Business context: An accounting platform where US founders pay overseas contractors needs to attach Utransfer transfers to QuickBooks/Xero entries. Data/API involved: webhook on payout completion, statement export (CSV), FinCEN reference IDs. OpenFinance mapping: structured payment-initiation receipt feeding the books-of-record without manual CSV downloads.

Scenario C — Compliance & AML monitoring

Business context: An MSB-compliance vendor monitoring cumulative outbound flows per user across providers. Data/API involved: sender profile, transfer record, status events. OpenFinance mapping: aligns with FinCEN BSA/AML controls; daily aggregation supports CTR/SAR pre-screen logic and cumulative-amount triggers.

Scenario D — Comparison & routing engine

Business context: A consumer comparison app surfaces the cheapest USD→KRW or USD→MXN route in real time. Data/API involved: FX quote API, corridor metadata, fee breakdown. OpenFinance mapping: normalised quote object placed alongside Wise, Xoom, WorldRemit, OFX, and MoneyGram quotes; deep link returns the user to Utransfer for the actual transfer.

Scenario E — Senior-care & family share

Business context: A US family-care app helps adult children watch over an elderly parent's overseas support transfers. Data/API involved: read-only transfer history, status webhook, low-balance / failed-transfer alerts. OpenFinance mapping: third-party consent flow with revocable scope, consistent with US OpenBanking 1033 expectations.

Snippet 1 — Authentication & token refresh

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

{
  "phone": "+1-415-555-0188",
  "country_code": "US",
  "device_id": "dvc_8c2ad9f1",
  "otp": "419283"
}

Response 200:
{
  "access_token": "ut_at_...",
  "refresh_token": "ut_rt_...",
  "expires_in": 3600,
  "kyc_tier": "TIER_2",
  "supported_corridors": ["AU","CA","IN","JP","KR","MX","PH"]
}

# Refresh
POST /api/v1/utransfer/auth/refresh
{ "refresh_token": "ut_rt_..." }

Snippet 2 — FX quote & statement export

POST /api/v1/utransfer/fx/quote
Authorization: Bearer <ACCESS_TOKEN>

{
  "send_currency": "USD",
  "receive_currency": "KRW",
  "send_amount": 500.00,
  "corridor": "US-KR"
}

Response 200:
{
  "quote_id": "qt_a91f...",
  "rate": 1392.45,
  "fee": 0.00,
  "expires_at": "2026-04-29T12:00:30Z",
  "estimated_arrival": "PT1H"
}

# Statement export
GET /api/v1/utransfer/statements?from=2026-01-01&to=2026-04-29&corridor=US-MX&format=csv
Authorization: Bearer <ACCESS_TOKEN>

Snippet 3 — Webhook (status update)

POST https://your-app.example.com/webhooks/utransfer
X-Utransfer-Signature: t=1714377600,v1=8c1f...
Content-Type: application/json

{
  "event": "transfer.status_changed",
  "idempotency_key": "evt_2f81c0",
  "transfer_id": "tx_4a91...",
  "previous_status": "FUNDED",
  "status": "PAID_OUT",
  "corridor": "US-MX",
  "amount": { "send": 500.00, "receive": 8412.30, "currency_pair": "USD/MXN" },
  "fincen_ref": "FC-20260429-...",
  "occurred_at": "2026-04-29T11:42:18Z"
}

# Verify HMAC, then upsert into your ledger; respond 2xx within 5s.

Deliverables checklist

• OpenAPI / Swagger specification for the Utransfer adapter (auth, FX quote, statement, webhook)
• Protocol & auth report (token lifecycle, device binding, OTP handling)
• Runnable source code for login, FX quote, statement export, and webhook receiver (Python and Node.js)
• Postman / cURL collection plus automated regression tests
• Compliance guidance (FinCEN MSB, BSA/AML, CFPB 1033, GDPR where applicable)
• Source-code delivery from USD 300 — pay after delivery upon satisfaction
• Pay-per-call hosted API option — no upfront cost, billed per call

Engagement workflow

1. Scope confirmation: which corridors, which data surfaces (history, FX, webhooks).
2. Protocol analysis & API design (2–5 business days, complexity-dependent).
3. Build & internal validation (3–8 business days).
4. Documentation, samples, and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; third-party approvals may extend timelines.