TOPii sends cash across borders — here is how to reach its records

A TOPii order begins as a barcode the sender pays in cash at one of roughly 80,000 US partner stores, per the app's store listing, and then moves cross-border so the recipient collects it as cash, a bank deposit, or a wallet top-up in minutes. That two-leg shape — a domestic cash pay-in linked to a foreign payout — is the data worth integrating. The records sit behind an authenticated sender account: transfers, beneficiaries, the generated barcodes, live corridor quotes, and the in-app chat used to arrange a transfer. Reaching them from outside the app is what this brief covers.

The route we would take is authorized analysis of the app's own mobile interface, run against a consenting account, with the recipient-bank side handled through open-banking consent where a transfer lands in an account. Below: what each surface holds, the worked auth flow, the deliverables, and how the US remittance rulebook shapes the work.

Reaching a transfer from outside the app

Three routes apply to TOPii, and they are not equal. Here is what each one reaches and what we set up to run it.

Authorized analysis of the mobile interface

The app talks to its backend over a token-authenticated HTTPS interface. Working against an account the client consents to, we observe and document those calls — login and token refresh, the quote request, order creation, barcode issuance, transfer listing, and the chat endpoints — then rebuild them as a clean client. This reaches everything the sender app itself can see, including the cash-leg references that no statement export carries. It is the most complete route and the one we would build on. Access to a consenting test account is arranged with you at the start; nothing about it is yours to clear before we begin.

Open-banking consent on the payout side

When a recipient takes the money into a bank account, the credit shows up in that account's transaction feed. Where the receiving market has a live regime — for example a recipient bank reachable through an Account Information Services connection — we can read the settled credit under the account holder's consent. This confirms a payout independent of TOPii's own status field, which is useful for reconciliation, but it only covers the bank-deposit payout option, not cash or wallet collection.

User-consented session access

For a one-off pull or a low-volume sync, a sender can authorize access to their own account and we drive the documented interface on their behalf, holding the session under their consent. Lighter to stand up than a full client, durable enough for periodic exports, and bounded to exactly the fields the user agrees to share.

For most TOPii work the mobile-interface route carries the build because it is the only one that exposes the barcode pay-in, the chat, and the quote at the moment of sending; open-banking consent rides alongside it purely to verify bank-deposit payouts. We would not lead with the consent route unless the job is a single sender's export.

What TOPii holds per sender

The store-locator network — those partner pay-in points — is public reference data rather than per-user state, so we treat it separately from the consented surfaces above.

What lands in your repo

The output is a working integration, not a report. For TOPii that means:

• An OpenAPI specification covering the transfer, recipient, quote, barcode, and chat surfaces, with request and response shapes documented field by field.
• A protocol and auth-flow write-up: the token issue and refresh chain, header signing, and how an order transitions from quote to barcode to disbursement.
• Runnable source for the key endpoints in Python or Node.js — list transfers, fetch a transfer with both legs, pull quotes, read a chat thread.
• A normalized schema that flattens the two-language receipts and the two-leg order into one consistent model.
• Automated tests against recorded fixtures, plus error-path handling for token expiry, expired barcodes, and rate-limit responses.
• Interface documentation and a short data-retention note covering consent logging and field minimization.

A worked example: a transfer with both legs

Illustrative shape only — exact field names are confirmed during the build against the live interface. It shows the pattern that matters for TOPii: one order, two settlement events.

POST /v2/auth/token
{ "grant_type": "refresh_token", "refresh_token": "<stored>" }
=> { "access_token": "<jwt>", "expires_in": 1800 }

GET /v2/transfers/{id}
Authorization: Bearer <jwt>
=> {
     "id": "trf_8842",
     "corridor": "US->DO",
     "send": { "amount": 200.00, "currency": "USD", "fee": 3.99 },
     "fx_rate": 58.6,
     "payin":  { "method": "cash_barcode", "ref": "BC-77f2",
                 "expires_at": "2026-06-09T23:59:00Z", "status": "paid" },
     "payout": { "method": "bank_deposit", "country": "DO",
                 "amount": 11491.10, "currency": "DOP", "status": "delivered" },
     "receipt_locale": "es-US"
   }

# error handling worth wiring from day one
# 401 -> refresh token and retry once
# 409 expired_barcode -> re-issue voucher, do not duplicate the order

Authorization and the remittance rulebook

TOPii moves consumer money out of the United States, so the relevant frame is the CFPB Remittance Transfer Rule — an amendment to Regulation E under the Electronic Fund Transfer Act — together with FinCEN money services business registration and state money transmitter licensing. Regulation E is also why a sender may see Spanish receipts: disclosures must come in the language the service is marketed in, and TOPii markets in Spanish. The dependable basis for the integration is narrower and simpler than any of that: the account holder's own authorization to reach their own records. We build on that consent, keep consent and access logs, pull only the fields a job needs, and work under an NDA where the client wants one. Consent scope and revocation are honored — when a user withdraws access, the sync stops and stored credentials are cleared.

