Ria Money Transfer API integration & remittance data services

Deliverables checklist

• OpenAPI 3.1 specification covering every Ria endpoint we wrap
• Protocol & auth-flow report — token chain, header signing, anti-replay nonces
• Runnable Python and Node.js client with retry, idempotency keys and webhook signature checks
• Sandbox + production Postman collection seeded with a fictitious "test corridor"
• Compliance brief — KYC field mapping, e-KYC selfie flow, OFAC screening hooks, PCI DSS guidance for card-funded transfers

Pricing models

Two engagement models so the cost shape matches your project profile:

• Source-code delivery from $300 — runnable API client and full documentation; you pay after delivery once acceptance tests pass.
• Pay-per-call hosted API — we run the integration on our infrastructure and bill per successful call, no upfront fee, ideal for usage that ramps slowly.

1. Diaspora-bank balance & remittance unification

Context. A neobank serving Mexican or Filipino communities in the US wants one screen showing both their card spend and pending Ria transfers home.

Data / API. GET /transfers filtered by sender, plus the webhook stream for status updates; we map each Ria transfer into the same ledger primitive the neobank uses for card transactions.

OpenFinance angle. Treats Ria as a non-bank financial-data source under an aggregation consent, similar to how Plaid or Tink expose bank statements.

2. SME accounting export for cross-border payroll

Context. A small business pays contractors in India, the Philippines and Colombia using the Ria app and needs the journal entries inside QuickBooks or Xero.

Data / API. Pull the monthly statement, FX quote and fee breakdown; emit IFRS-compatible journal lines (Expense, FX Gain/Loss, Cash) keyed by Ria reference number.

OpenFinance angle. Same envelope an OpenBanking statement export uses, but for a money-transmitter ledger rather than a bank account.

3. Risk & compliance screening for partner platforms

Context. A digital wallet that lets users initiate a Ria transfer from inside its app needs to relay OFAC and source-of-funds checks back to its own risk engine.

Data / API. KYC verification status, transfer amount, destination country and payout method; mirrored into the wallet's transaction-monitoring queue with a deterministic hash so duplicates are filtered.

OpenFinance angle. Aligns with FATF Recommendation 16 (the "travel rule") for cross-border consumer transfers.

4. Multi-provider remittance comparison engine

Context. A price-comparison site wants live FX and fee quotes for the same corridor across Ria, Remitly, Wise and Western Union to surface the cheapest option.

Data / API. The Ria quote endpoint with locked-in TTL, polled per amount-bracket; cached on our side for 30 seconds and exposed under a unified /quotes schema.

OpenFinance angle. Open-product-data: surfacing comparable retail prices is the consumer-protection variant of OpenBanking.

5. Conversational remittance via WhatsApp

Context. A community-finance startup wants to bolt Ria's WhatsApp send-money flow (added by Ria in 2024 for US→Mexico, since extended to 15+ corridors) into its own chatbot.

Data / API. Quote + create-transfer endpoints called from a WhatsApp Cloud API handler, with status updates pushed back as templated WhatsApp messages.

OpenFinance angle. Channel-agnostic remittance: same backend transfer regardless of whether it was created from app, web or chat.

1. Authenticate & list saved recipients

POST /v1/ria/auth/token
Content-Type: application/json
Ocp-Apim-Subscription-Key: <PARTNER_KEY>

{
  "grant_type": "password",
  "username": "sender@example.com",
  "password": "<app_password>",
  "device_id": "0c3a-..."
}

200 OK
{
  "access_token": "eyJhbGciOi...",
  "refresh_token": "rt_8f...",
  "expires_in": 3600,
  "kyc_status": "verified"
}

GET /v1/ria/recipients?country=MX&limit=50
Authorization: Bearer eyJhbGciOi...

200 OK
{
  "items": [
    {
      "recipient_id": "rcp_24c1",
      "first_name": "Maria",
      "last_name": "L.",
      "country": "MX",
      "payout_method": "BANK_DEPOSIT",
      "bank_account_masked": "****8821"
    }
  ],
  "next_cursor": null
}

2. Quote & create a transfer (with promo)

POST /v1/ria/quotes
Authorization: Bearer <ACCESS_TOKEN>

