Owners, operations leaders, Support teams, and launch managers
Aplauso country and language support
Use the living planning matrix for core-platform countries, language coverage, guest currency display, payout routes, Tap to Pay, and future card programs. Planning rows are not live availability.
Complete planning matrix
The current country planning matrix is maintained in the Mission Control knowledge base. It is a planning target and never a live-availability claim.
- Route A and Route B are planning classifications, not authorization.
- A country row cannot replace an unpaused, complete country-release record.
- Connect may be one eligible route, but Wallet must show the route that passes the current checks.
How to read status terms
- Current support requires a completed release record and authenticated evidence.
- Launch target, Global Payouts candidate, and Tap to Pay capability market are planning states.
- Watchlist and unavailable states must not be described as supported or live.
Local charge currency and visitor display
- The property charge remains local.
- Visitor presets are rounded display choices only.
- The final review amount must be exact and local before authorization.
Global Payouts tourism planning
- Local-bank, wire payout, Connect-eligible, and watchlist statuses are separate.
- A candidate route is not an enabled recipient payout route.
- Wallet shows only the route and destination that pass current checks.
Core language set and future coverage
- The core platform uses English, Spanish, and French with English as the approved fallback.
- Guest kiosk language coverage does not expand operator, mobile, or payout availability.
- New locale claims require native review and release evidence.
Country gate and surface separation
- Country release, account onboarding, payout route, app distribution, website routing, and Support publication are separate gates.
- A planning row cannot authorize a route, currency, provider, or bank destination.
Conditional Tap to Pay layer
- Tap to Pay requires its own device, build, merchant, provider, legal, and market evidence.
- When unavailable, use Share or a browser Reward Code instead of routing guests to Wallet.
Future card issuing layer
- Issuing is a separate future program and balance.
- It is not a current payout method and does not authorize a country or withdrawal route.
The practical path
- 1
Start with the planning matrix and treat every route or country row as a launch target, not a live-support statement.
- 2
Verify the country checks, account or destination setup, enabled capabilities, payment and currency decisions, tax, legal, Support, risk, and authenticated live evidence.
- 3
Keep the local charge currency separate from optional visitor display presets. The review screen must show the exact local amount before payment authorization.
- 4
Treat Global Payouts as a separate route. Local-bank candidates, wire payout candidates, and watchlist countries are not automatically active.
- 5
Evaluate Tap to Pay and future Issuing through their own provider, merchant, device, legal, risk, and live-test gates.
Common questions
Does a guest kiosk language mean that Aplauso operates in that country?
No. Guest language and operator availability are separate decisions. A guest may use a supported kiosk language while local operator onboarding is not available.
Does a country in the matrix mean it is already available?
No. The matrix is a planning target, not production authorization. A country may be announced only after its onboarding, payout, compliance, Support, and authenticated live-evidence gates are complete.
What must be checked before announcing a country?
Check the country release, active route and capabilities, payout destination, payment and currency decisions, tax, legal, Support, risk, app and website routing, localized copy, and an authenticated controlled live payment and payout test.
Does a visitor currency change the charge currency?
No. The property charges in its local currency. Visitor presets only help guests choose; the review screen must show the exact local amount, fees, total, currency code, and local-charge disclosure.
Do Global Payouts, Tap to Pay, or future Aplauso cards make a country available?
No. They are separate programs and routes. Each needs its own provider approval, account setup, legal and operational review, risk controls, and authenticated tests before it can be announced.
Go deeper with the knowledge base
Use the detailed guide that matches your workflow, or ask the Aplauso assistant a specific question.