WorldRemit API integration & remittance OpenFinance services

Transfer history & status API

Paginated retrieval of historical transfers with filters by date, corridor, payout type, and status (pending, in-transit, paid, refunded, cancelled). Used for monthly reconciliation, finance close, and customer-support lookups when a receiver claims non-receipt.

Recipient & KYC tag sync

Mirror saved recipients into your CRM with corridor, payout method, partner bank/wallet and KYC tier tags. Critical for sanctions screening refresh and beneficial-owner reviews across multi-jurisdiction rollouts.

FX quote & fee snapshot

Sample the live rate WorldRemit offers per corridor versus the mid-market reference, plus the fee schedule (which varies by payout method). Useful for treasury teams pricing internal cross-border float and for comparison dashboards against Wise, Remitly and Western Union.

Payout corridor & partner map

Structured catalogue of supported destination countries and per-country partner sets — e.g. M-Pesa, Airtel, Equity Bank in Kenya; GCash, PayMaya, CoinsPH, BDO in the Philippines; MTN, Vodafone, EcoBank in Ghana. Enables routing logic for downstream payout orchestration.

Webhook / notification bridge

A push channel that fires when a transfer changes state ("ready to collect", "paid", "blocked – AML review"). Replaces brittle polling and is mandatory for SLA-sensitive use cases like emergency family transfers.

Airtime topup & mobile wallet rail

Programmatic visibility into airtime topup transactions and mobile-money rails. Important for diaspora-focused fintechs and telco-aligned products where airtime credit and wallet top-ups are part of the same financial story.

1. Diaspora-focused fintech: unified remittance ledger

Business context: a UK or US fintech serves migrant communities that hold accounts with WorldRemit, Sendwave and a local neobank. Data involved: transfer history, FX quote, recipient list. OpenFinance mapping: account-information-style read endpoints exposing remittance activity as a normalised "money-out" feed alongside open banking AISP data, so customers see one ledger.

2. SME accounting export

Business context: an SME pays overseas freelancers and contractors through WorldRemit and needs the activity in Xero or QuickBooks. Data involved: paginated transfer history with fee, FX and counterparty fields. Flow: nightly extract → CSV/JSON push → ledger mapping. Mirrors the Open Banking "transactions" endpoint but for outbound remittance.

3. Compliance & AML monitoring

Business context: a regulated bank co-marketing remittance services wants near-real-time visibility into its customers' cross-border flows for AML triage. Data involved: transfer events, recipient KYC tags, status. Webhook delivery into the bank's transaction-monitoring engine. Aligns with FATF Recommendation 16 expectations on originator/beneficiary information.

4. FX dashboard & pricing intelligence

Business context: a treasury team or comparison-shopping site benchmarks WorldRemit rates against Wise, Remitly, Xe, OFX and Western Union across 20+ corridors. Data involved: FX quote endpoint, fee schedule, payout-method matrix. Output: time-series store + Grafana / Metabase dashboard.

5. Telecom & airtime partner ops

Business context: an MNO operating in Kenya, Ghana or the Philippines reconciles inbound airtime topup volumes from WorldRemit. Data involved: airtime topup records by MSISDN, partner identifier and operator. Flow: scheduled pull → settlement file → partner billing.

Deliverables checklist

• API specification (OpenAPI / Swagger) per endpoint
• Protocol & auth flow report (OAuth, token rotation, cookie/session chain, SCA/3DS notes)
• Runnable source for login, transfer history, FX quote and webhook receiver (Python and Node.js, single Docker image)
• Automated tests (happy path, paging, pending → paid transitions, error cases)
• Compliance guidance (FCA, PSD2 SCA, GDPR, FATF AML/CTF, data minimization, retention)
• Postman / Insomnia collection ready for your QA team

API example 1 — paginated transfer history

// Example: fetch WorldRemit-style transfer history (pseudocode)
POST /api/v1/worldremit/transfers/list
Content-Type: application/json
Authorization: Bearer <ACCESS_TOKEN>

{
  "account_id": "wr_user_abc123",
  "from_date":  "2026-04-01",
  "to_date":    "2026-04-30",
  "corridor":   "GB-KE",
  "status":     ["paid","ready_for_collection"],
  "page":       1,
  "page_size":  50
}

