CROSS: REMIT & SHOP API integration (Korea remittance & OpenFinance)

Account login & KYC sync

Mirrors the CROSS app's authorization flow: phone-based OTP, OAuth-style token issuance, and refresh. Captures KYC status — passport image submission, ARC (Alien Registration Card) number verification, and the post-2024 enhanced identity check that allows sign-up even when a passport has expired.

Typical use: HR and payroll providers verifying that a foreign worker's CROSS account is in verified state before triggering an automated remittance.

Remittance history API

Paged transaction history with date range, corridor, status, and beneficiary filters. Each record exposes sender ID, beneficiary name and bank, destination country, sent amount (KRW), received amount and currency, mid-market reference rate, applied rate, fee, status (requested, processing, paid, refunded), and the underlying RippleNet or Tranglo reference where applicable.

Use: monthly statement export to Excel/JSON/PDF for accounting close, KOSI-style ledger feeds, and remittance corridor analytics.

Cross Wallet balance & top-up

Cross Wallet is the prepaid pouch CROSS introduced so users can pre-fund remittances and re-send refunded transactions instantly. The API exposes wallet balance, top-up source (bank deposit, card), refund inflow, and FX-locked balances. Webhooks fire on every balance change.

Use: treasury dashboards that aggregate prepaid float across CROSS, WireBarley Wallet, and Sentbe Pocket.

Points, referral & loyalty events

Stream of point-earning events: 10,000 points per accepted referral code, daily-attendance increments, and fee-waiver redemptions. Each event has a timestamp, source (referral, attendance, promo), and an idempotency key so loyalty engines do not double-count.

Use: CRM enrichment, churn signals, and loyalty consolidation across multiple Korean fintech apps.

Cross Shop order export

Cross Shop sells Korean goods (cosmetics, food, USIM top-ups, hometown products) to foreigners in their own language. The order API returns SKU, vendor, KRW price, foreign-currency display price, shipping country, address, payment method, and tracking URL.

Use: ERP sync for resellers, shopping behaviour analytics, and CRM segmentation.

Customer-care & support transcript

The CROSS app embeds in-language chat (Cross Call) for foreign workers. With user consent, transcripts and ticket metadata can be exported to Zendesk, Freshdesk, or a custom queue — useful for QA and dispute resolution audits.

1. Payroll → remittance automation for foreign workers

Business context. Korean factories, hospitality groups, and shipyards employ foreign workers who routinely remit a large share of payroll home. Today, HR teams hand off salary data and workers re-key it into CROSS each month.

Data & APIs. Payroll system pushes net pay and beneficiary references; we call CROSS login (token), confirm KYC=verified, fetch quote, create a remittance, and write back the reference and ETA.

OpenFinance mapping. Same pattern as PSD2 payment-initiation, adapted to Korea's small-amount overseas remittance license.

2. Multi-app remittance ledger for fintech aggregators

Business context. Foreign-worker community apps in Vietnam, Nepal, and the Philippines aggregate remittance flow across CROSS, WireBarley, Sentbe, GME, and Hanpass to give users a single view of "money sent home this year".

Data & APIs. Per-app transaction history APIs, normalized to a unified schema (sent_at, corridor, send_amount_krw, recv_amount, fee_krw, fx_rate, status).

OpenFinance mapping. Account-aggregation pattern from EU/UK OpenBanking, applied to non-bank licensed remittance providers.

3. AML / travel-rule monitoring for licensed corridors

Business context. Compliance teams must report remittances above the $10,000/year threshold to Korea's National Tax Service and follow FATF travel-rule logging.

Data & APIs. Streaming export of remittance and Cross Wallet events into a SIEM (Splunk, Datadog, or in-house). Each event carries beneficiary name, sender ID hash, country, amount, and originator institution.

OpenFinance mapping. Travel-rule plus AML transaction monitoring, supervised by the FSC and FSS.

4. Cross Shop ERP sync for cross-border resellers

Business context. Cross Shop sells Korean cosmetics, food, and USIM products to foreigners. Resellers in Vietnam and Indonesia want orders pushed into their ERP automatically.

Data & APIs. Order export endpoint with SKU, vendor, KRW price, shipping country, address, and tracking number; reconciles against Cross Wallet payments.

OpenFinance mapping. E-commerce open-data pattern — order history sharing under user consent.

5. FX-rate analytics & corridor pricing

Business context. Treasurers and market researchers want a feed of mid-market reference rate vs CROSS applied rate per corridor, to model spread, fee, and total cost-to-send.

Data & APIs. Per-quote snapshot (quoted_at, corridor, mid_rate, applied_rate, fee_krw), aggregated daily.

