Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.me-cash.com/llms.txt

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

meCash provides two isolated environments so you can build, test, and launch without risk. Use the sandbox for iterative development and only switch to production once your flows are certified.
Dashboard toggle for switching between sandbox and production environments

Sandbox

https://sandboxapi.me-cash.com
Simulated money movement, ideal for integration testing and demos.

Production

https://api.me-cash.com
Processes real transactions once your business is approved.

​
Sandbox environment

The sandbox mirrors live behavior while keeping funds virtual—perfect for prototyping and QA.
  • Authentication: Use your sandbox API keys from the dashboard.
  • Webhooks & events: All endpoints fire test payloads so you can validate handlers.
  • Data reset: Wallet balances and transactions are synthetic and may reset periodically.
How to access
  1. Create your business account.
  2. Follow the Quickstart to generate sandbox keys.
  3. Whitelist the IPs that will call the API via /ip-whitelisting.
Keep development strictly in sandbox until you have end‑to‑end tests, webhook verification, and monitoring in place.

​
Production environment

Production is where your customers experience real payouts, collections, and settlements.
  • Base URL: https://api.me-cash.com.
  • Traffic: Real money movement with full compliance monitoring.
  • Rate limits: Higher throughput tiers are available on request—contact support with your projected volumes.
  • API keys: Issued separately from sandbox; never reuse test keys in production.
Access prerequisites
  1. Complete KYB.
  2. Finish smoke testing in sandbox, including webhook verification.
  3. Request production keys from the dashboard or by emailing support@me-cash.com.
  4. Whitelist the production IP addresses that will originate live traffic.
Keep production credentials in a secure secrets manager. Rotate keys regularly and remove unused IP addresses to minimize attack surface.

​
Best practices

Deployment workflow

  1. Build and test in sandbox.
  2. Run automated contract and webhook tests.
  3. Perform a supervised pilot in production.
  4. Monitor logs and metrics continuously.

Environment hygiene

  • Maintain separate API keys and IP whitelists.
  • Document every environment change.
  • Use feature flags to control rollout.
  • Set alerts for 4XX/5XX spikes.

​
Need help?