Troubleshooting Guide
This guide helps you resolve common issues when integrating with the meCash API.Table of Contents
- Authentication Issues
- API Endpoint Issues
- Payout Issues
- Webhook Issues
- Rate Limiting
- Environment Issues
- Getting Help
Authentication Issues
Problem: 401 Unauthorized Error
Symptoms:-
Check API Key Format
-
Verify API Key Validity
- Log into your meCash dashboard
- Navigate to Developer → API Keys
- Ensure your key is active and not expired
-
Check Environment
- Sandbox: Use sandbox API keys with
sandboxapi.me-cash.com - Production: Use production API keys with
api.me-cash.com
- Sandbox: Use sandbox API keys with
Problem: 403 Forbidden Error
Symptoms:-
Whitelist Your IP Address
- Go to Developer → IP Whitelisting
- Add your server’s IP address
- Wait 5-10 minutes for changes to take effect
-
Check IP Address
API Endpoint Issues
Problem: 404 Not Found Error
Symptoms:-
Check Endpoint URL
-
Verify HTTP Method
- Quotes:
POST /v1/quote - Payouts:
POST /v2/payout - Transactions:
GET /v1/transaction/{id}
- Quotes:
Problem: 400 Bad Request Error
Symptoms:-
Validate Request Body
-
Check Data Types
Payout Issues
Problem: Quote Expired Error
Symptoms:-
Generate New Quote
-
Check Quote Expiry
Problem: Insufficient Balance Error
Symptoms:-
Check Wallet Balance
-
Fund Your Wallet
- Log into your meCash dashboard
- Navigate to Wallet section
- Add funds to your wallet
Problem: Invalid Recipient Data
Symptoms:-
Validate Recipient Information
-
Use Correct Format for Each Currency
Webhook Issues
Problem: Webhooks Not Received
Symptoms:- No webhook events received
- Webhook delivery failures
-
Check Webhook URL
-
Verify Webhook Configuration
- Ensure webhook URL is HTTPS
- Check that your server responds with 200 OK
- Verify webhook events are enabled
-
Test with ngrok
Problem: Webhook Signature Verification Failed
Symptoms:-
Verify Signature Implementation
-
Check Webhook Secret
- Verify webhook secret in dashboard
- Ensure secret is stored securely
- Use environment variables for secrets
Rate Limiting
Problem: 429 Too Many Requests
Symptoms:-
Implement Rate Limiting
-
Use Exponential Backoff
Environment Issues
Problem: Wrong Environment
Symptoms:- API calls failing with wrong base URL
- Confusion between sandbox and production
-
Use Correct Base URLs
-
Environment Validation
Getting Help
Before Contacting Support
-
Check Documentation
- Review API reference documentation
- Check error codes and messages
- Verify request/response formats
-
Test in Sandbox
- Reproduce issue in sandbox environment
- Test with minimal request data
- Check logs for detailed error information
-
Gather Information
- API endpoint and method
- Request payload (sanitized)
- Response error message
- Timestamp of occurrence
- Your API key (last 4 characters only)
Contacting Support
Email Support:- Email: support@me-cash.com
- Subject: “API Issue - [Brief Description]”
- Include: Error details, request/response data, steps to reproduce
- Discord: Join our community
- GitHub: Report issues
- For production emergencies, use subject: “PRODUCTION EMERGENCY”
- Include: Impact description, affected transactions, immediate steps needed
Debugging Tools
-
API Logging
-
Request/Response Logging
-
Health Check Endpoint
Common Error Codes
| Error Code | Description | Solution |
|---|---|---|
UNAUTHORIZED | Invalid API key | Check API key format and validity |
FORBIDDEN | IP not whitelisted | Whitelist your IP address |
NOT_FOUND | Resource not found | Check endpoint URL and resource ID |
BAD_REQUEST | Invalid request data | Validate request payload |
RATE_LIMIT_EXCEEDED | Too many requests | Implement rate limiting |
QUOTE_EXPIRED | Quote has expired | Generate new quote |
INSUFFICIENT_BALANCE | Not enough funds | Fund your wallet |
INVALID_RECIPIENT | Invalid recipient data | Validate recipient information |
Next Steps
- API Reference - Complete endpoint documentation
- Error Handling Guide - Handle errors gracefully
- SDK & Testing Guide - Use official SDKs
- Webhook Signature Verification - Secure webhook handling

