Six payment rails, five currencies, one integration

Reaching Osmo's payment data across six rails

Three integration routes apply to Osmo's data. Each reaches a different slice; the first covers everything.

Authorized interface integration (recommended)

We map Osmo's authenticated mobile and web traffic, document the request/response structure for every data surface, and deliver a client library that reproduces the session lifecycle — login, token refresh, device binding — and queries transfers, pocket balances, card activity, Bitcoin positions, and FX conversions. This route covers every domain the logged-in user can see. It is the most complete and the most durable.

User-consented credential access

The account holder provides their Osmo credentials under a documented consent agreement. The integration operates within that user's session, scoped and logged. Best suited when a business needs to sync its own Osmo account rather than a third party's.

Native export as supplement

If Osmo exposes downloadable receipts or transaction exports within the app, we parse and normalize those as a fallback for any domain that proves difficult to reach via the primary route. Useful but limited in scope.

What sits behind an Osmo login

Behind a logged-in Osmo session, six data domains are available. The table maps each to its origin, granularity, and typical integrator use.

FinCEN, the Bitcoin Law, and your consent

HODL Group LLC — Osmo's operating entity, per its Play Store and App Store disclosures — holds FinCEN registration as a money services business in the US. Bitcoin services run through OSMO El Salvador S.A. de C.V., licensed under El Salvador's Bitcoin Law and supervised by the Superintendencia del Sistema Financiero (SSF). Osmo's home market is Guatemala, where the Superintendencia de Bancos (SIB) oversees financial entities. Costa Rica operations fall under SUGEF.

For data access, the dependable basis is the account holder's own authorization. We operate under documented consent: access is scoped to the domains the customer needs, consent is recorded and revocable, and data handling follows the AML/KYC standards the app itself enforces. NDAs are arranged where the client requires them.

Where local data-protection law applies — Guatemala's access-to-information framework, Costa Rica's personal data protection act, El Salvador's privacy provisions, US state-level statutes — we scope collection to the minimum necessary and maintain deletion schedules aligned with the client's retention policy.

The runnable source and specs for Osmo

The delivered package for an Osmo integration includes:

• OpenAPI specification covering each data domain — transfers, balances, card activity, BTC/Lightning, FX conversions, payee directory. Fields, types, and enumerations reflect Osmo's actual response structures.
• Protocol and auth-flow documentation — the full session lifecycle: login, token issuance, refresh, expiry. If Osmo uses device fingerprinting or biometric gating, the report documents the chain and the replay strategy.
• Runnable client library (Python or Node.js) with methods for each data surface. Includes pagination for transfer history, real-time balance polling, and Lightning invoice capture.
• Automated test suite — integration tests that validate field structure, status codes, and error handling against a consenting account. The suite doubles as a change-detection layer.
• Interface documentation — annotated request/response examples for every endpoint, with notes on rate limiting, idempotency, and retry behavior observed in Osmo's backend.
• Compliance and data-retention guidance — consent-scope template, data-minimization recommendations, deletion procedures aligned with the relevant privacy regimes.

Querying Osmo's cross-border transfer log

A typical query against Osmo's transfer surface. Exact paths are confirmed during the build.

# Illustrative — exact paths confirmed during the build
import httpx

async def fetch_transfers(client: httpx.AsyncClient, token: str,
                          start: str, end: str, cursor: str = None):
    params = {"from": start, "to": end, "limit": 50}
    if cursor:
        params["cursor"] = cursor
    resp = await client.get(
        "/v1/transfers",
        params=params,
        headers={"Authorization": f"Bearer {token}"}
    )
    resp.raise_for_status()
    body = resp.json()
    # Each record: id, amount, source_currency, target_currency,
    # fx_rate, rail (ACH|WIRE|CLABE|PIX|SINPE), beneficiary,
    # status, created_at
    return body["data"], body.get("next_cursor")

The response normalizes every rail into the same schema. A rail field distinguishes ACH from CLABE from PIX; the rest of the fields — amount, currencies, rate, beneficiary, status — are uniform.

What the build accounts for

Each payment rail Osmo supports uses a different identifier format: routing-plus-account for ACH, 18-digit CLABE for Mexico, PIX keys in four formats (CPF, CNPJ, email, phone, random) for Brazil, IBAN or SINPE Móvil phone numbers for Costa Rica. We normalize all of these into a single transfer schema with a rail discriminator, so downstream systems don't need to branch on country.

