DaviPlata
In Colombia, DaviPlata has reached the scale where excluding this payment method from a local payment strategy means neglecting a substantial part of the country's digital-finance market. DaviPlata is the digital financial product of Banco Davivienda, Colombia’s second-largest bank, which counted 18.5 million DaviPlata customers at the end of 2024, while more than 2.4 million microbusinesses used the product for their financial needs. That puts DaviPlata firmly on the shortlist for a Colombia-facing cashier, but not in the role of a direct PSP or full iGaming payment gateway. Rather, it functions as a local account-based payment method within the operator’s broader payment stack, giving DaviPlata users a way to pay directly from their accounts through Davivienda’s merchant-payment infrastructure.
Why Operators Choose DaviPlata
DaviPlata’s scale already makes the case for considering it in a Colombia-facing cashier. On top of that reach, there are several practical reasons why operators use it:
- A direct merchant-payment API exists. DaviPlata lets merchants connect their checkout directly to its payment system. The customer identifies their DaviPlata account, receives a one-time verification code, and uses it to authorize the payment before the transaction is completed.
- Checkout can avoid a conventional third-party gateway. DaviPlata’s own lightweight payment button is designed to operate on the merchant’s page without a separate payment gateway. The provider reports a payment process below 30 seconds and approval rates above 98% for this product.
- Direct regulated-gambling implementation. Local operator RushBet currently lists “Daviplata Directo” alongside PSE, Nequi, cards, and cash deposit routes, so this is evidence of actual licensed use rather than generic technical compatibility.
- The same local account can support a withdrawal at RushBet. The operator allows a player to request a withdrawal to the mobile number associated with the player’s DaviPlata account. This makes the payment method more useful than a strictly deposit-only option, although the outbound processing architecture is not disclosed in DaviPlata’s public API catalog. We recommend contacting GR8_TECH to discuss how DaviPlata withdrawals can be implemented within your specific payment setup.
Limitations
The most obvious limitation is geographic: DaviPlata is primarily a Colombia-focused payment method, so its value to iGaming operators depends heavily on their exposure to the Colombian market. On top of that, operators should focus on:
Commercial terms: Merchant pricing, gaming fees, reserve requirements, and settlement terms are not publicly disclosed and require commercial onboarding.
API capacity. DaviPlata claims 100 API requests per hour and a 60-second timeout, but does not confirm whether these limits apply to high-volume production contracts.
Production suitability. Operators need to confirm contracted throughput and capacity before relying on DaviPlata as a primary cashier method.
Contact GR8_TECH for a thorough check on DaviPlata’s commercial capacity, projected traffic and an integration model before DaviPlata can be assigned a core role as a payment method for online casino.
DaviPlata: Markets and Availability
For iGaming operators, DaviPlata is primarily relevant in Colombia, where it has a large user base, merchant payment infrastructure, and documented use by licensed gambling operators. The following table shows where DaviPlata fits into the local iGaming payment landscape.
| GEO | Colombia |
| Provider Presence | Davivienda deposit product with merchant APIs |
| Relevance for Casinos and Sportsbooks | Primary for evidenced iGaming use; RushBet supports direct deposits and withdrawals |
| Typical Setup | Direct API/button or operator payment integration |
| Key Alternatives | PSE, Nequi Directo, cards, cash |
| Limitations | Gaming terms, enterprise settlement, and production capacity require contracting |
💡 There is also an important distinction between direct and indirect DaviPlata payment acceptance. Wplay, another Coljuegos-authorized operator, published a March 2026 guide in which a DaviPlata-funded deposit starts by selecting PSE and then choosing DaviPlata as the financial institution. That demonstrates another route into the gambling cashier, but PSE is the payment infrastructure in that setup; it should not be counted as evidence of Wplay using DaviPlata’s direct merchant API.
This distinction affects integration strategy. A platform can potentially cover some DaviPlata-funded players through PSE while reserving direct casino payment integration for situations where the direct method has a commercial or product advantage worth maintaining as a separate cashier option.
Deposits, Withdrawals and Settlement
The clearest DaviPlata’s native merchant function is inbound payment collection. DaviPlata’s API documentation describes an on-demand purchase process using account data and an OTP, while its payment-button documentation has the customer select DaviPlata, provide the requested information, and enter a confirmation code before the payment is processed:
- Player selects DaviPlata Directo
- Player enters the last four digits of their identity document and chooses an amount (currently the deposit range at COP 5,000 to COP 1,000,000).
- A notification then arrives in the DaviPlata app for confirmation
- Identity data registered with DaviPlata and checked against an online casino’s account holder.
- DaviPlata reports that payments made through its checkout can be processed in under 30 seconds. However, this refers to the payment itself rather than the time it takes for funds to appear in a player’s casino balance, which can also depend on the operator’s processing and reconciliation.
| Area | Operator View |
| Deposit availability | Direct DaviPlata deposits are evidenced at RushBet Colombia. |
| Withdrawal availability | DaviPlata withdrawals are evidenced at RushBet, but a public generic merchant payout API has not been established. |
| Typical deposit speed | DaviPlata reports payment-button transactions in under 30 seconds; this is a provider-reported general merchant metric, not a gambling-specific SLA. |
| Typical withdrawal speed | RushBet may review a withdrawal for up to 72 hours. After approval, DaviPlata and Nequi withdrawals generally reflect almost immediately. |
| Settlement model | DaviPlata WebCheckout documentation says payment-link proceeds can reach a merchant DaviPlata or Davivienda account instantly. Enterprise gaming settlement terms are not publicly disclosed. |
| Deposit-only risk | Not applicable where the operator has a verified DaviPlata payout route; otherwise a separate withdrawal rail is still required. |
| Deposit–withdrawal asymmetry | Deposits use documented merchant payment infrastructure. The evidenced withdrawal route is operator-specific and does not prove a generally available DaviPlata merchant payout product. |
| What depends on the setup | Merchant pricing, contracted limits, production throughput, settlement terms, gambling acceptance and payout architecture must be confirmed during onboarding. |
For merchants, DaviPlata’s WebCheckout supports instant receipt of payments for online casinos into a DaviPlata or Davivienda account. The exact settlement terms for a high-volume iGaming operation are not publicly disclosed and need to be confirmed as part of the commercial agreement.
Withdrawal Availability
Withdrawal speed depends on two separate processes. The operator must first approve and release the withdrawal; once the payment is sent, the funds can reach the DaviPlata account almost immediately. In other words, the payment itself may be fast, but the complete withdrawal is only as fast as the operator’s internal review.
⚠️ DaviPlata’s public API documentation covers merchant payments but does not document an equivalent gaming payout API. Operators therefore need to confirm how outbound payments are processed and reconciled as part of their specific integration. We encourage you to contact the GR8_TECH team to discuss the payout setup available for your specific integration.
Building the Payment Stack Around DaviPlata
DaviPlata is a local payment method, not a complete cashier architecture. Operators still need other iGaming payment methods to cover players who do not use DaviPlata, support transactions outside its available limits, and provide alternative deposit and withdrawal routes when needed. The table below shows which complementary payment layers operators should consider alongside DaviPlata and the role each plays in the wider payment stack.
| Complementary Payment Layer | Why Operators Need It | Priority Markets |
| PSE | Adds broad Colombian bank-account coverage and provides an alternative bank-funded route when players do not use DaviPlata directly. | Colombia |
| Nequi | Extends wallet coverage beyond DaviPlata and reduces dependence on a single bank-linked digital account product. | Colombia |
| Visa and Mastercard debit | Covers players who prefer cards and provides a mainstream cashier option outside wallet and bank-transfer flows. | Colombia |
| Cash networks | Serves cash-preferring and underbanked player segments that a digital-account method alone cannot cover. | Colombia |
| Dedicated bank payout rail | Provides withdrawal continuity when DaviPlata payout support is unavailable, limited or commercially unsuitable. | Colombia |
| Routing and reconciliation | Normalizes different transaction states, handles pending payments and retries, and keeps deposit and payout reporting consistent across providers. | Colombia |
The cashier therefore needs to decide whether DaviPlata should be a preferred route for Colombian users or one of several online casino payment options. Transaction limits make the case for maintaining alternatives: direct DaviPlata deposits can be capped at COP 1 million, compared with limits of up to COP 10 million for PSE, Nequi Directo, and Visa/Mastercard payments. The same applies to payouts, where direct DaviPlata withdrawals can be limited to COP 500,000. Operators therefore need higher-value deposit and withdrawal routes alongside DaviPlata to avoid turning method-specific limits into cashier bottlenecks.
GR8_TECH can place DaviPlata inside a broader payment setup rather than evaluating it in isolation: player coverage can be mapped against alternative rails, while routing rules can preserve deposit and payout continuity when transaction value or method availability pushes a payment elsewhere.
💭 Operator note: do not count indirect PSE access and a direct DaviPlata integration as the same capability. They may reach the same player’s money, but they create different commercial contracts, transaction states, and operational dependencies.
Most Common Fraud and Risks
DaviPlata’s account verification and OTP/app authorization provide useful controls at the payment level, but they do not secure the player’s casino account or eliminate fraud. Operators still need to detect compromised accounts, third-party funding, manipulated transaction states, and suspicious withdrawals.
Account takeover and confirmation-code abuse: An OTP confirms payment authorization, not that the legitimate player controls the gambling account. Login, device, and withdrawal controls remain essential.
Third-party funding and ownership mismatch: The DaviPlata account and gaming account should belong to the same person. Mismatches require additional verification or rejection.
False confirmation and duplicate processing: Pending or delayed transactions can lead to repeated attempts or false payment claims. Player balances should only be credited against a verified final transaction status.
Withdrawal-destination substitution: Changing the mobile number linked to a payout can redirect funds. Destination changes should trigger ownership verification and, where appropriate, additional review.
Mule accounts and payment cycling: Rapid deposits followed by withdrawals with little genuine play can indicate misuse. Payment activity should therefore be monitored alongside wagering and withdrawal patterns.
Compliance
DaviPlata operates within Colombia’s regulated banking system as a deposit product of Banco Davivienda, which is supervised by the Superintendencia Financiera. This gives the payment method a regulated banking layer, including Fogafín deposit protection, but it does not take compliance off the operator’s hands. iGaming operators still need their own Coljuegos authorization and remain responsible for KYC, AML, transaction monitoring, and other gambling-specific controls.
| Domain | Provider Position | Operator Implication |
| Provider regulation | Banco Davivienda S.A. is an active banking establishment supervised by Colombia’s Superintendencia Financiera. DaviPlata is documented as a low-value or ordinary deposit protected by Fogafín. | Treat DaviPlata as a bank-issued payment method, not as a substitute for the operator’s own regulated gambling and payment obligations. |
| Gambling authorization | DaviPlata is demonstrably used by RushBet, an operator listed by Coljuegos as an authorized online operator in 2026. One implementation does not establish universal acceptance of gaming. | Confirm that DaviPlata and the contracted integration route accept the operator’s gambling merchant category before launch. |
| AML and KYC | DaviPlata applies banking/customer controls to its own account relationship. Public documentation does not indicate that these replace gambling-operator KYC or AML controls. | Maintain operator-side KYC, AML, source-of-funds and transaction-monitoring processes. |
| Account ownership | RushBet requires DaviPlata identity or phone details to match the gambling account holder for relevant deposit and withdrawal flows. | Use ownership matching to reduce third-party funding and payout diversion, while retaining independent gambling-account verification. |
| Authentication | Direct DaviPlata payment flows use an OTP or app-confirmation step. | Treat DaviPlata authentication as payment authorization only; it does not secure the player’s gambling account or remove account-takeover controls. |
| Responsible gambling | No public evidence establishes that DaviPlata enforces gambling-specific responsible-gambling controls. | Apply deposit, loss and responsible-gambling controls within the operator platform. |
| Commercial and technical approval | Production access requires commercial onboarding, legal documentation and risk validation; public developer material does not establish automatic gaming eligibility. | Complete merchant underwriting and confirm gaming acceptance, limits, throughput and settlement terms before relying on the method in production. |
⚠️ A working API does not prove that every merchant category is contractually accepted, and implementation by one licensed sportsbook does not establish universal gambling payment acceptance. A prospective merchant should obtain explicit confirmation that its legal entity, license, and intended transaction flows are approved before treating DaviPlata as part of its production online gambling payments stack.
The same logic applies to identity. The matching controls documented by local operators are valuable because they tie the DaviPlata account to the gaming account holder, but they do not replace casino KYC. The operator still owns decisions concerning the source of funds, suspicious behavior, and whether a withdrawal is consistent with the player’s account history.
Conclusion: Is DaviPlata Worth Integrating?
For regulated Colombia-facing iGaming operators, the answer is a conditional yes. DaviPlata has sufficient consumer scale to matter, a documented direct merchant-payment architecture, and live evidence of deposits and withdrawals at a Coljuegos-authorized operator. That makes it a credible local component of casino payment methods.
However, DaviPlata works best as one of several payment options in a Colombia-facing cashier. PSE provides broader bank-account coverage, while Nequi competes more directly with DaviPlata as another popular digital account and payment method; cards provide a further route for players who prefer conventional debit payments. These alternatives also cover higher-value transactions: direct DaviPlata deposits can be capped at COP 1 million, compared with limits of up to COP 10 million through PSE or Nequi Directo, while direct DaviPlata withdrawals can be limited to COP 500,000. In practice, DaviPlata adds valuable local coverage rather than replacing the rest of the payment stack.
The integration decision should therefore start with actual Colombian player coverage and expected transaction values. From there, GR8_TECH can assess whether direct DaviPlata adds enough coverage to justify the separate route, then place it alongside complementary payment solutions for online gambling so that method limits or payout dependencies do not become cashier constraints.
Share
