Western Union Send Money MY API integration (remittance & OpenFinance)

1. Migrant-worker payroll portal

Context: a Malaysia-based recruiter or employer wants to offer Bangladeshi or Nepali workers a one-tap remittance flow tied to payday. Data/API involved: FX quote API (MYR→BDT, MYR→NPR), FPX-funded send API, status webhook, statement export for HR. OpenFinance mapping: PISP-style payment initiation funded by an authorized FPX bank account, plus AISP-style statement read for downstream reporting.

2. Accounting & ERP reconciliation

Context: an SME with frequent cross-border supplier or family payments needs unified bookkeeping. Data/API involved: paged transfer history, MTCN, fee, FX rate at execution, payout method, MYWU points earned. The exporter pushes daily JSON or Excel into Xero, QuickBooks, or SAP. OpenData mapping: this is a classic statement-export pattern, equivalent to a bank’s read-only AISP feed but for remittance activity.

3. Compliance & AML monitoring

Context: a fintech aggregator must screen consolidated outbound flows against BNM’s 2025 e-money AML/CFT expectations and the UNSCR sanctions list. Data/API involved: receiver country, principal, frequency, KYC verification level, repeat-receiver pattern. The integration emits a normalized event stream into the customer’s transaction monitoring stack with consent records attached.

4. Multi-rail remittance comparator

Context: a price-comparison site (Bangladesh, Indonesia, Philippines audiences) wants to display Western Union Send Money MY rates next to other rails. Data/API involved: real-time MYR→BDT FX quote, transfer fee bands, payout-method availability per corridor. We deliver a thin read-only adapter that respects the app’s rate-limit envelope.

5. Loyalty wallet aggregation

Context: a super-app aggregates loyalty points across remittance, e-wallets, and airline programs. Data/API involved: MYWU points balance, accrual events per send, redemption history. OpenFinance mapping: treats loyalty points as a tokenized balance, surfaced via a normalized "wallet read" endpoint that downstream UIs can render alongside cash balances.

Deliverables checklist

• OpenAPI 3.1 specification covering quote, send, track, statement and webhook endpoints
• Protocol & auth flow report (mobile token, device binding, certificate pinning notes)
• Runnable source for FX, send, and statement APIs (Python & Node.js)
• Postman collection plus pytest / Jest integration suite against a captured fixture set
• Compliance guidance pack: BNM Money Services Business Act, AML/CFT, retention
• Operational runbook (token rotation, FPX outage handling, MTCN trace procedure)

API example 1 — FX quote (pseudocode)

POST /api/v1/wu-my/quote
Content-Type: application/json
Authorization: Bearer <PARTNER_TOKEN>

{
  "send_country": "MY",
  "send_currency": "MYR",
  "receive_country": "BD",
  "receive_currency": "BDT",
  "principal": 1000.00,
  "payout_method": "BANK_DEPOSIT",
  "funding_method": "FPX"
}

200 OK
{
  "principal_myr": 1000.00,
  "fx_rate": 25.7184,
  "fee_myr": 5.00,
  "payout_bdt": 25718.40,
  "govt_incentive_pct": 2.5,
  "quote_id": "Q-7f3e9b1a",
  "expires_at": "2026-05-09T12:35:00Z"
}

API example 2 — Statement export (pseudocode)

POST /api/v1/wu-my/statement
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "wu:my:1834***",
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "corridors": ["MY-BD", "MY-PH"],
  "page":      1,
  "page_size": 100
}

200 OK
{
  "page": 1, "total": 27,
  "items": [
    {
      "mtcn": "6427-1839-2210",
      "status": "PAID",
      "sent_at": "2026-04-12T03:14:08Z",
      "principal_myr": 800.00,
      "fee_myr": 5.00,
      "fx_rate": 25.5102,
      "payout_bdt": 20408.16,
      "payout_method": "BANK_DEPOSIT",
      "receiver_ref": "rcv:bd:9921",
      "mywu_points": 8
    }
  ]
}