Lightning payments settle in seconds and produce no persistent on-chain record. The integration captures the BOLT-11 invoice, preimage, and satoshi amount at event time and stores them alongside on-chain transactions, so the complete BTC ledger is available through one query path. Without this, Lightning activity is invisible to any system polling on-chain data alone.

Osmo's real-time balances per currency pocket can shift mid-session when an FX conversion or inbound transfer lands. We design the sync to snapshot balances atomically per poll cycle and flag any in-flight conversions, so the consuming system doesn't see a stale USD pocket while the GTQ pocket has already moved.

Scenarios that drive an Osmo integration

Remittance reconciliation for a payroll provider. A US-based company pays contractors in Guatemala and Costa Rica through Osmo. The integration pulls the transfer log nightly, matches each payout against the payroll system's disbursement records, and flags unmatched or stuck transactions.

Crypto tax reporting for an accounting firm. A firm's client uses Osmo to buy and send Bitcoin. The integration exports the full BTC and Lightning activity feed, converts satoshi amounts to USD at the transaction-time rate, and produces a tax-lot report compatible with standard filing formats.

Multi-currency treasury dashboard. A business holds USD, GTQ, and CRC pockets in Osmo alongside accounts at other providers. The integration feeds Osmo's pocket balances and FX conversion history into a consolidated treasury view, updated every fifteen minutes.

Osmo's interface in practice

Production screenshots from Osmo Money's current build, showing the surfaces the integration reaches.

Cross-border and crypto apps in these corridors

Remitly — handles high-volume US-to-LATAM remittances with bank deposit, cash pickup, and mobile wallet delivery. Holds transfer records, recipient details, and delivery-status tracking per corridor.

Wise — multi-currency accounts with borderless debit cards and mid-market FX rates. Maintains transfer history, fee breakdowns, and balance snapshots across dozens of currencies.

Xoom — PayPal's remittance arm, covering bank deposit and cash pickup across Latin America. Transfer records include sender/receiver details, FX rates, and delivery status.

Félix — WhatsApp-based remittance to Mexico, Guatemala, and Honduras, now using stablecoin rails via dLocal for near-instant settlement. Transfer data is lightweight but high-frequency.

Strike — Bitcoin and Lightning-native payments with direct USD-to-BTC conversion and cross-border sends. Holds Lightning invoice history and on-chain transaction logs.

Bitso — the largest crypto exchange in Mexico, also offering cross-border payment infrastructure. Holds trade history, fiat deposit/withdrawal records, and crypto balances.

Chivo Wallet — El Salvador's government-backed Bitcoin wallet. Holds BTC balances, Lightning transactions, and USD conversion history under the country's Bitcoin Law framework.

Ria — traditional remittance network with agent locations across LATAM. Transfer records include corridor, delivery method, and agent-level tracking data.

Sources and review date

This assessment checked Osmo Money's Play Store and App Store listings, the osmomoney.com site (including its about page), LatAm Fintech Co's coverage of Osmo's Costa Rica expansion, and the IBEX Mercado partnership report on Nasdaq. Regulatory basis was verified against FinCEN's MSB registration guidance and El Salvador's Bitcoin Law documentation.

Integration mapping by OpenBanking Studio, June 2026.

Osmo-specific questions

Can the integration pull transfers from all six of Osmo's payment rails in one call?

Yes. The delivered source normalizes ACH, wire, CLABE, PIX, SINPE, and SINPE Móvil into a unified transfer object. You query by date range and the rail type is a field on each record.

How does the integration handle Bitcoin and Lightning data differently from fiat transfers?

Lightning payments settle instantly and leave no on-chain record. We capture invoice metadata and the preimage at event time, then merge that with on-chain BTC transactions into a single crypto-activity feed in the delivered source.

Does the integration cover Osmo's Visa card transactions?

Yes. Card swipes — merchant name, category code, local-currency amount, and the conversion rate Osmo applied — are a separate data domain in the deliverable. Card freeze and unfreeze state is also queryable.

What happens when Osmo updates its app interface?

The delivered source includes a validation layer that flags structural changes in Osmo's responses. When a field moves or a new endpoint appears, the test suite catches it. The maintenance cycle addresses changes typically within days.

For Osmo's multi-rail payment data, source-code delivery starts at $300 — paid after delivery once you're satisfied with the build. If you'd rather not run anything yourself, our pay-per-call hosted endpoints let you query Osmo's data surfaces directly with no upfront fee. Delivery runs one to two weeks. Reach out to get started.