- The four primary integration models for accepting payments.
- 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.
Before You Choose
Consider these key questions to guide your decision:- Do you have developers available to write code?
- How quickly do you need to launch and start accepting payments?
- Is a custom-branded user interface essential for your checkout flow?
- Does your organization hold a valid PCI DSS certification?
- Do you need to both accept payments (deposits) and send payouts (withdrawals)?
Quick Comparison
This matrix provides a high-level comparison of the integration models.| Integration Model | Deposits | Withdrawals | Refunds | Setup Time (est.) | Customization | PCI Cert Required |
|---|---|---|---|---|---|---|
| Hosted Checkout | Yes | No | No | 1 day | Low | No |
| Full SDK | Yes | No | No | 2-3 days | Medium | No |
| Lite SDK | Yes | No | No | 5-7 days | High | No |
| API Direct Integration (S2S) | Yes | Yes | Yes | 1-2 weeks | Complete | Yes |
Withdrawals for this model are handled via the Standalone Withdrawals API.Refunds are initiated from the merchant’s dashboard.
Integration Models in Detail
Dive into the specifics of each model to understand its architecture, features, and limitations.- Hosted Checkout
- Full SDK (Pre-built UI)
- Lite SDK (Custom UI)
- API Direct Integration
A ready-to-use, Tonder-hosted payment page accessed via a redirect URL. This is the fastest way to start accepting payments.
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.
| Aspect | Details |
|---|---|
| UI Location | Tonder-hosted pages |
| Money Flows | (Yes) Deposits (Yes) Refunds (via Dashboard) (No) Withdrawals |
| Setup | 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. |
LimitationsCannot be embedded directly into your application or website.
Customization options are limited to branding basics.
Withdrawals API
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). |
| 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.
Feature Support Across Models
In this table, we summarize the availability of key features across the different integration models.| Feature | Hosted Checkout | Full SDK | Lite SDK | API Integration |
|---|---|---|---|---|
| Card Payments | Yes | Yes | Yes | Yes |
| Bank Transfers | Yes | Yes | Yes | Yes |
| Cash Payments | Yes | Yes | Yes | Yes |
| Digital Wallets | Yes | Yes | Yes | Yes |
| 3D Secure | Automatic | Automatic | Automatic | Manual Control |
| Tokenization | Automatic | Automatic | Automatic | Merchant Implements |
| Saved Cards | Yes | Yes | Yes | Merchant Implements |
| Webhooks | Yes | Yes | Yes | Yes |
| Test Environment | Yes | Yes | Yes | Yes |
Contact Tonder support for guidance on selecting the right integration model for
your business.
I need to ACCEPT PAYMENTS (Deposits)
I need to ACCEPT PAYMENTS (Deposits)
Do you have developers?
- No → Hosted Checkout
- Yes → Continue to question down below
Do you need a completely custom UI?
Do you need a completely custom UI?
- No → Full SDK (for a standard, embeddable UI)
- Yes → Lite SDK (for full UX/UI control)
Are you PCI certified and need maximum control?
Are you PCI certified and need maximum control?
- Yes → API Integration
- No → Choose between Full SDK or Lite SDK based on UI needs.
I need to ACCEPT AND SEND PAYMENTS (Deposits + Withdrawals)
I need to ACCEPT AND SEND PAYMENTS (Deposits + Withdrawals)
Are you PCI certified?
- Yes → API Integration is the all-in-one
- No → Continue to question down below
Choose a deposit model and pair it with the Withdrawals API:
Choose a deposit model and pair it with the Withdrawals API:
- Fastest Launch: Hosted Checkout + Withdrawals API
- Standard Embedded UI: Full SDK + Withdrawals API
- Custom Branded UI: Lite SDK + Withdrawals API
I need to SEND PAYMENTS ONLY (Withdrawals)
I need to SEND PAYMENTS ONLY (Withdrawals)
- Use the standalone Withdrawals API.
Use Cases
Every single integration model can be used to support various use cases. Here are some common scenarios and the recommended models for each:- Receiving Deposits
- Sending Payouts
- Accepting Payments
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 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).