MACH
MACH is the consumer payment brand of MACHBANK de Bci, a Chilean digital bank backed by Banco Bci. Its merchant product, MACH Comercios, is a closed-loop QR and payment-button rail: only MACHBANK and Bci app users can pay, and funds settle to a Chilean bank account. For casino and sportsbook operators targeting Chile, MACH offers access to a well-established local payment ecosystem: MACHBANK currently puts the combined MACHBANK and Bci customer base at more than 6 million users.
Why Operators Choose MACH
For iGaming operators targeting Chile, MACH adds a familiar local payment option to the cashier without requiring players to enter card details or bank credentials. Payments are authorized from a phone in Chilean pesos (CLP), creating a straightforward deposit experience for players already using the MACHBANK or Bci ecosystem.
Its main value lies in local payment coverage rather than replacing an operator’s existing payment infrastructure. MACH can complement cards and other casino payment methods by giving Chilean players another way to deposit through a service they already recognize and use. For locally incorporated operators, that makes the MACH payment method particularly relevant as part of a broader mix of online casino payment options.
Strengths
MACH offers operators a relatively straightforward addition to an online payment system where MACH Comercios provides self-service onboarding, API documentation and a sandbox for testing, while built-in reporting and reconciliation tools help merchants track payments without adding unnecessary operational complexity.
Players, on the other hand, enjoy familiarity and speed. Payments are confirmed through the MACHBANK app without entering card details at checkout, making MACH a convenient addition to the alternative payment methods available to Chilean players. MACHBANK also positions its merchant checkout around payments completed directly from the MACHBANK and Bci apps.
Commercially, MACH publishes a base transaction fee of 1.8%, although actual pricing can vary by merchant.Â
đź’ As a closed-loop payment method, MACH avoids card-scheme chargebacks, while its API and transaction notifications provide the core technical infrastructure needed to integrate and monitor payments. We encourage you to contact the GR8_TECH team for more information on MACH availability and how it can fit into your existing iGaming payment setup.Â
Limitations
MACH works best as a complementary deposit method rather than a complete casino payment system. It supports local CLP deposits in Chile, but operators still need separate infrastructure for withdrawals, routing, failover and other payment methods.
The main limitations are:
- Gambling acceptance is not publicly confirmed. MACH does not publish specific eligibility or pricing terms for iGaming merchants, so operators should verify availability directly during onboarding.
- Pricing may differ from the advertised base rate. MACH publishes a 1.8% base transaction fee, but rates can vary by merchant profile, sales channel, and industry.
- Withdrawals require another solution. MACH does not publicly document a merchant payout product, so it cannot provide the full deposit-withdrawal loop.
- Transaction limits can restrict high-value deposits. MACH publishes daily limits that vary by payment route, making it less suitable for some VIP or high-stakes transactions.
- Coverage is Chile-specific. Payments are CLP-only and settle to a Chilean bank account, so MACH is not designed as a multi-market online gambling payment solution.
Regulation is another important consideration. Chile still does not have a licensing framework permitting commercial online gambling platforms, and the country’s gambling regulator continues to describe unlicensed online betting as illegal. For a bank-backed payment provider for gambling, this means merchant acceptance cannot be assumed and may change as Chile’s regulatory framework develops.
⚠️ Operators should also distinguish the absence of card-scheme chargebacks from the absence of disputes. Chile’s Ley 20.009 provides procedures for unrecognized electronic transactions, including claims covering transactions made before the customer reports the issue.
Overall, MACH’s limitations are manageable when it is treated for what it is: a Chile-specific deposit option within a broader payment stack, rather than a standalone iGaming payment solution.
MACH: Markets and Availability
MACH is a distinctly local payment method: its reach begins and ends in Chile. Within that market, however, its established consumer presence makes it potentially relevant for operators looking to strengthen their local payment coverage.
| GEO | Provider Presence | Relevance for Casinos and Sportsbooks | Typical Setup | Key Alternatives | Limitations |
|---|---|---|---|---|---|
| Chile — locally incorporated operator | Bank-owned wallet supervised by the CMF; 4.2 million users reported at the January 2025 rebrand; merchant product live with portal, API and e-commerce connectors for Shopify and VTEX | High as a secondary deposit option. Strong mobile recognition, immediate authorization, low headline cost, CLP-native | Direct merchant registration with MACH Comercios, or via a local aggregator that resells MACH alongside Webpay and Servipag | Webpay Plus and Redcompra via Transbank, Khipu, Fintoc, Servipag, Mercado Pago, Visa and Mastercard, bank transfer | Requires a Chilean company; SpA, “Empresa en un dĂa”, associations and foundations accepted, Ltda. and EIRL currently not. Deposits only. Daily caps of CLP 400,000 (QR) to CLP 1,000,000 (Onepay). Gambling acceptance not publicly disclosed |
| Chile — offshore operator, no Chilean entity | Reachable only indirectly: MACHBANK Visa card at a card checkout, or MACHBANK selected inside Webpay Plus through Onepay | Low as a distinct method; the transaction is a card or acquiring event, not a MACH payment method | Card acquiring through a cross-border PSP; MACH is not offered as a distinct alternative payment method by the major Latin American cross-border processors, whose Chile catalogs center on Webpay, Khipu, Servipag and Mercado Pago | Card acquiring, AstroPay, bank transfer, vouchers, crypto | No merchant contract, no settlement relationship, no reconciliation data from MACH. Issuer-side declines on gambling merchant categories are possible and outside operator control |
đź’ Operator note: Availability is more restrictive on the merchant side, as direct access requires a Chilean legal entity, while acceptance of gambling businesses is not publicly documented. For iGaming operators, the key question is therefore not where MACH is available, but how it can be accessed and under what conditions.Â
Deposits, Withdrawals and Settlement
MACH offers deposits, not a loop. The merchant API exposes payment creation, retrieval, QR generation, cancellation, reversal, refund and confirmation — and no disbursement endpoint. Capability also differs by access route: a directly contracted Chilean merchant receives webhooks, compensation reports, and refunds, while an offshore operator reached via cards or Onepay receives none of that from MACH.
| Area | Operator View |
|---|---|
| Deposit availability | Dynamic charges, reusable payment templates, payment links, static and dynamic QR, and API-generated payments delivered as a deeplink or checkout URL. Bci app users can pay the same charge. Strongest and only market: Chile |
| Withdrawal availability | No payout product is documented. The sole outbound movement is a refund bound to an original payment, capped at its value and expiring after 14 calendar days. Whether MACH offers merchant disbursements is not publicly disclosed and must be confirmed during commercial onboarding |
| Typical deposit speed | Seconds. The payment moves to completed on in-app authorization and the business-payment-completed webhook fires immediately; unpaid charges expire on a timestamp set at creation |
| Typical withdrawal speed | Provider transfer time is not applicable, since payouts leave via Chilean interbank transfer rather than MACH. Operator approval and first-withdrawal KYC remain the binding constraint and are entirely operator-controlled |
| Settlement model | Commission plus IVA is netted before compensation; the balance is credited to the merchant’s Chilean bank account normally within 24 hours, exceptionally up to 48. CLP only. A commission invoice is issued at period end with no further payment due |
| Deposit-only risk | Yes, and it is the normal configuration. Operators can accept MACH deposits while paying out by bank transfer, which is what Chilean cashiers in practice do |
| Deposit–withdrawal asymmetry | Instant in, materially slower out. The player experiences a same-second deposit and a multi-step withdrawal through a different instrument |
| What depends on the setup | Effective pricing by industry and channel; whether tokenised enrolments are enabled; whether manual payment confirmation is switched on, which is off by default and requires a support ticket; whether webhooks are subscribed to online, in-person or both channels; and automated state-change timings, which MACH will modify on request through an assigned account executive |
Withdrawal Availability
MACH supports deposits but does not provide a dedicated payout rail. This does not prevent a player from receiving their winnings in a MACHBANK account; it simply means the withdrawal must be processed through another payment provider or bank-transfer solution.
For a typical MACH-funded casino account, the withdrawal flow looks like this:
- The player requests a withdrawal from their casino or sportsbook account.
- The operator processes the payout through its bank or another provider supporting Chilean transfers.
- Funds are transferred to the player’s MACHBANK account as an ordinary bank transfer rather than a MACH payment.
- MACHBANK receiving limits apply. Unvalidated accounts have a CLP 3 million balance cap, while other transfer limits can affect how much a player receives at once.
MACH refunds should not be used as an alternative withdrawal method. They are tied to the original payment, cannot exceed the deposited amount, and are available only within 14 days of the transaction.
đź’ˇ What is the practical implication for iGaming operators: MACH can form the deposit side of an online casino payment setup, but a separate payout solution is required to complete the player journey. Since MACH deposits can arrive almost immediately while withdrawals follow a different route and timetable, clearly communicating expected payout times at the cashier can also help prevent unnecessary payment-related support requests.
Building the Payment Stack Around MACH
MACH is designed to solve local deposits from Chilean players. It does not provide the broader infrastructure an operator needs for cards, withdrawals, multi-currency payments, routing, or payment failover. A complete Chilean cashier therefore needs complementary payment methods and infrastructure around MACH. The table below shows the main layers operators should consider, why each is needed, and where MACH fits within the overall payment stack.
| Complementary Payment Layer | Why Operators Need It | Priority Markets |
|---|---|---|
| Card acquiring (Visa, Mastercard, Redcompra) | MACH reaches only MACHBANK and Bci users and caps online QR deposits at CLP 400,000 daily. Cards carry the high-value segment and every player outside the MACH base | Chile, all segments |
| Local bank-transfer rails (Khipu, Fintoc, Webpay Plus) | Broad bank coverage, higher ticket tolerance and materially lower cost on large deposits; Khipu publishes 0.69% plus IVA against MACH’s 1.8% base | Chile, high-ticket and VIP |
| Dedicated payout rail | MACH documents no disbursement product. Without a Chilean payout arrangement there is no way to complete the loop for players who deposited with MACH | Chile, mandatory |
| Cash and voucher networks (Servipag, Sencillito) | Serves unbanked and cash-preferring players and absorbs deposits declined by bank-side controls | Chile, regional and lower-ARPU segments |
| Payment orchestration and routing | MACH offers no failover, no cascading and no alternative route when a charge fails. Orchestration supplies retry logic and method-level performance data across the cashier | Chile and any multi-GEO footprint |
| Fraud and identity tooling | Merchant-facing device fingerprinting, risk scoring and rules are not described in MACH’s public documentation. Account-takeover and mule detection stay with the operator | Chile, all segments |
| FX and treasury infrastructure | Settlement is CLP-only into a Chilean bank account, leaving conversion, repatriation and hedging entirely outside the rail | Offshore treasury structures |
đź’ˇ Operator note: MACH makes the strongest case when an operator has a local presence in Chile and expects meaningful demand from MACHBANK users. The bigger consideration is what surrounds it: since MACH covers deposits rather than the full payment journey, operators need a reliable payout route and broader cashier coverage. Transaction costs matter, but they should be weighed against local reach and the role MACH will actually play in the payment mix.
Contact the GR8_TECH team for a Chile-specific cashier review covering MACH integration, card acquiring, payout rails and routing under a single iGaming payment system.
Most Common Fraud and Risks
MACH reduces some traditional payment risks because players authorize transactions inside the MACHBANK app rather than entering card details at the casino cashier. However, secure iGaming payments still depend on operator-level controls, particularly around player identity and account ownership.
The main risks operators should consider include:
- Account takeover: A stolen device or compromised PIN can allow an attacker to authorize payments from a legitimate MACH account. Operators still need their own device and behavioral controls.
- Third-party funding: The MACH account holder and casino player are not necessarily the same person. For online gambling payments, operators should therefore maintain their own checks against third-party deposits and mule accounts.
- Payment-link and QR fraud: MACH payments can use links and QR codes, creating opportunities for phishing or fraudulent payment requests outside the legitimate casino environment.
- Disputes and refund abuse: MACH does not use card-scheme chargebacks, but Chilean law still provides mechanisms for disputing unrecognized electronic transactions. Refund and reversal windows can also create opportunities for abuse.
The key distinction is that MACH secures the payment authorization itself, not the player’s entire casino journey. Identity verification, transaction monitoring and fraud controls therefore remain the responsibility of the operator.
Compliance
⚠️MACHBANK’s status as a CMF-supervised bank does not transfer any gambling, AML or player-protection obligation to the operator’s side of the relationship. The provider verifies its own account holders; the operator remains solely accountable for its players.
| Domain | Provider Position | Operator Implication |
|---|---|---|
| AML and KYC | MACHBANK performs identity validation on its own account holders and applies balance and transfer limits where data is unvalidated | Provider KYC does not substitute for player KYC. Run independent identity, age and source-of-funds checks |
| Account-ownership verification | The payer is the authenticated MACH account holder; the merchant receives a payment token and metadata, not verified payer identity | Payment-account ownership does not prove gambling-account ownership. Enforce name-matching and block third-party funding at the cashier |
| Local gambling-payment restrictions | Not addressed in provider documentation. Chile’s pending bill would require CMF-authorised payment means for both deposits and withdrawals, block transactions destined for unauthorised platforms, and bar unauthorised entities from holding Chilean bank accounts | Treat acceptance as contingent. Contract for termination notice and have a substitute deposit method configured before launch |
| Licensing status of the operator | MACH publishes no gambling merchant policy; acceptance is not publicly disclosed and must be confirmed during commercial onboarding | Disclose the gambling activity explicitly at onboarding. Availability in other regulated industries establishes nothing about gambling acceptance |
| Recordkeeping and reporting | Compensation documents, downloadable reconciliation files and scheduled reports with configurable fields are provided | Map upstream_id, metadata and compensation identifiers into the AML case file, not only into finance reporting |
| Transaction monitoring | Enrolment charges are rate-limited and auto-deactivated after four consecutive failures; broader merchant-facing monitoring is not publicly disclosed | PSP-side controls are not AML monitoring. Retain independent transaction monitoring and suspicious-activity reporting |
| Responsible gambling | No responsible-gambling functionality is evidenced on this rail | Deposit limits, cooling-off and self-exclusion must be enforced in the cashier and player account |
| Data protection | Operates under Chilean data protection rules; the closed-loop design keeps card and account credentials out of the merchant environment | Reduced scope is not zero scope. Player payment references and reconciliation data remain the operator’s records |
| Strong authentication and PCI DSS | The QR and payment-button flow carries no card data, removing PCI DSS scope for that flow specifically; the MACHBANK Visa card route is an ordinary card transaction | Maintain full PCI compliance for the cashier’s card element. Do not describe closed-loop authorization as scheme-level authentication |
Conclusion: Is MACH the Right Fit for Your iGaming Payment Stack?Â
For iGaming operators targeting Chile, the MACH payment method is best understood as a local deposit option rather than a complete payment solution. Its value lies in a familiar mobile experience, CLP-native payments, and access to the established MACHBANK and Bci ecosystem.Â
At the same time, its role is deliberately narrow: coverage is limited to Chile, withdrawals require separate payout infrastructure, and direct acceptance of gambling merchants is fairly ambiguous, so you’d do well consulting the GR8_TECH team prior to integration.Â
MACH therefore works best as part of a broader mix of online casino payments, alongside cards, bank transfers, payout rails, and other local methods. For operators with a Chilean presence and meaningful demand from MACHBANK users, it can strengthen cashier coverage without requiring MACH to carry the entire payment journey.
Share
