WireBarley Global Remittance API integration (OpenFinance / cross-border payouts)

Deliverables checklist

• API specification in OpenAPI 3.1 / Swagger with examples per corridor
• Protocol and auth flow report (token issuance, refresh, device binding)
• Runnable source for login, transfer history, payout create, payout status (Python and Node.js)
• Webhook receiver template for transfer status changes and FX rate updates
• Automated tests against sandbox or recorded fixtures, plus Postman collection
• Compliance brief (KYC tiers, Travel Rule fields, retention windows, redaction map)

Engagement & pricing

• Source code delivery from $300 — runnable API source, OpenAPI spec and docs; pay after delivery upon satisfaction.
• Pay-per-call API billing — call our hosted endpoint, pay per successful response, no upfront fee.
• Add-on: ongoing protocol-drift monitoring with weekly diff reports.
• Add-on: dedicated reconciliation worker that closes loops between transfer history and your ledger.

1. Diaspora payroll & gig payouts

Context: a payroll platform pays migrant workers and contractors in Vietnam, the Philippines and Indonesia from sending entities in Korea, Australia or the US. Data & APIs involved: OpenBarley quote endpoint, create payout with beneficiary bank or mobile wallet, status webhook, plus transfer history pull for monthly reconciliation. OpenFinance mapping: corridor selection driven by FX quote and fee table; ledger entries match ISO 20022 pacs.008 fields where the partner network supports them.

2. Accounting & ERP reconciliation

Context: an SME with cross-border suppliers needs WireBarley transfers to flow into Xero, QuickBooks or SAP S/4HANA. Data & APIs: paginated transfer history with state filter, fee breakdown, FX leg, plus PDF receipts for supporting documents. OpenFinance mapping: this is the OpenBanking statement export pattern applied to remittance — same shape as PSD2 AISP feeds, but populated with sender/receiver and FX components rather than card transactions.

3. Marketplace and super-app embed

Context: a Korean travel super-app or e-commerce marketplace embeds outbound transfers next to flight bookings and gift-card purchases. Data & APIs: account login API to resolve user identity, FX quote API to display the recipient amount inline, OpenBarley create-payout API behind the user's confirmation, then status webhook to drive in-app notifications. OpenFinance mapping: payment initiation pattern (PISP-equivalent) layered over WireBarley's own KYC.

4. Treasury dashboards & compliance

Context: a fintech treasury team needs visibility into volumes, average ticket size, FX margin and corridor risk. Data & APIs: read-only history API, FX history endpoint, plus daily aggregates pulled into a warehouse. OpenFinance mapping: feeds match common AISP analytics — only here the transactions are cross-border legs, so we add Travel Rule fields and originator/beneficiary metadata for sanctions screening.

5. Migration from legacy aggregator

Context: a money-services business is moving away from a legacy aggregator and wants OpenBarley to handle direct payouts in 15 currencies. Data & APIs: corridor metadata sync, FX rate sync, payout creation, refund and reversal endpoints. OpenFinance mapping: parallel-run wrapper that exposes one stable internal API while we translate to and from OpenBarley behind the scenes — this is how we typically de-risk cutover for production fintechs.

Auth: token issuance (pseudocode)

POST /api/v1/wirebarley/auth/token
Content-Type: application/json

{
  "grant_type": "client_credentials",
  "client_id": "<PARTNER_ID>",
  "client_secret": "<PARTNER_SECRET>",
  "scope": "transfer.read payout.write fx.read"
}

200 OK
{
  "access_token": "<JWT>",
  "token_type": "Bearer",
  "expires_in": 3600,
  "refresh_token": "<OPAQUE>"
}

Transfer history export (pseudocode)

GET /api/v1/wirebarley/transfers
?from_date=2026-04-01
&to_date=2026-04-30
&status=paid,refunded
&corridor=KR-VN
Authorization: Bearer <ACCESS_TOKEN>

200 OK
{
  "items": [
    {
      "transfer_id": "WB-2026-0411-83A",
      "sender_currency": "KRW",
      "receiver_currency": "VND",
      "send_amount": 1500000,
      "fx_rate": 18.42,
      "fee": 4500,
      "receive_amount": 27630000,
      "payout_method": "bank_transfer",
      "status": "paid",
      "created_at": "2026-04-11T09:11:02Z"
    }
  ],
  "next_cursor": "eyJvIjoxMDB9"
}

OpenBarley payout webhook (pseudocode)

POST https://your-app.example.com/webhooks/wirebarley
Content-Type: application/json
X-OpenBarley-Signature: t=1714780800,v1=<HMAC_SHA256>