API example 3 — Status webhook (pseudocode)

POST https://your-app.example.com/wu/webhook
X-WU-Signature: t=1746792000,v1=8d1c…a02
Content-Type: application/json

{
  "event": "transfer.status_changed",
  "mtcn": "6427-1839-2210",
  "previous_status": "IN_PROCESS",
  "new_status": "AVAILABLE_FOR_PICKUP",
  "corridor": "MY-PH",
  "updated_at": "2026-05-09T11:02:31Z"
}

// Verify signature: HMAC_SHA256(secret, "t="+t+"."+raw_body)
// Reject if |now - t| > 300s or signature mismatch
// Idempotency key = mtcn + new_status

Compliance & privacy

All Western Union Send Money MY integrations we deliver operate under documented authorization or published partner APIs, never through unauthorized credential reuse. Our reference compliance baseline includes the Malaysian Bank Negara Malaysia Money Services Business Act 2011, the BNM 2025 e-money AML/CFT exposure draft (sanctions screening against the UNSCR list), and Western Union’s own Open Banking partner programme. PII (national ID, selfie, MTCN, beneficiary name) is encrypted at rest, retained for the minimum window required by audit, and removed on revocation.

Data flow / architecture

• Client App (Western Union Send Money MY on Android/iOS) issues a quote or send request.
• Ingestion / API gateway normalizes the call, attaches consent & partner credentials, and forwards to the Western Union remittance backend (or an authorized partner endpoint).
• Storage writes the redacted transaction record (MTCN, FX, fee, status) to a partitioned ledger (Postgres + object storage for KYC artifacts).
• Analytics / API output exposes downstream feeds: REST statement endpoint, webhook fan-out, daily Excel drop, and a metrics surface for AML monitoring.

Market positioning & user profile

Western Union Send Money MY is the Malaysia-focused build of Western Union’s consumer remittance app. Its primary users are migrant workers (Malaysia hosts roughly 3 million migrant workers, predominantly from Indonesia, Bangladesh and Nepal) and the families of Malaysian residents abroad. The app is mobile-first, supports Android and iOS, and is strongest along outbound corridors to Bangladesh, the Philippines, Indonesia, India and Nepal. Recent ecosystem moves include API-level integration with the Valyou mobile wallet for cash and wallet payouts, alignment with regional initiatives such as BIS Project Nexus (which connects Malaysia’s instant payment system with Indonesia, the Philippines, Singapore and Thailand), and the Bangladesh government’s ongoing 2.5% remittance incentive that the app surfaces inside its quote flow.

About OpenFinance Lab

We are an independent technical studio focused on mobile-app protocol analysis and OpenData / OpenFinance / OpenBanking adapters. Our engineers come from card-scheme acquiring, cross-border PSPs, and mobile reverse-engineering backgrounds. For Western Union Send Money MY specifically, the team is familiar with FPX integration patterns, Malaysian e-KYC artifacts, and the BNM regulatory perimeter.

• Two engagement models: source code delivery from $300, or pay-per-call API access
• End-to-end pipeline: protocol analysis → build → validation → compliance handover
• Custom Python / Node.js / Go SDKs with pytest or Jest harnesses
• Security & privacy reviews aligned to BNM RMiT and PSD2-style consent patterns

Contact

To request a quote or send your target app and requirements, open our contact page:

Contact page

Engagement workflow

1. Scope confirmation: corridors (MY-BD, MY-PH…), funding method (FPX or cash agent), data needs.
2. Protocol analysis & API design: 2–5 business days depending on auth complexity.
3. Build & internal validation against captured fixtures: 3–8 business days.
4. Docs, sample SDK, Postman collection, test cases: 1–2 business days.
5. First delivery typically lands in 5–15 business days; partner-side approvals may extend.

FAQ

What do you need from me to start a Western Union Send Money MY integration?

How long does delivery take for a remittance API integration?

How do you handle compliance and KYC for Western Union flows?

Can you support pay-per-call API access instead of source code delivery?