Tigo
For operators facing Paraguayan and Bolivian players, Tigo is a secondary local rail—valuable for reaching the cash-preferring, card-light segment, not a stack you build on—accessed almost always through a local aggregator at an indicative 3–5% merchant fee (QR/payment-link, Paraguay, April 2026), on top of the wallet's own cash-in/cash-out charges. Tigo Money is Millicom's mobile financial service and Latin America's largest mobile money operation, serving more than 15 million wallet users across the region. Treat it as a local option that broadens funnel coverage in specific GEOs, never as a substitute for cards, bank transfers, or your orchestration layer.
WHY TIGO WIDENS A LATAM CASHIER
Tigo earns its place in a cashier for one reason: reach into a player base that cards and bank rails miss. Across Paraguay, Bolivia, and parts of Central America, a large share of adults transact primarily in cash or through a phone-linked wallet rather than a debit card. For an operator, that gap is the whole argument—a player who cannot fund with Visa can fund with Tigo Money in seconds from a balance tied to their mobile number. It is not, however, a standalone global solution: Tigo is a country-specific rail with no footprint outside Millicom’s LATAM markets, so it belongs alongside cards, local bank transfers and alternative payment methods, never in place of them.
Where Tigo reaches players cards miss
Tigo‘s case rests on the specific players and cost dynamics of its home markets, so read each advantage against Paraguay and Bolivia rather than as a general claim.
Bypasses low card-approval rates. Issuer approval for gambling MCCs is notoriously weak in the region; Tigo sidesteps it by reaching the unbanked and underbanked directly. In Paraguay, it is also one of the payment systems licensed operators are expected to integrate—a signal of local legitimacy, not just convenience.
A wallet players already use. Funding comes from a balance players already use for airtime, bills, and remittances, in local currency, with no card data exposed and no bank account required. Wallet-to-wallet movement is instant and, on Tigo‘s own rails, free.
Priced like local wallet commerce. Merchant QR/payment-link acceptance runs at an indicative 3–5% in Paraguay (April 2026), with wallet-to-wallet transfers free and cost landing on cash-in and cash-out—which for the right GEO can beat the all-in cost of decline-heavy card traffic.
One connector via a local PSP. You don’t integrate Tigo directly; you reach it through a local PSP or aggregator that already exposes it as a casino payment option, so the work is a single connector returning wallet identity, a transaction reference, and a webhook status model for reconciliation.
The constraints that keep Tigo secondary
Each limitation below is a reason Tigo supports a cashier rather than anchors one, so size them before you promote it.
Access is intermediated. Tigo Money is a telco wallet, not a merchant acquirer with a gambling program. There is no public, operator-facing gambling API—you depend on a local aggregator’s commercial relationship, and that dependency shapes pricing, payout support, and settlement.
GEO restriction is severe. Tigo exists only in Millicom’s nine LATAM markets, and Tigo Money as a live consumer wallet is concentrated in Paraguay, Bolivia, Guatemala, Honduras, and El Salvador. Outside that set it is simply unavailable. The historic African “Tigo Cash / Tigo Pesa” wallets now belong to other owners after Millicom’s 2022 Africa exit and are not the same product.
Low transaction ceilings. KYC-tiered wallets cap balances and monthly throughput—e.g., El Salvador’s per-transaction and monthly limits sit around US$365 and US$1,825 for lower tiers. High-stakes players will hit walls that cards and bank transfers do not impose.
Regulatory exposure varies sharply by GEO. In Bolivia, online gambling sits in a legal gray zone with no local licenses; in Paraguay, a new concession regime is still bedding in. If you’re unsure whether a target market’s rules actually permit wallet-funded play, the GR8_TECH team can map Tigo against the current license position before you commit it to the cashier.
WHERE TIGO MONEY WORKS AS A GAMBLING RAIL
Tigo Money’s usable footprint for iGaming is narrower than Millicom’s overall telecom map—what matters is where the wallet is both widely held and reachable as a gambling rail through a local provider. The table below summarizes the markets that matter, and the caveats attached to each.
| Market / GEO | Tigo availability | Operator considerations |
| Paraguay | Strong. 3M+ active wallets; explicitly named among the local payment systems licensed operators integrate (Tigo Money, Zimple, bank transfer). | New concession regime (Law 7438/2025); online-casino tender still pending mid-2026. Access via local aggregator; expect .bet.py domain and DNIT/CONAJZAR oversight. |
| Bolivia | Present and actively used at casinos for deposit and withdrawal; KYC-tiered accounts (SEGIP-validated). | Online gambling is a gray market under Law 060/2010—no local online licenses; offshore tolerated but domestic operations pursued. Crypto gambling banned. Player tax 15%. |
| Guatemala | Live consumer wallet; part of the Tigo Money Visa footprint. | Gambling framework is thin; confirm operator licensing route and whether an aggregator carries Tigo for gaming MCCs. |
| Honduras | Live wallet; monthly limits tiered (≈ L30,000–50,000). | Similar to Guatemala—verify aggregator support and payout capability per operator. |
| El Salvador | Live wallet with published fee schedule (bill-pay $0.25, top-up $0.05); low per-txn / monthly caps. | Small ceilings constrain deposit sizes; check aggregator gambling acceptance. |
💡 Tigo Money is not available outside Millicom’s LATAM markets—there is no Tigo rail in Brazil, Mexico, Argentina, Chile, Peru, the US, Europe, or Asia, and the former African Tigo wallets are separate businesses today. For those GEOs, you need Pix, SPEI, local bank transfer, cards, or region-specific alternative payments instead.
Tigo and Paraguay’s concession regime: what operators need to know
Paraguay is the clearest case for Tigo as a casino payment method, but it is also a market mid-transition, so the regulatory reading matters as much as the wallet coverage.
⚠️ Authorization runs through CONAJZAR under the DNIT (Law 7438/2025, Decree 3846/2025); the model is a limited concession—up to three operators per vertical—and the online-casino tender was still pending as of mid-2026.
⚠️ Licensed operators are expected to run on Paraguayan payment systems—Tigo Money, Zimple, and local bank transfers—and to use the .bet.py domain; sites offering only obscure e-wallets or crypto are a red flag to the regulator.
⚠️ Player winnings carry an 8% tax and operators a 10% corporate income tax plus a variable concession canon—build these into unit economics before promising Tigo as a headline funding option.
DEPOSITS, WALLET PAYOUTS AND AGGREGATOR SETTLEMENT
Tigo‘s behavior in a cashier depends heavily on the market and the aggregator in front of it, but the two-way question—can you pay out to it, not just take deposits—is the one to settle first. In Paraguay and Bolivia, Tigo Money is used for both deposits and withdrawals; in the smaller Central American markets it is more reliably a deposit rail.
| Area | Operator view |
| Deposit availability | Strong in Paraguay and Bolivia; live but thinner in Guatemala, Honduras, El Salvador. Always mediated by a local PSP/aggregator. |
| Withdrawal availability | Supported in Paraguay and Bolivia (player cash-out to wallet); confirm per-aggregator and per-GEO—not guaranteed everywhere. |
| Typical deposit speed | Near-instant. Player confirms via SMS/PIN and funds credit in seconds. |
| Typical withdrawal speed | Fast where supported—wallet credit is near-instant once the operator/aggregator releases the payout; agent cash-out is a separate player step. |
| Settlement model | Operator settlement is via the aggregator, not Tigo directly—typically D+1 to D+7 in local currency (Guaraní, Boliviano, USD in El Salvador). Confirm cadence and currency in the commercial contract. |
| Deposit-only risk | Real in the smaller GEOs. If your aggregator only enables Tigo deposits, players fund locally but must be paid out on another rail—surface this before launch. |
| Deposit–withdrawal asymmetry | Common. Deposit acceptance is broader than payout support; wallet balance and monthly caps can block larger withdrawals even where payouts exist. |
| What depends on the setup | Which GEOs are live, whether payouts are enabled, fees, limits, and settlement—all set by the aggregator relationship, not by Tigo Money itself. |
Paying out to a Tigo wallet, market by market
Tigo is two-way in its core markets but only as a payout destination, not an independent payout processor—the operator (or its aggregator) initiates the disbursement and the funds land in the player’s Tigo wallet, from which the player can cash out at an agent. That distinction matters for reconciliation and for responsible-payout controls: you are crediting a wallet tied to a specific mobile number and cédula, which helps with same-account payout rules, but liquidity and prefunding sit with the aggregator. Where a market or provider only supports deposits, treat Tigo as a funding-in rail and pair it with a payout method (bank transfer, or another wallet) so you never advertise a withdrawal channel you can’t honor. If you need to confirm whether your target provider actually enables Tigo payouts in a given GEO, the GR8_TECH payments team can check it against your shortlist.
COSTS, LIMITS AND APPROVAL
The numbers below are indicative benchmarks drawn from public wallet pricing and local acceptance data—treat them as a starting point for commercial negotiation, not a rate card.
| Item | Indicative value |
| MDR / transaction fee | ~3–5% merchant acceptance (QR / payment-link, Paraguay, Apr 2026); wallet-to-wallet free. Payouts often priced separately by the aggregator. |
| Rolling reserve | Not a Tigo construct; if applied, it comes from the aggregator/PSP underwriting your gambling MCC—typical iGaming reserves run 5–10% for 90–180 days. |
| Settlement cadence & currency | Aggregator-dependent, typically D+1…D+7; local currency (PYG, BOB, USD in SV). |
| Deposit limits | Tiered by KYC level. Lower tiers are small—e.g. El Salvador ≈ US 365/txn, ≈ US 1,825/month; higher tiers require in-branch ID verification. |
| Withdrawal limits | Governed by the same wallet tiers and monthly caps; large payouts may need to be split or routed to another rail. |
| Indicative approval rate | High for wallet-native flows (no issuer in the loop): most declines are wallet-balance, expired-SMS/PIN or KYC-tier ceilings rather than risk declines. Reduce them by showing limits up-front and prompting cash-in before deposit. |
| FX/repatriation | If you settle in EUR/USD but collect in PYG/BOB, factor FX and treasury/prefunding cost—a non-trivial line for a Guaraní- or Boliviano-denominated flow. |
BUILDING A PARAGUAY-BOLIVIA STACK AROUND TIGO
Tigo is one local rail, and on its own it covers neither every player nor every GEO in a LATAM-facing cashier. The point of the stack around it is to catch the card-holding players it doesn’t serve, cover the markets it doesn’t reach, and guarantee a payout path where Tigo is deposit-only. The complementary layers below are the ones that actually matter for a Paraguay/Bolivia-centerd build—not a generic “add everything” list.
| Complementary payment layer | Why operators need it | Priority markets |
| Local bank transfer / Zimple (PY) | The other rail licensed Paraguayan operators integrate; covers players who prefer bank rails and larger-value flows Tigo’s caps block. | Paraguay |
| Cards (Visa/Mastercard) via local acquirer | Reaches banked players and higher-limit deposits; the fallback when a wallet cash-out isn’t available. | All LATAM GEOs |
| Alternative wallets/vouchers | Redundancy against a single-wallet dependency and single-aggregator risk. | Bolivia, Central America |
| Payout rail (bank transfer) | Guarantees a withdrawal path where Tigo is deposit-only, so you never advertise an unavailable cash-out. | Guatemala, Honduras, El Salvador |
| Orchestration/routing layer | Lets you add Tigo per GEO, route around outages, and reconcile wallet + card + bank flows in one place. | Region-wide |
💭 The commercial reality is that Tigo‘s value compounds only inside a well-built cashier: it lifts deposit conversion in specific GEOs, but the margin comes from routing each player to the cheapest rail that will actually approve. That routing logic is exactly what an orchestration setup from the GR8_TECH team is for.
Reaching Tigo through a local aggregator
Tigo Money has no operator-facing gambling API, so access is never direct—you connect through a local PSP, aggregator, or orchestrator that already carries Tigo as a casino payment method. In practice, that is one connector to integrate rather than a wallet integration project, days to a few weeks of work, most of it the provider’s onboarding rather than your engineering. Coverage for Paraguay and Bolivia is delivered by regional aggregators and local PSPs that bundle Tigo alongside bank transfer and cards; the specific shortlist depends on your license footprint, and GR8_TECH can name the gambling-capable providers that carry Tigo for your markets during scoping.
On reconciliation, a Tigo transaction through an aggregator typically returns the payer’s wallet identifier (mobile-number-linked), a unique transaction reference, and a webhook status model (pending → confirmed → settled); confirm the settlement report format and whether payer identity is passed through for AML and same-account payout checks. Underwriting is the gate, not code: expect the aggregator to ask for your gambling license (or a clear read on the market’s legal status), ownership and UBO documents, target-GEO list, processing history and flow diagrams, with a realistic lead time of a few weeks.
FRAUD AND RISK ON AN INTERMEDIATED WALLET
Because Tigo is a wallet with no card issuer in the loop, its risk profile differs from card processing—chargeback fraud largely disappears, but ownership, mule, and bonus risks rise, and most of the mitigation stays in the operator’s own fraud stack.
Third-party funding/ownership mismatch. A wallet is tied to a mobile number and cédula, but a player may fund from someone else’s wallet. The wallet’s KYC helps, but matching payer identity to the account holder stays your responsibility.
Mule accounts / circular funding. Cheap, instant wallet-to-wallet movement is convenient for players and for launderers. Monitor for rapid deposit-withdraw cycling and clusters of accounts funded from the same wallet.
SMS/PIN account takeover. Wallet access via SMS and PIN is phishable; a compromised wallet can fund an account the real owner never opened. Step-up checks on new payout destinations reduce exposure.
Withdrawal-destination substitution. Ensure payouts return to the same verified wallet used for deposit, not a newly supplied number—a core same-account control.
💭 The provider (Tigo and the aggregator) handles wallet-level security and basic KYC tiers; everything downstream—RG, AML transaction monitoring, ownership matching—remains the operator’s cost and obligation.
COMPLIANCE: WHAT THE AGGREGATOR DOESN’T COVER
Using Tigo through an aggregator reduces your integration and settlement workload; it does not transfer your regulatory obligations. The split below is the one to hold in mind: the provider secures the rail; you keep the license-level duties.
| Domain | Provider position | Operator implication |
| PCI DSS | No card PAN in wallet flows; scope is reduced vs cards. | Still applies to any card rails you run alongside Tigo. |
| SCA / Authentication | Wallet SMS/PIN authenticates the payer. | Not a substitute for your own login and payout step-up controls. |
| AML & KYC | Tigo runs tiered wallet KYC (e.g. SEGIP validation in Bolivia). | You keep player KYC/AML and transaction monitoring at operator level. |
| Account ownership | Wallet is number- and cédula-linked. | You must match wallet identity to the registered player; enforce same-account payouts. |
| Responsible gambling | Out of scope for the wallet. | Deposit limits, self-exclusion and RG tooling are entirely yours. |
| Data protection | Local data-protection regimes apply per GEO. | Ensure your aggregator contract covers lawful data handling in each market. |
| Transaction monitoring | Aggregator provides transaction data/webhooks. | Feeding it into your AML monitoring is on you. |
| Local gambling-payment restrictions | Varies: PY concession regime; BO gray market. | Confirm wallet-funded play is permitted before enabling it in a GEO. |
| Recordkeeping & reporting | Aggregator supplies settlement/txn reports. | Retain and reconcile per your license’s requirements. |
| Sanctions screening | Not performed for you. | Screen players and counterparties within your own compliance stack. |
TIGO: THE TL;DR
Before the detail fades, here is the decision compressed to its essentials for a LATAM-facing operator.
- Add it where it wins. Paraguay first—where Tigo Money is a named, expected payment system—and Bolivia with a clear-eyed read on the gray market.
- It’s a secondary rail, not a foundation. It reaches card-light players issuer-dependent methods miss, but caps, intermediated access, and patchy payout support keep it off the critical path.
- Confirm payouts before you promise them. Two-way works in Paraguay and Bolivia; elsewhere assume deposit-only until an aggregator proves otherwise.
- Price the whole picture. ~3–5% acceptance in Paraguay plus cash-in/cash-out charges, KYC-tier ceilings, and FX if you settle in EUR/USD.
- Run it behind orchestration. Pair Tigo with local bank transfer, Zimple, cards, and a guaranteed payout rail, and route each player to the cheapest rail that will approve.
If you’re weighing Tigo against the rest of a LATAM cashier, the GR8_TECH team can scope the aggregators that carry it for your GEOs and slot it into a payment gateway build alongside your other payment methods.
Share