{
  "event": "payout.status_changed",
  "payout_id": "OB-77F5C1",
  "previous_status": "in_flight",
  "current_status": "paid",
  "settled_at": "2026-04-29T14:02:11Z",
  "rail": "mobile_wallet",
  "corridor": "AU-PH"
}

// Verify HMAC using the shared secret, then idempotently
// upsert into the ledger keyed by payout_id.

Error handling & retries

All endpoints return RFC 7807-style problem+json on failure with a stable error_code. Recommended retry policy: exponential backoff with jitter on 503, 504 and idempotent POSTs carrying an Idempotency-Key header. We ship a reference Python and Node.js client that implements signature verification, idempotent retry, and structured logging out of the box.

Regulatory perimeter

Cross-border remittance integration sits in a multi-regulator zone. For EU-touching flows we follow PSD2 strong customer authentication and the EU's Anti-Money Laundering Directives (5AMLD and 6AMLD). For US flows we observe the FinCEN MSB perimeter and OFAC screening. For UK we align with the FCA payment-services rules, and for the Asia-Pacific corridors we reference local regulators such as MAS in Singapore and BSP in the Philippines. Travel Rule data — originator and beneficiary identifiers — is preserved end-to-end where the partner network supports ISO 20022 enriched fields.

Data minimization & retention

We avoid pulling raw KYC documents unless the integration explicitly requires them. Default: pull KYC tier and verification status only. Where document images are needed for downstream onboarding, we expose them through pre-signed URLs with short expiry and per-call audit logging. Retention windows are configurable per jurisdiction so EU and Korean data subjects can be handled without leaking into US storage.

Wise

Multi-currency accounts and transfers in 50+ currencies. Holds balance, transfer history and FX margin data; users who run Wise alongside WireBarley typically want a unified statement export and matched FX cost report.

Remitly

Mobile-first remittance with strong US-to-LATAM and US-to-Asia corridors. Holds transfer status, payout method and recipient data; commonly paired with WireBarley for redundancy in Asia-Pacific corridors.

WorldRemit (Zepz)

Sends to 130+ countries. Holds transfer, payout-method and KYC data; treasuries often want a normalized cross-app view of fees and FX margin alongside WireBarley's corridor mix.

Xoom (PayPal)

PayPal-owned remittance to 160+ countries. Holds transfer history and recipient data behind the PayPal wallet; useful as a parallel rail for North American senders also using WireBarley.

Western Union

Legacy global cash and digital network with deep agent coverage. Holds transaction, agent-location and ID-verification data; relevant when WireBarley users need cash pick-up in regions WireBarley does not directly cover.

MoneyGram

Cross-border peer-to-peer transfers via app, web and agent. Holds transfer-status and beneficiary data; teams sometimes pull MoneyGram and WireBarley data together for compliance dashboards.

Panda Remit

Asia-focused digital remittance, especially around Greater China corridors. Holds transfer history and FX rate data; complements WireBarley's Hong Kong and mainland-inbound flows.

TerraPay

Cross-border payments network used by banks, fintechs and MTOs. Holds settlement, routing and partner data; an important upstream when comparing WireBarley's direct corridors against network reach.

Remessa Online

Brazil-headquartered global remittance for individuals and SMEs. Holds transfer, FX and recipient data on Brazilian outbound and inbound legs; pairs naturally with WireBarley for global accounting consolidation.

About us

OpenFinance Lab is an independent studio focused on remittance, OpenBanking and protocol-analysis work. Our team comes from licensed payment institutions, MTOs, mobile-banking app teams and cloud security. We have shipped end-to-end integrations across Europe (PSD2 / 6AMLD), the US (FinCEN / OFAC perimeter), and Asia-Pacific (MAS, BSP, BNM) and are familiar with how remittance apps such as WireBarley actually package their FX, KYC and corridor logic.

• Remittance, digital banking, payroll and cross-border clearing
• API gateways, webhook receivers and idempotent retry stacks
• Custom Python, Node.js and Go SDKs with test harnesses
• Full pipeline: scoping → protocol analysis → build → validation → compliance review
• Source code delivery from $300; pay-per-call hosted API as an alternative

Contact

To request a quote or hand over your target app and requirements, open our contact page. We typically reply within one business day in Asia-Pacific and Europe time zones.

Contact page

Engagement workflow

1. Scope confirmation: which corridors, which endpoints (login, history, payout, FX, webhooks).
2. Protocol analysis and API design (2–5 business days, complexity-dependent).
3. Build and internal validation against sandbox or recorded fixtures (3–8 business days).
4. Docs, samples, Postman collection and test cases (1–2 business days).
5. Typical first delivery: 5–15 business days; partner approvals on OpenBarley may extend timelines.

FAQ

What do you need from me to start a WireBarley integration?

How long does delivery take?

How do you handle compliance and privacy on remittance data?

Can you cover both Android and iOS?