Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tonder.io/llms.txt

Use this file to discover all available pages before exploring further.

This guide covers testing requirements, test data, and best practices for validating your Withdrawals API integration.
Authentication RequiredEvery single request during testing requires authentication. Include the Authorization: Token YOUR_API_KEY header in all requests, including Postman requests. See Authentication requirements for details.

​
Testing Environment

​
Stage Environment

Use the Stage environment for all testing, where fund transfers are simulated rather than processed with real money. Stage Base URL: https://stage.tonder.io/api/v1
Simulated TransfersIn the Stage environment, withdrawals are simulated. No actual funds are transferred, making it safe for comprehensive testing.

​
Test Institution Code

​
CRITICAL: Use 97846 for Testing

When testing in the Stage environment, you must use institution code 97846 for the beneficiary_institution field. Why: This is a special test code that simulates bank responses without processing actual transfers. Example: 
{
  "beneficiary_institution": "97846",
  ...
}
Production Institution CodesNever use 97846 in production. Use real bank institution codes from the Mexican Banking Reference for live transactions.
Test Environment Interbank CodeThe interbank code (originator account) for the test environment is: 646180567300000006. Use this value for the interbank_code field when testing in the Stage environment.

​
Testing Scenarios

​
1. Basic Withdrawal Creation

Test creating withdrawals with valid data:
  • SPEI transfers with valid 18-digit CLABE
  • Debit card transfers with valid 16-digit card numbers
  • Different amounts (small, medium, large)
  • Both fee models (00 and 01)

​
2. Parameter Validation

Test error handling for invalid parameters:
  • Missing required fields
  • Invalid account formats
  • Invalid currency codes
  • Invalid transfer methods
  • Missing metadata (latitude/longitude for SPEI/MXN)

​
3. Status Transitions

Test and verify all status transitions:
  • PENDING → PROCESSING
  • PROCESSING → SENT_TO_PROVIDER
  • SENT_TO_PROVIDER → PAID_FULL
  • Any status → REJECTED

​
4. Webhook Receipt

Test webhook handling:
  • Verify webhook payload structure
  • Test all status change notifications
  • Validate webhook signatures (if implemented)
  • Handle duplicate webhooks gracefully
  • Test webhook retry scenarios

​
5. Error Scenarios

Test error handling:
  • Invalid authentication (401): Test with missing or incorrect Authorization header
  • Bad request parameters (400)
  • Not found errors (404)
  • Server errors (500) with retry logic
Testing AuthenticationWhen testing authentication errors in Postman:
  • Remove the Authorization header to test missing authentication
  • Use an invalid token to test incorrect authentication
  • Verify you receive 401 Unauthorized responses

​
Test Data Examples

​
Valid SPEI Withdrawal

{
  "user_id": 27055,
  "amount": 15,
  "currency": "MXN",
  "transfer_method": "SPEI",
  "beneficiary_account": "846180000400000001",
  "beneficiary_name": "Jhon Doe",
  "beneficiary_rfc": "ND",
  "beneficiary_institution": "97846",
  "interbank_code": "646180567300000006",
  "email": "test@example.com",
  "description": "Test withdrawal",
  "metadata": {
    "latitude": "22.8870221",
    "longitude": "-109.911775",
    "operation_date": "2024-01-15",
    "customer_email": "test@example.com",
    "business_user": "admin_user_001",
    "customer_id": "CUST_12345",
    "order_id": "ORDER_ABC_789"
  },
  "fee_model": "01"
}

​
Valid Debit Card Withdrawal

{
  "user_id": 1,
  "amount": 100,
  "currency": "MXN",
  "transfer_method": "DEBIT_CARD",
  "beneficiary_account": "4111111111111111",
  "beneficiary_name": "Test Beneficiary",
  "beneficiary_rfc": "ND",
  "beneficiary_institution": "97846",
  "interbank_code": "646180567300000006",
  "email": "test@example.com",
  "description": "Test debit card withdrawal",
  "metadata": {
    "latitude": "22.8870221",
    "longitude": "-109.911775",
    "operation_date": "2024-01-15",
    "customer_email": "test@example.com",
    "business_user": "admin_user_001",
    "customer_id": "CUST_12345",
    "order_id": "ORDER_ABC_789"
  },
  "fee_model": "01"
}
Complete Test DataThese examples include all required fields for testing. Remember to:
  • Replace user_id with a valid user ID from the Get User ID endpoint
  • Include the Authorization: Token YOUR_API_KEY header in all requests
  • Use the test institution code 97846 and interbank code 646180567300000006 for Stage environment testing

​
Verification Checklist

Before going to production, verify:
  • Withdrawal creation works with valid data
  • All required parameters are validated
  • Error responses are handled correctly
  • Webhooks are received and processed
  • All status transitions are handled
  • Rejection scenarios are handled gracefully
  • Different amounts work correctly
  • Both transfer methods (SPEI and DEBIT_CARD) work
  • Both fee models work
  • Metadata requirements are met
  • Authentication works correctly
  • Retry logic works for transient errors

​
Testing Best Practices

​
1. Test Different Amounts

Test with various amounts to ensure:
  • Small amounts (e.g., 10.00 MXN)
  • Medium amounts (e.g., 1000.00 MXN)
  • Large amounts (e.g., 100000.00 MXN)
  • Decimal precision handling

​
2. Test Both Transfer Methods

Verify both transfer methods work:
  • SPEI: Test with valid 18-digit CLABE
  • DEBIT_CARD: Test with valid 16-digit card numbers

​
3. Test Webhook Receipt

Ensure webhook handling works:
  • Receive webhooks for all status changes
  • Parse webhook payloads correctly
  • Handle duplicate webhooks
  • Process webhooks asynchronously

​
4. Test Error Scenarios

Verify error handling:
  • Invalid parameters return 400
  • Missing auth returns 401
  • Invalid withdrawal ID returns 404
  • Server errors are retried appropriately

​
5. Test Status Monitoring

Verify status tracking:
  • Status transitions are logged
  • Final statuses are handled correctly
  • Rejections are processed appropriately

​
Pre-Production Checklist

Before moving to production:
  1. Complete all test scenarios listed above
  2. Verify webhook endpoints are accessible from Tonder’s servers
  3. Test with production-like data (but in Stage environment)
  4. Validate error handling for all error codes
  5. Review logs for any unexpected behavior
  6. Test retry logic for transient failures
  7. Verify monitoring and alerting are set up
  8. Document any issues and resolutions

​
Production Readiness

You’re ready for production when:
  • ✅ All test scenarios pass
  • ✅ Webhooks are working reliably
  • ✅ Error handling is comprehensive
  • ✅ Monitoring and alerts are configured
  • ✅ Support team knows how to handle issues
  • ✅ Documentation is complete

​
Next Steps