Overview & Matrix
Every method you can accept, and what changes in the request when you switch between them.
All payment methods in Tonder work through the same unified /process/ endpoint. You just change
payment_method.type and add the method-specific parameters, making it easy to offer multiple
options without managing different integrations.
{
"operation_type": "payment",
"amount": 100.00,
"currency": "MXN",
"customer": { /* customer data */ },
"payment_method": {
"type": "CARD"
},
"client_reference": "ORD-001"
}Available methods
| Method | Type | Best for | Processing time |
|---|---|---|---|
| Cards | Instant | E-commerce, instant confirmation | Immediate |
| Apple Pay | Instant | Safari / iOS shoppers, via the Web SDK button | Immediate |
| MercadoPago | Instant | Digital wallet customers | Immediate |
| SPEI | Bank transfer | Higher-value, B2B | Real-time |
| OXXO Pay | Cash | Customers without bank accounts | 24-48 hours |
| Cash vouchers | Cash | Regions without OXXO coverage | 24-48 hours |
Country and network availability, and each method's support for deposits/withdrawals/refunds, vary by market. See Country coverage for the full breakdown.
Implementation strategy
They provide immediate confirmation and work for most customers.
Essential in the Mexican market, where cash is still popular.
Bank transfers are trusted for larger transactions.
Add digital wallets and alternative methods based on customer feedback.
Set up webhooks to track asynchronous payments (OXXO Pay, SPEI, Cash vouchers).