// Response (excerpt)
{
  "page": 1, "page_size": 50, "total": 217,
  "transfers": [{
    "id": "WR-7Q9-XJ12",
    "sent_amount":   {"value": 250.00, "ccy": "GBP"},
    "received_amount":{"value": 41875.00,"ccy": "KES"},
    "fx_rate":       167.50,
    "fee":           {"value": 1.99, "ccy": "GBP"},
    "payout_method": "mobile_wallet",
    "payout_partner":"M-Pesa",
    "recipient_id":  "rcpt_91a2",
    "status":        "paid",
    "created_at":    "2026-04-12T08:14:22Z",
    "paid_at":       "2026-04-12T08:14:39Z"
  }]
}

API example 2 — FX quote & fee snapshot

GET /api/v1/worldremit/quote
   ?send_ccy=GBP&recv_ccy=PHP
   &amount=300&payout=cash_pickup
Authorization: Bearer <ACCESS_TOKEN>

// Response
{
  "send":   {"value": 300.00, "ccy": "GBP"},
  "receive":{"value": 21285.00,"ccy": "PHP"},
  "fx_rate": 70.95,
  "mid_market_rate": 71.62,
  "spread_bps": 94,
  "fee": {"value": 0.99, "ccy": "GBP"},
  "payout_partner_options": ["BDO","Cebuana","M Lhuillier","PS Bank"],
  "estimated_delivery": "minutes"
}

API example 3 — webhook event (transfer status change)

POST <your-callback-url>
Content-Type: application/json
X-OFL-Signature: sha256=...

{
  "event_id":   "evt_018f9d4d",
  "event_type": "transfer.status_changed",
  "occurred_at":"2026-04-12T08:14:39Z",
  "data": {
    "transfer_id": "WR-7Q9-XJ12",
    "previous_status": "in_transit",
    "current_status":  "paid",
    "corridor": "GB-KE",
    "payout_partner": "M-Pesa"
  }
}

// Errors: 401 invalid_token, 409 corridor_unavailable,
// 422 amount_below_min, 451 corridor_blocked_compliance

Regulatory alignment

WorldRemit is authorised in the UK by the Financial Conduct Authority and is part of the Zepz group. Integrations we ship are designed to respect the same boundaries: PSD2 Strong Customer Authentication for any payment-initiation flow, GDPR for personal data on UK/EU residents, and FATF Recommendation 16 originator/beneficiary information for the travel rule. We also reference the WorldRemit overview on Wikipedia when scoping public-context facts.

Data handling

We work strictly under your customer's authorization or documented public flows; we do not bypass authentication, and we do not extract data beyond the explicit scope. Logs record every access event with caller, scope, timestamp and IP. Personal data is redacted at rest by default; the only fields persisted past a job are those you list in the scope schema. NDAs and DPIAs signed on request.

About our studio

OpenFinance Lab is a small, focused studio specialising in mobile app protocol analysis and authorized API integration. Our engineers come out of payments, banking, mobile-money and protocol-analysis backgrounds, and we have shipped integrations against remittance apps, neobanks, e-commerce platforms, OTT services and travel apps for clients in the UK, EU, MENA, India and Southeast Asia.

• Domain depth in payments, digital banking, remittance and cross-border clearing
• Custom Python, Node.js and Go SDKs plus test harnesses and Postman bundles
• Full pipeline: protocol analysis → build → validation → compliance hand-off
• Source code delivery from $300 — receive runnable API source code and full documentation; pay after delivery upon satisfaction
• Pay-per-call API billing — access our hosted API and pay only per call, no upfront cost; suited to teams that prefer usage-based pricing

Contact

For a quote or to submit your target app and requirements (WorldRemit corridors, data scope, region), open our contact page:

Contact page

Typical reply within one UK business day.

Engagement workflow

1. Scope confirmation: corridors, payout methods, data fields, region of senders.
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build and internal validation against your sandbox accounts (3–8 business days).
4. Docs, samples and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; third-party approvals or extra corridors may extend.

FAQ

Does WorldRemit publish a public developer API?

What WorldRemit data can be exposed via API integration?

How long does a WorldRemit-style integration take to deliver?

How do you handle compliance and AML?