Tonder offers multiple integration models to accept deposits and send withdrawals. Selecting the right model is critical for your project’s success, as it impacts your time to market, development resources, user experience, and compliance requirements.This guide will help you understand:
The five integration approaches for accepting payments, including our recommended Hybrid model.
The standalone Withdrawals API for sending payouts.
The key differences to help you select the right model for your needs.
Real-world use cases for platforms like gaming and e-commerce.
Withdrawals for this model are handled via the Standalone Withdrawals API.Refunds are initiated from the merchant’s dashboard.*Refunds in Hybrid mode: Dashboard (recommended) or API Direct for cards only. See Hybrid Integration details below.
Create payment links via the dashboard or an API call.
Code Required
No
Customization
Upload your logo and set brand colors.
PCI Compliance
Tonder manages all PCI compliance.
Use this model ifYou need to launch immediately and accept payments
quickly. You do not have a technical team or development resources. Your
payment needs are straightforward.
LimitationsCannot be embedded directly into your application or website.
Customization options are limited to branding basics.
A pre-built checkout interface that you can embed directly into your application, providing a more integrated user experience than a redirect.
Aspect
Details
UI Location
Embedded in your application (e.g., via iframe).
Money Flows
(Yes) Deposits (No) Withdrawals
Setup
Install the SDK, configure your keys, and embed the component.
Code Required
Low integration code.
Customization
Styling options (colors, fonts, spacing).
PCI Compliance
Tonder handles sensitive data via tokenization.
Platforms
Web (JavaScript), iOS, Android, React Native, Ionic, Flutter.
Use this model ifYou need an embedded checkout experience within your
website or mobile app. A standard but styleable UI is acceptable for your
brand. You are building a mobile application and want a native-feel checkout
LimitationsUI customization is limited to styling; the layout and flow
are fixed.
If you want to learn more about the Full SDK provided, check out the available SDKs below:
Build your own custom checkout UI from the ground up while our SDK handles the tokenization of sensitive card data in the background.
Aspect
Details
UI Location
Your custom-built forms and customer journey.
Money Flows
(Yes) Deposits (No) Withdrawals
Setup
Install SDK, build your payment forms, and integrate the tokenization function.
Code Required
Requires front-end development to build payment forms.
Customization
Complete control over the user experience (UX) and user interface (UI).
PCI Compliance
Tonder handles sensitive data via tokenization.
Platforms
Web (JavaScript), iOS, Android, React Native, Ionic, Flutter.
Use this model if you needBrand consistency and a specific user
experience are critical. You have unique UI/UX requirements for your checkout
flow. You have a strong front-end development team.
LimitationsLonger implementation time compared to pre-built solutions.
Requires significant UI development effort from your team.
If you want to learn more about the Lite SDK provided, check out the available SDKs below:
The best-of-both-worlds approach: Combine the simplicity of SDK/Hosted for card payments with the power and flexibility of API Direct for all other payment methods and withdrawals—without requiring PCI certification.
Aspect
Details
Architecture
Dual integration: SDK/Hosted for cards only + API Direct for everything else
Money Flows
(Yes) Deposits (all methods) (Yes) Withdrawals (Yes) Refunds (cards via Dashboard or API Direct)
PCI Scope
No PCI certification required. Tonder handles card PCI compliance through SDK/Hosted.
Setup Time
1-2 weeks (est.)
Customization
High - Full API control for non-card methods while maintaining secure card processing
Dashboard (Recommended): Process all card refunds through the Tonder merchant dashboard
API Direct: Use the API Direct Integration for card refunds
Important: We strongly recommend choosing one refund method and using it consistently. Mixing both approaches requires handling different refund flows and can complicate your integration.
You want API Direct control for payment methods and withdrawals without PCI certification
You need programmatic control over SPEI, cash payments, digital wallets, and withdrawals
You’re comfortable implementing and maintaining dual integration patterns
You want the best balance of control, flexibility, and compliance simplicity
Limitations
Requires managing two different integration patterns simultaneously
More complex webhook handling compared to single-model integrations
Higher initial development effort than pure SDK/Hosted approaches
Refund handling requires careful planning to avoid mixing approaches
Direct backend API integration gives you complete control over the payment flow, data handling, and user interface.
Aspect
Details
UI Location
You build and control the entire front-end and back-end stack.
Money Flows
Deposits (Yes) Withdrawals (Yes) Refunds
Setup
Full back-end API integration.
Code Required
Full-stack development effort.
Customization
Complete control over all aspects of the payment process.
PCI Compliance
You must be PCI certified.
Use this model ifYour organization is already PCI certified. You need to
support deposits, withdrawals, and refunds within a single integration. You
process a high volume of transactions and require maximum control and
flexibility.
PCI Certification is Required.With this model, your servers will handle raw card data, making PCI DSS certification mandatory. You must provide a valid Attestation of Compliance (AOC) before starting your implementation.
LimitationsPCI certification is a strict prerequisite. The longest and
most complex implementation path.
If you want to learn more about API Integration, check out the API reference below:
The Withdrawals API is a standalone, server-to-server API designed exclusively for sending payments to recipients.
Aspect
Details
Money Flow
(Yes) Withdrawals only
Combines With
Can be used alongside any deposit integration model (Hosted, Full SDK, Lite SDK). Note: If using Hybrid model, withdrawals are handled via API Direct.
PCI Scope
Tonder manages PCI compliance for this API.
Setup Time
1-2 days (est.)
Use Cases
Player payouts, seller payments, affiliate commissions, etc.
Key PointThe Withdrawals API is independent of deposit integrations. You can add withdrawal functionality without modifying your existing payment acceptance setup.Hybrid Integration Note: When using the Hybrid model, withdrawals are already included through API Direct Integration—no separate Withdrawals API implementation needed.
Every single integration model can be used to support various use cases. Here are some common scenarios and the recommended models for each:
Deposits + Withdrawals (Hybrid) ⭐
Receiving Deposits
Sending Payouts
Accepting Payments
An i-Gaming platform wants to accept deposits from multiple payment methods and send player payouts, but does not have PCI certification. They also want programmatic control over SPEI transfers and cash payments.Recommended Solution: Hybrid Integration
Card Payments: Implement Full SDK for embedded card processing (Tonder handles PCI)
Other Methods: Use API Direct for SPEI, OxxoPay, Mercado Pago (full API control, no PCI required)
Withdrawals: Use API Direct for automated player payouts
Setup Time: ~1-2 weeks
Benefits: Maximum control without PCI certification, unified withdrawal handling, flexible payment method management
Trade-off: Must handle dual webhook notifications and different request/response patterns for cards vs. other methods.
An i-Gaming company wants to implement a Platform with secure deposits from players to initiate the user experience. Developers then can choose from multiple endorsed models to meet this need:
Hosted Checkout: The fastest option, requiring no code and minimal setup (estimated 1 day).
Full SDK/Lite SDK: These models allow for an embedded checkout experience. Full SDK is quicker (2-3 days) with a standard UI, while the Lite SDK provides complete customization.
API Integration: The model that offers maximum control, but the merchant must be PCI certified (L1 ROC or L2 SAQ D required).
All these models support Deposits and Refunds
To satisfy the need to send winnings to players, an i-Gaming Platform must implement robust withdrawal capabilities. The two primary endorsed models for this outflow are:
Withdrawals API: This standalone, independent API is for Withdrawals only and can be combined with any deposit model. Implementation is a server-to-server API with an estimated setup of 1-2 days.
API Integration (Direct Connect): This single integration handles all three money flows (Deposits, Withdrawals, Refunds), but is only suitable if the platform is PCI certified.
This flexible approach simplifies integration, compliance and transaction monitoring.
For an E-commerce web site, the core need is to securely accept customer payments. Developers can choose from endorsed models that balance speed, customization, and compliance:
Hosted Checkout: Best for the fastest implementation (1 day) and sites with no code required.
Full SDK/Lite SDK: Offer embedded checkout with the Full SDK providing a standard UI and the Lite SDK offering complete UX/UI control for strong branding.
Direct Connect API Integration (S2S): Allows for maximum control and full backend integration, but requires the merchant to be PCI certified.
These models all support Deposits and Refunds , providing a complete, scalable, transaction system optimized for e-commerce.
