Getting Started

Sandbox to production

This guide outlines the requirements and process for moving your integration from sandbox testing to production deployment.

Prerequisites

Before initiating production migration, ensure all sandbox testing is complete and security requirements are met.

  • Completed sandbox integration testing
  • Validated all payment flows
  • Implemented comprehensive error handling
  • Configured webhook endpoints
  • Reviewed security requirements
  • Performance benchmarked under expected load

Technical requirements

All production integrations must meet strict security standards for financial data protection.

HTTPS enforcement:

  • All API endpoints must use HTTPS
  • Webhook URLs must be secure (HTTPS)
  • Certificate validation enabled

Credential security:

  • OAuth credentials stored securely
  • No hardcoded secrets in code
  • Environment-based configuration
  • Credential rotation procedures

Webhook security:

  • Webhook signature verification implemented
  • Endpoint authentication configured
  • Request validation and sanitization
  • Rate limiting and DDoS protection

Error handling:

  • Comprehensive error handling for all scenarios
  • Graceful degradation for service disruptions
  • Logging and monitoring implementation
  • Retry logic with exponential backoff

Complete end-to-end testing ensures smooth production deployment and reduces post-launch issues.

Payment flow validation:

  • Complete end-to-end payment testing
  • Third-party customer registration
  • Quote generation and acceptance
  • Recipient management
  • Payment creation and completion

Webhook delivery confirmation:

  • Webhook endpoint accessibility
  • Event handling for all supported events
  • Delivery retry mechanisms
  • Failed delivery handling

Error scenario handling:

  • Authentication failures
  • Validation errors
  • Rate limiting responses
  • Network connectivity issues
  • Service unavailability

Performance benchmarking:

  • Response time measurement
  • Throughput testing
  • Load testing under expected volumes
  • Resource utilization monitoring

Operational readiness

Proper monitoring setup prevents post-launch issues and ensures smooth customer experience.

Essential monitoring:

  • API performance monitoring
  • Error rate tracking
  • Payment status monitoring
  • Webhook delivery monitoring

Alerting setup:

  • Response time thresholds
  • Error rate alerts
  • Failed webhook notifications
  • System availability alerts

Technical support procedures:

  • Error troubleshooting workflows
  • Escalation pathways
  • Business hour coverage
  • Emergency response plans

Documentation requirements:

  • Internal integration documentation
  • Operational runbooks
  • Troubleshooting guides
  • Team training materials

Work with your legal and compliance teams to ensure all regulatory requirements are met for your jurisdiction.

Key areas to review:

  • Customer data protection requirements
  • Financial services compliance
  • Cross-border payment regulations
  • Audit trail maintenance

Production deployment

Production credentials are provided after completing partner onboarding and security review.

Obtain production credentials:

  • Submit production access request
  • Complete partner onboarding verification
  • Receive production OAuth credentials
  • Validate credential format and permissions

Update configuration:

  • Replace sandbox base URLs with production URLs
  • Update OAuth client ID and secret
  • Configure production webhook endpoints
  • Verify environment-specific settings

Test authentication:

  • Validate OAuth token generation
  • Test API endpoint accessibility
  • Confirm webhook endpoint reachability
  • Verify security configurations

Base URL updates:

  • Sandbox: https://sandbox.redpincompany.com
  • Production: https://api.redpincompany.com

Webhook endpoint migration:

  • Update webhook URLs to production endpoints
  • Verify SSL certificate validity
  • Test webhook delivery mechanisms
  • Configure event subscriptions

Rate limiting adjustment:

  • Review production rate limits
  • Adjust client-side rate limiting
  • Implement appropriate backoff strategies
  • Monitor usage patterns

Use this comprehensive checklist to ensure nothing is missed during production deployment.

Pre-deployment:

  • Production credentials obtained and configured
  • Base URLs updated to production endpoints
  • Webhook endpoints tested and verified
  • SSL certificates validated
  • Error handling implementation verified
  • Monitoring systems configured and active
  • Support processes documented and ready
  • Team training completed
  • Documentation updated

Deployment:

  • Configuration deployed to production
  • Smoke tests executed successfully
  • Webhook delivery confirmed
  • Authentication flow validated
  • Error scenarios tested
  • Performance benchmarks met

Post-deployment:

  • Production monitoring active
  • Error rates within acceptable limits
  • Webhook delivery functioning correctly
  • Support processes operational
  • Documentation accessible
  • Team prepared for live operations

Testing in production

Phased rollout minimizes risk and allows for controlled scaling of your production integration.

Phase 1: Limited testing

  • Small volume transactions
  • Selected customers or regions
  • Enhanced monitoring
  • Immediate issue response

Phase 2: Expanded testing

  • Increased transaction volumes
  • Broader customer base
  • Performance monitoring
  • Capacity validation

Phase 3: Full deployment

  • Complete feature rollout
  • All customers and regions
  • Standard monitoring
  • Operational procedures
Technical metrics
  • API response times
  • Error rates and types
  • Payment success rates
  • Webhook delivery rates
  • System availability
  • Response time percentiles
Business metrics
  • Transaction volumes
  • Customer conversion rates
  • Payment completion times
  • Support ticket volumes
  • Error rate trends
  • Capacity utilization

Support and escalation

Technical support

First-line support:

  • API documentation review
  • Error response analysis
  • Configuration validation
  • Common issue resolution

Escalation procedures:

  • Technical team contact
  • Priority-based response
  • Business hour coverage
  • Emergency support access
Business support

Account management:

  • Business relationship support
  • Agreement questions
  • Commercial discussions
  • Strategic planning

Compliance assistance:

  • Regulatory guidance
  • Process validation
  • Documentation support
  • Audit preparation

Success metrics

Technical metrics

Performance indicators:

  • API response time < 2 seconds
  • Error rate < 0.1%
  • Webhook delivery rate > 99%
  • System availability > 99.9%
Business metrics

Operational indicators:

  • Payment success rate > 95%
  • Customer onboarding completion > 90%
  • Support ticket resolution < 24 hours
  • Documentation completeness 100%