Sandbox & Testing

Learn how to test your integration safely using Rach Payments' sandbox environment before going live.

Overview

The sandbox environment allows you to:

• ✅ Test all API endpoints without real money
• ✅ Use testnet blockchains (BSC Testnet, Sepolia, etc.)
• ✅ Receive test API keys instantly
• ✅ Simulate payment flows end-to-end
• ✅ Test webhook integrations

---

Test vs Production Keys

You'll receive two types of API keys:

Key Type	Prefix	Environment	Blockchain	Real Money
Test Key	test_sk_	Sandbox	Testnets	❌ No
Production Key	live_sk_	Production	Mainnets	✅ Yes

Using Test Keys:

curl -H "X-API-Key: test_sk_1234567890abcdef" \
  https://payments-api-dev-966260606560.europe-west2.run.app/api/v1/checkout/crypto

Using Production Keys:

curl -H "X-API-Key: live_sk_abcdef1234567890" \
  https://payments-api-dev-966260606560.europe-west2.run.app/api/v1/checkout/crypto

---

Testnet Blockchains

When using test API keys, all operations use testnet blockchains:

Mainnet	Testnet	Get Test Tokens
BSC	BSC Testnet	BSC Faucet
Ethereum	Sepolia	Sepolia Faucet
Polygon	Mumbai	Mumbai Faucet
Tron	Shasta	Shasta Faucet
Solana	Devnet	Solana Faucet

---

Getting Test Tokens

Step 1: Get Native Tokens (for gas fees)

Use the faucets above to get native tokens (BNB, ETH, MATIC, etc.) for transaction fees.

Step 2: Get Test USDT/USDC

Most testnets have test stablecoin contracts:

BSC Testnet USDT:

Contract: 0x337610d27c682E347C9cD60BD4b3b107C9d34dDd

Sepolia USDT:

Contract: 0x7169D38820dfd117C3FA1f22a697dBA58d90BA06

Mumbai USDT:

Contract: 0x0FA8781a83E46826621b3BC094Ea2A0212e71B23

You can mint test tokens from these contracts using block explorers or web3 tools.

---

Testing Payment Flow

1. Create Test Checkout

curl -X POST https://payments-api-dev-966260606560.europe-west2.run.app/api/v1/checkout/crypto \
  -H "X-API-Key: test_sk_YOUR_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 10.00,
    "currency": "USDT",
    "network": "BSC",
    "customer_email": "test@example.com",
    "reference": "TEST-001"
  }'

2. Send Test Tokens

Use MetaMask or another wallet to send test USDT to the deposit address.

3. Monitor Payment Status

curl -X GET https://payments-api-dev-966260606560.europe-west2.run.app/api/v1/checkout/CHECKOUT_ID \
  -H "X-API-Key: test_sk_YOUR_TEST_KEY"

4. Receive Webhook

If you've configured webhooks, you'll receive a notification when the payment is detected:

{
  "event": "payment.received",
  "checkout_id": "checkout_xyz789",
  "amount": "10.00",
  "currency": "USDT",
  "network": "BSC",
  "txn_hash": "0x123abc...",
  "confirmations": 12,
  "status": "confirmed"
}

---

Testing Wallet Service

Create Test Wallet

curl -X POST https://payments-api-dev-966260606560.europe-west2.run.app/api/v1/wallet/customer/create \
  -H "X-API-Key: test_sk_YOUR_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "customer_id": "test_user_123",
    "networks": ["BSC"]
  }'

Send Test Tokens to Wallet

Send test USDT to one of the generated addresses.

Check Balance

curl -X GET https://payments-api-dev-966260606560.europe-west2.run.app/api/v1/wallet/customer/WALLET_ID/balance?network=BSC \
  -H "X-API-Key: test_sk_YOUR_TEST_KEY"

---

Webhook Testing

Using ngrok for Local Testing

1. Install ngrok:

   npm install -g ngrok

2. Start your local server:

   node server.js
   # Running on http://localhost:3000

3. Expose with ngrok:

   ngrok http 3000

4. Configure webhook URL: Use the ngrok URL when creating checkouts:

   {
     "amount": 100,
     "currency": "USDT",
     "network": "BSC",
     "callback_url": "https://abc123.ngrok.io/webhooks/payment"
   }

Webhook Verification in Test Mode

Even in test mode, verify webhook signatures to ensure your verification code works:

const crypto = require('crypto');

function verifyWebhook(payload, signature, secret) {
  const hmac = crypto.createHmac('sha256', secret);
  hmac.update(JSON.stringify(payload));
  const computed = hmac.digest('hex');
  
  return crypto.timingSafeEqual(
    Buffer.from(signature),
    Buffer.from(computed)
  );
}

---

Common Test Scenarios

Scenario 1: Successful Payment

1. Create checkout
2. Send exact amount to deposit address
3. Wait for confirmations
4. Verify webhook received
5. Check merchant balance credited

Scenario 2: Underpayment

1. Create checkout for 100 USDT
2. Send only 50 USDT
3. Payment status should remain "pending"
4. Send remaining 50 USDT
5. Payment completes

Scenario 3: Overpayment

1. Create checkout for 100 USDT
2. Send 150 USDT
3. Payment completes for 100 USDT
4. Extra 50 USDT goes to merchant balance

Scenario 4: Expired Checkout

1. Create checkout (expires in 30 minutes by default)
2. Wait for expiration
3. Try to pay - should not credit merchant

---

Best Practices

Testing Checklist

• ✅ Test all supported networks (BSC, ETH, POL, TRX, SOL)
• ✅ Test both USDT and USDC where supported
• ✅ Test webhook signature verification
• ✅ Test error handling (network failures, invalid addresses)
• ✅ Test concurrent payments
• ✅ Test wallet balance tracking
• ✅ Performance test with multiple API calls

---

Differences from Production

Feature	Test Mode	Production Mode
Blockchain	Testnets	Mainnets
Currency	Test tokens	Real crypto
Confirmations	Same as mainnet	Same as mainnet
API Response Time	Similar	Similar
Webhooks	Fully functional	Fully functional
Rate Limits	More lenient	Standard limits

---

Transitioning to Production

When ready to go live:

1. Switch to production API key:

   const apiKey = process.env.NODE_ENV === 'production'
     ? process.env.RACH_PROD_KEY
     : process.env.RACH_TEST_KEY;

2. Update webhook endpoints to production URLs

3. Test with small real amounts first

4. Monitor closely for the first few transactions

5. Set up monitoring and alerts

---

Need Help?

If you encounter issues during testing:

• Check API Reference for endpoint details
• Review Crypto Gateway Integration
• Review Wallet Service Integration
• Email support@rach.finance