{
  "send_amount": "200.00",
  "send_currency": "USD",
  "receive_country": "PH",
  "payout_method": "MOBILE_WALLET",
  "promo_code": "HELLORIA"
}

200 OK
{
  "quote_id": "q_5f1b",
  "exchange_rate": "55.842",
  "receive_amount": "11168.40",
  "receive_currency": "PHP",
  "fee": "0.00",
  "expires_at": "2026-05-01T12:34:11Z"
}

POST /v1/ria/transfers
Idempotency-Key: 2026-05-01-T-77231

{ "quote_id": "q_5f1b", "recipient_id": "rcp_24c1",
  "funding_source": "DEBIT_CARD", "card_token": "tok_..." }

3. Webhook for transfer state changes

POST https://your-app/webhooks/ria
X-Ria-Signature: t=1714560000,v1=8a4c9f...

{
  "event_id": "evt_91a",
  "event_type": "transfer.paid",
  "occurred_at": "2026-05-01T12:38:02Z",
  "transfer": {
    "id": "tr_77231",
    "reference": "PJ8H-2K1F-9",
    "status": "PAID",
    "payout_location_id": "agt_mex_2104",
    "amount_paid": "11168.40",
    "currency": "PHP"
  }
}

# Verification: HMAC-SHA256 of "{t}.{raw_body}" using shared secret;
# reject events older than 5 minutes to mitigate replay.

Compliance & privacy

Ria operates as a regulated money transmitter under multiple licences: FinCEN-registered Dandelion Payments in the US (NMLS #920968), Euronet Payment Services in the UK under FCA supervision, and Ria Lithuania UAB authorised by the Bank of Lithuania for the EEA. Our integrations preserve that perimeter: card data follows PCI DSS tokenisation, personal data is processed under GDPR for EU senders, and OFAC sanctions screening is enforced on every payload.

For cross-border behaviour we follow FATF guidance — specifically Recommendation 16 ("travel rule") — so the originator and beneficiary information attached to a Ria transfer survives the hop into your downstream system without being silently dropped. Consent decisions, IP and timestamp are stored alongside every API call in an append-only audit log.

Modules we typically wire up

• OAuth-style token issuance and refresh against the Ria session
• Recipient CRUD with deduplication by (country, payout method, masked account)
• Quote → create-transfer → status pipeline with idempotency keys
• Webhook receiver with HMAC verification and dead-letter queue
• Statement and fee export (JSON / CSV / Excel) for finance teams
• Promo-code application (HELLORIA and successor campaigns) with eligibility checks

About OpenFinance Lab

We are an independent technical studio focused on App interface integration, OpenData aggregation and authorised API integration for fintech, e-commerce, travel and OTT clients. Engineers on the team have shipped production code at banks, card networks and remittance providers, so we understand the difference between a marketing screenshot and a production-ready API.

• Cross-border payments, digital banking and accounting integrations
• Protocol analysis, API design, SDK development in Python / Node.js / Go
• Compliance-aware delivery: GDPR, PSD2, PCI DSS, FATF travel rule
• End-to-end pipeline: discovery → reverse engineering → build → conformance tests → handover
• Source-code delivery from $300 — runnable code & docs, paid after acceptance
• Pay-per-call hosted API — usage-based pricing, no upfront cost

Contact

To request a quote, scope a Ria Money Transfer integration, or ask about another target app, head to our contact page. Provide the target app name and your concrete data needs, and we will respond with a delivery estimate within one business day.

Contact page

Engagement workflow

1. Scope confirmation: which Ria flows you need (transfer history, FX export, webhook subscriber, WhatsApp channel) and your downstream system.
2. Protocol analysis & API design (2–5 business days, depending on whether sandbox credentials are available).
3. Build & internal validation against the sandbox (3–8 business days), with daily progress checkpoints.
4. Documentation, sample requests and Postman collection (1–2 business days).
5. Typical first delivery: 5–15 business days. Approvals from Ria's partner team for production credentials may extend the timeline.

FAQ

What kind of Ria Money Transfer data can you integrate?

How long does delivery take?

How do you handle compliance and privacy?

Do you support Ria's WhatsApp send-money flow?