Skip to main content

Going to Production

This guide will help you prepare your WEpayments integration for production. Follow this checklist to ensure a smooth launch.

Pre-Launch Checklist

1. Testing & Validation

  • All API endpoints tested in Dev Mode
  • Success scenarios verified
  • Error handling tested
  • Edge cases covered
  • Payment flows work end-to-end
  • Webhooks registered and tested
  • Signature verification implemented
  • Retry logic in place
  • Idempotency handling configured
  • All event types handled
  • API keys stored securely
  • HTTPS enabled on all endpoints
  • Input validation implemented
  • Rate limiting configured
  • Security headers set
  • All error codes handled
  • User-friendly error messages
  • Logging implemented
  • Monitoring set up
  • Alerting configured

2. Account Configuration

1

Verify Business Information

Ensure all business details are accurate in your dashboard
2

Configure Transfer Accounts

Set up another bank account with the same ownership for transfer funds
3

Enable Two-Factor Authentication (2FA)

After receiving access to the production panel, you must activate 2FA for enhanced security. Learn how to enable 2FA

3. API Keys & Credentials

Critical: Never expose your production API keys in client-side code or public repositories.
// βœ… Good - Using environment variables
const apiKey = process.env.WEPAYMENTS_API_KEY;

// ❌ Bad - Hardcoded key
const apiKey = 'live_sk_1234567890abcdef';
Production API Keys Checklist:
  • Generate production API keys
  • Store keys in secure environment variables
  • Remove all test keys from production code
  • Implement key rotation policy
  • Restrict API key permissions
  • Configure allowed IPs for API requests
Important: After accessing the production panel, configure the allowed IPs that can make API requests. This adds an extra layer of security to your integration. Learn how to configure allowed IPs

Launch Day

Final Steps

1

Switch to Production Keys

Update all API keys to production values
2

Enable Production Webhooks

Verify webhooks are pointing to production URLs
3

Test First Transaction

Process a small real transaction to verify everything works
4

Monitor Closely

Watch logs and monitoring tools for the first few hours
5

Be Ready to Respond

Have your team available to address any issues

Post-Launch Monitoring

For the first 24-48 hours:
  • Monitor transaction success rates
  • Watch for error spikes
  • Check webhook delivery rates
  • Review customer feedback
  • Verify settlement timing

Common Issues & Solutions

Symptoms: Many failed transactionsSolutions:
  • Check API key is correct
  • Verify endpoint URLs
  • Review error logs
  • Check rate limits
Symptoms: Webhooks not being receivedSolutions:
  • Verify webhook URL is accessible
  • Check HTTPS certificate
  • Review webhook logs in dashboard
  • Test signature verification
Symptoms: Slow response timesSolutions:
  • Implement caching
  • Optimize database queries
  • Use async processing
  • Scale infrastructure

Support During Launch

Priority Support

Contact [email protected] for launch assistance

Documentation

Reference our complete API documentation

Congratulations! πŸŽ‰

You’re now ready to go live with WEpayments. Remember:
  • Start small and scale gradually
  • Monitor everything closely
  • Respond quickly to issues
  • Keep improving the experience
Need help? We’re here for you at [email protected]