Cashier checkout
Player deposits, balance updates and withdrawal requests create continuous two-way fund flows across gaming and forex platforms. Gaming cashier software manages multi-currency wallets and closed-loop payouts through Cardflo’s transaction routing and acquirer partner access.
- Category
- Checkout
- Capabilities
- 10
- Available on
- All plans
Cardflo's cashier checkout provides a hosted payment page solution, redirecting customers to a secure, Cardflo-branded or co-branded environment for payment. This approach significantly reduces PCI compliance scope for merchants while offering a robust, feature-rich payment experience.
It is suitable for businesses prioritising security and rapid deployment with minimal development overhead.
Our multi-acquirer cashier checkout simplifies complex payment flows by managing multiple MIDs and optimising transaction routing. This reduces operational costs and boosts conversion rates, providing a streamlined payment solution for merchants and customers.
Cashier checkout overview
A cashier checkout functions as a hosted payment environment where the customer is redirected from the merchant site to a secure interface managed by a payment service provider. This architectural choice places the burden of sensitive data capture on the acquirer or gateway infrastructure, effectively isolating the merchant from primary cardholder data.
By utilising a hosted page, businesses can facilitate transactions via various methods including credit cards, digital wallets, and alternative payment methods without the development complexity of bespoke integrations.
The system handles the entire authorisation flow, including the execution of Strong Customer Authentication and 3DS protocols, before returning the customer to the merchant site with a success or failure notification.
This model is common for businesses that require high security and minimal data handling, as it simplifies the process of achieving and maintaining PCI DSS compliance through the use of pre-certified components.
How cashier checkout works
Initialisation and redirect
When a customer initiates a transaction, the merchant server sends a request to the payment gateway API. The gateway generates a unique session and returns a secure URL. The merchant site then redirects the browser to this hosted environment, ensuring no card data enters the merchant infrastructure.
Payment method selection
The hosted page presents the available payment options based on the merchant configuration, customer location, and transaction currency. The customer selects their preferred method, such as a scheme card or digital wallet, and enters the necessary credentials within the secure, governed frame of the payment provider.
Authentication and authorisation
The system executes required security checks, including CVV verification and AVS. If mandated by PSD2 regulations, the interface triggers a 3DS challenge. Once authenticated, the transaction request is routed through the acquirer to the issuer for authorisation, following standard clearing and settlement protocols.
Callback and reconciliation
Following the issuer response, the hosted page redirects the customer back to the merchant site. Simultaneously, an asynchronous webhook is sent to the merchant server to update the order status. This ensures that the transaction state is synchronised across both systems for accurate record keeping.
Why cashier checkout matters
Facilitates Global Expansion
A hosted checkout environment typically supports a wide range of alternative payment methods and local currencies without requiring the merchant to build individual integrations for each. The service provider manages the underlying relationships with various local acquirers and schemes, allowing businesses to accept payments in multiple jurisdictions while maintaining a uniform reporting structure and settlement process.
Security and Maintenance
Hosted pages are updated by the provider to include the latest security patches, compliance requirements, and payment technologies. This eliminates the need for the merchant to manually update their code when schemes mandate changes to 3DS specifications or when new regulatory requirements like PSD3 are introduced. It ensures the payment flow remains functional and compliant with minimal internal developer intervention.
Cashier checkout use cases
In-play betting cashier
Sportsbook operators face concentrated deposit traffic during live fixtures, followed by payout requests after markets settle and enhanced scrutiny of rapid deposit-withdrawal cycles. Cardflo applies gaming-specific routing, configurable deposit limits and withdrawal controls, while acquirer partners support eligible card traffic under the operator’s gambling licence and MCC.
Margin funding and withdrawals
Retail forex brokers need multi-currency cashier flows for margin deposits, trading-account balances and withdrawals back to the original funding instrument, with funding speed affecting position entry. Cardflo routes eligible transactions through its acquirer partner network, maintains payment-to-payout references and supports controls for source-of-funds, KYC and AML workflows.
Casino wallet segregation
Casino operators manage card deposits, e-wallet funding, bonus balances and cashable winnings within one cashier, while keeping player funds distinct from operational money. Cardflo orchestrates payment methods and balance-status events, routes gaming traffic to suitable acquirer partners and supports withdrawal rules based on wagering completion, verification status and original payment method.
Tournament entry funding
Fantasy sports operators experience sharp entry-fee deposit peaks before contest lock times, then process prize withdrawals after results are confirmed and scoring disputes close. Cardflo uses multi-acquirer routing to manage concentrated authorisation demand, presents local funding methods where available and supports controlled payout queues tied to verified player balances and contest settlement.
Cashier checkout by the numbers
This represents a typical reduction in the volume of security controls a merchant must personally manage when moving from a direct API to a hosted redirect model.
Industry benchmarks suggest that hosted pages can be integrated multiple times faster than bespoke API integrations, depending on the complexity of the existing tech stack.
High performance gateways aim for processing times under two seconds, though total redirect time depends on the customer's network and the issuer's 3DS response speed.
Methodology: these figures are illustrative ranges drawn from published industry data and observed merchant cohorts, not guarantees. Actual results depend on your risk profile, card mix, geography and acquiring setup, and are confirmed only in your own pricing and approval terms.
Related terms
Talk to our team about a live rollout across our acquirer partners' rails.
What you get with Cashier checkout
- Minimises PCI DSS compliance burden by ensuring card data never touches the merchant server
- Provides automatic updates for SCA and 3DS compliance without requiring manual code changes
- Supports multiple currencies and local settlement to facilitate efficient cross border commerce
- Integrates diverse alternative payment methods through a single, managed checkout interface
- Allows for co-branding and custom CSS to maintain brand consistency throughout the payment journey
- Triggers real time webhooks to ensure merchant order management systems remain synchronised
- Handles complex routing and failover logic automatically to improve authorisation success rates
- Includes built in fraud prevention tools such as AVS and CVV verification requirements
- Reduces development time through pre-built templates and standardised API redirection protocols
- Supports secure tokenisation for subsequent recurring transactions and merchant initiated payments
A short scoping call, then a written plan for your MIDs.
Questions about Cashier checkout
How does gaming cashier software manage withdrawals exceeding original deposits?
The cashier records deposit amounts and payment methods against each player balance before evaluating a withdrawal request. Where closed-loop controls require deposited funds to return through the original method, any remaining winnings can be separated and sent through an eligible payout route.
Operators can configure these flows around their policies, supported currencies and acquirer partner requirements, while maintaining a clear transaction record for reconciliation and compliance review.
Can gaming cashier software split one payout across multiple methods?
Gaming cashier software can divide a payout when return-to-source rules, payment method limits or available balances prevent one route from covering the full amount.
The orchestration layer assigns each portion to an eligible card, bank or wallet payout method and records the resulting transactions under the same withdrawal request.
Operators can review the status of each portion independently, including pending, completed or failed payouts, without losing the link to the player’s original request.
Does this checkout method support Strong Customer Authentication?
Yes, the hosted environment is designed to handle the complexities of PSD2 and SCA. When a transaction requires authentication, the page will automatically trigger the necessary 3DS flow, directing the customer to their issuing bank's portal.
Once the customer completes the challenge, the result is processed by the gateway, and the customer is returned to the merchant site. This ensures compliance with regional regulations without additional development work from the merchant.
What happens if a customer closes the window during the redirect?
If a customer terminates the session before the redirect is complete, the transaction remains in a pending or cancelled state. Systems typically use webhooks to notify the merchant server if a session expires or is abandoned.
The merchant's order management system should be configured to handle these status updates, either by allowing the customer to retry the payment or by automatically cancelling the order after a specific period of inactivity.
Is a hosted checkout suitable for mobile applications?
Hosted checkouts can be used in mobile applications, often through a web view or by opening the mobile browser. However, for a fully native experience, some providers suggest using SDKs.
The hosted page itself is usually designed with responsive web design principles to ensure it functions correctly on various screen sizes, providing a functional payment path for mobile users while maintaining the security benefits of a hosted environment.
How are alternative payment methods configured in the checkout?
Alternative payment methods like digital wallets or bank transfers are typically enabled at the PSP or gateway level. Once configured in the merchant's account, these options automatically appear on the hosted checkout page based on the transaction's parameters.
This allows merchants to dynamically offer relevant payment methods to different customer segments without needing to update the integration code on their own website.
What is the difference between a hosted page and an iFrame?
A hosted page involves a full redirect where the URL in the browser changes to the provider's domain. An iFrame embeds the payment form directly within the merchant's page, keeping the merchant's URL visible.
While both methods help reduce PCI scope, a full redirect is often considered easier to implement and provides a clear separation of environments, whereas an iFrame requires more careful handling to ensure it remains responsive and secure.
Related features.
Related guides.
See how Cardflo compares.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.