OpenFinance mapping. OpenData FX transparency, adjacent to World Bank Remittance Prices Worldwide.

Account login (OTP + token)

POST /api/v1/cross/login
Content-Type: application/json

{
  "phone": "+82-10-1234-5678",
  "country_code": "KR",
  "device_id": "dev-uuid-..."
}

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

Remittance history (paged)

POST /api/v1/cross/remit/history
Authorization: Bearer <ACCESS_TOKEN>

{
  "from_date": "2026-04-01",
  "to_date":   "2026-04-30",
  "corridor": "KR-PH",
  "page": 1, "page_size": 50
}

200 OK
{
  "items": [
    {
      "ref": "CR2026042812345",
      "sent_amount_krw": 500000,
      "recv_amount": 19850.40,
      "recv_currency": "PHP",
      "fee_krw": 5000,
      "fx_rate": 0.0397,
      "status": "paid",
      "beneficiary": {"name":"DELA CRUZ J.","bank":"BDO","account":"****4321"},
      "settled_at": "2026-04-28T11:42:10+09:00"
    }
  ],
  "next_page": 2
}

Cross Wallet webhook

POST https://your-server/webhooks/cross-wallet
X-Cross-Signature: sha256=...
Content-Type: application/json

{
  "event":  "wallet.balance_changed",
  "user_id": "u_8821",
  "delta_krw": -500000,
  "balance_krw": 120000,
  "reason":  "remit_outflow",
  "ref":     "CR2026042812345",
  "ts":      "2026-04-28T11:42:11+09:00"
}

# Recommended: verify signature, idempotency-key, retry
# with exponential backoff (max 5 retries / 24h)

Error handling & idempotency

Every write endpoint accepts an Idempotency-Key header so a retried remittance never double-spends. Errors follow a uniform shape: {"error":{"code":"KYC_NOT_VERIFIED","message":"...","trace_id":"..."}}. Common codes include KYC_NOT_VERIFIED, CORRIDOR_UNSUPPORTED, QUOTE_EXPIRED, WALLET_INSUFFICIENT, and RATE_LIMITED.

Korean regulatory framework

CROSS operates under Korea's Foreign Exchange Transactions Act and is supervised by the Financial Services Commission (FSC) and the Financial Supervisory Service (FSS). Its license — Small Amount Overseas Remittance Business No. 2018-11 — was issued in 2018 under the framework that opened cross-border remittance to non-bank fintechs in July 2017.

Reporting thresholds matter: remittances exceeding USD 10,000 per user per year are reported to Korea's National Tax Service (NTS), and AML obligations under the Act on Reporting and Using Specified Financial Transaction Information apply.

Privacy & data minimization

Our integrations follow Korea's Personal Information Protection Act (PIPA) and align with GDPR/CCPA equivalents for global use. We hash sender IDs at the boundary, store only what the customer needs, and document retention windows. FATF travel-rule logging is supported for in-scope corridors.

We never bypass app authentication. We do not scrape biometric data, and we refuse engagements that would breach user authorization or local law.

About OpenFinance Lab

We are an independent technical studio specializing in app interface integration and authorized API integration. Our team has years of hands-on experience in mobile fintech, protocol analysis, and Open Data, with engineers from banks, payment gateways, and cloud-platform teams. We routinely deliver Korea, Southeast Asia, EU, and US fintech integrations with proper licensing context.

• Financial and banking apps (transactions, statements, payments)
• E-commerce, food delivery, and retail apps (orders, payment, sync)
• Hotel, travel, and mobility apps (bookings, itineraries, verification)
• Social, OTT, and dating apps (auth, messaging, profiles)
• Source-code delivery from $300 — runnable API source plus full docs; pay after delivery upon satisfaction
• Pay-per-call hosted API — no upfront fee; ideal for usage-based teams

Contact

Send us your target app and concrete needs (login, statements, wallet, orders) and we will return a scope and timeline within one business day.

Open contact page

Engagement workflow

1. Scope confirmation: which CROSS surfaces (login, remit, wallet, points, shop) and which delivery format.
2. Protocol analysis and API design (2–5 business days).
3. Build and internal validation against a sandbox account (3–8 business days).
4. Docs, sample clients (Python and Node.js), and test cases (1–2 business days).
5. First delivery typically 5–15 business days; multi-corridor reconciliation may run 3–4 weeks.

FAQ

What does the CROSS: REMIT & SHOP integration export?

Is this integration compliant with Korean foreign exchange rules?

How long does delivery take?

Can I just call your hosted API instead of running source code?