What we plan for on a TOPii build

Two things about this app shape the engineering, and we handle both rather than hand them back as conditions.

• The order is genuinely two-legged. A barcode can be issued and never paid, paid but not yet disbursed, or fully delivered — and the cash pay-in and the foreign payout settle on different clocks. We model them as separate events with their own status and references so a stalled cash leg never reads as a completed transfer, and reconciliation stays honest.
• Payout options differ by destination country: the same recipient may be eligible for bank deposit in one corridor and cash-only in another. We map the per-corridor payout rules so the integration presents the right options per recipient instead of assuming one shape, and we wire a periodic re-check so a front-end change to the quote or chat flow is caught and patched in maintenance.

Access to a consenting account or sandbox is arranged with you during onboarding; the build runs against it. That setup is our step, not a checklist you complete first.

Where teams plug this in

• A fintech reconciling outbound remittances into its own ledger, matching each cash pay-in to its foreign payout.
• A compliance team archiving Regulation E receipts and the linked chat thread as one audit record per transfer.
• A comparison or treasury tool reading live corridor quotes to track TOPii's rate and fee against peers.
• A CRM keeping a sender's recipients and transfer status in sync without manual re-entry.

Screens we mapped

From the app's published store screenshots. Open each to inspect the surface.

How this brief was put together

Checked on 2026-06-07 against the app's own Play and App Store listings for the cash-barcode flow, store count, payout options and chat feature; against the TOPii corporate site for its US-to-Latin-America corridors; and against CFPB and FinCEN primary pages for the remittance and money-services framing. Routes and field shapes are described from how the app presents the flow, not from a confirmed teardown, and are validated during the build itself.

• TOPii on Google Play (com.topii.shopper)
• TOPii on the App Store
• CFPB Remittance Transfer Rule resources
• FinCEN money services business definition

Mapped by the OpenBanking Studio integration desk · June 2026.

The remittance corridor it sits in

Same-category apps an integrator often unifies alongside TOPii. Listed for context, not ranked.

• Remitly — bank, cash-pickup and wallet payouts across many corridors; large delivery-option catalog.
• WorldRemit — bank deposit, cash pickup and mobile money, strong in Africa and Latin America.
• Wise — multi-currency accounts and transparent fee data per transfer.
• Western Union — global agent network with cash pickup in 200+ countries.
• Taptap Send — low-fee transfers to Africa, Asia and Latin America.
• Pangea Money Transfer — cash pickup at Oxxo, Coppel and Banco Azteca, debit and bank delivery.
• Sendwave — fast mobile-money and bank payouts with fee-light corridors.
• Félix Pago — WhatsApp-driven transfers to Mexico, Guatemala and Honduras.
• Remmesa — person-to-person transfers to roughly a dozen countries with retail cash payout.
• Ria Money Transfer — broad cash-pickup and bank-deposit network.

Questions integrators ask about TOPii

Can the cash pay-in leg be separated from the cross-border payout in the data?

Yes. A TOPii order carries two distinct states: the barcode voucher the sender pays in cash at a partner store, and the disbursement to the recipient's bank, wallet, or cash point abroad. We model them as separate events with their own references and timestamps so a ledger can reconcile pay-in against payout independently.

Does the built-in chat come through as structured messages?

The coordination chat is tied to a recipient thread rather than a free global inbox. During protocol analysis we capture each message with its thread id, sender, timestamp, and the linked transfer, so a support or archival tool can read conversations alongside the transfer they refer to.

Which US rules cover pulling a sender's TOPii remittance records?

Cross-border consumer transfers from the US sit under the CFPB Remittance Transfer Rule, an amendment to Regulation E under the Electronic Fund Transfer Act, alongside FinCEN money services business registration and state money transmitter licensing. The dependable basis for the integration is the account holder's own authorization to reach their records; we keep consent logs and minimize the fields pulled.

Do you handle the Spanish-language receipts TOPii surfaces to senders?

Regulation E requires disclosures and receipts in the language used to market the service, so a sender may receive Spanish receipts. We normalize the receipt fields — amount sent, fees, exchange rate, total to recipient — into a single schema regardless of the display language, and keep the original text for audit.

On commercials: the source-code engagement starts at $300, where you get the runnable client, the OpenAPI spec, tests and the interface docs, and you pay after delivery once the integration works for you. The other model is the hosted API — you call our endpoints for TOPii and pay per call with nothing upfront. Either way the build runs in a one-to-two-week cycle. Tell us the app and what you want out of its data and we will scope it — start at /contact.html.