> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.redpincompany.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.redpincompany.com/_mcp/server.

# Environments

> Understanding Redpin's sandbox and production environments for development and testing

Redpin provides separate environments for development and production use, each designed for different stages of your integration lifecycle.

#### Sandbox Environment

**Purpose**: Development, testing, and integration validation

**Base URL**: `https://sandbox.redpincompany.com`

* Simulated payment flows without real money transfers
* Full API functionality for testing
* Webhook testing capabilities
* No regulatory compliance requirements
* Test data automatically cleared periodically

#### Production Environment

**Purpose**: Live payment processing with real transactions

**Base URL**: `https://api.redpincompany.com`

* Real money transfers and currency conversions
* Full regulatory compliance required
* Enhanced security monitoring
* Business-critical SLA guarantees
* Complete audit trails

> **Warning**
>
> Never use production credentials in development environments. Always maintain strict separation between sandbox and production configurations.

## Key differences

#### Sandbox

* **Transactions**: Simulated payments
* **Data**: Temporary, may be reset
* **Credentials**: Sandbox client ID/secret
* **Support**: Self-service documentation
* **Access**: Available immediately

#### Production

* **Transactions**: Real money transfers
* **Data**: Permanent with audit trails
* **Credentials**: Production client ID/secret
* **Support**: Dedicated technical support
* **Access**: Requires compliance verification

## Credential management

#### Getting sandbox access

**Quick setup for development**:

1. Contact Partner Integrations Team
2. Provide basic partner information
3. Receive credentials within 24 hours

#### Getting production access

**Requirements for live deployment**:

1. Complete sandbox integration testing
2. Submit production access request
3. Pass security and compliance review
4. Execute business agreements

## Best practices

#### Security

* Store credentials in environment variables
* Never commit secrets to code repositories
* Use different credentials for each environment
* Implement credential rotation procedures

#### Testing

* Test complete payment workflows in sandbox
* Validate all API endpoints and error scenarios
* Verify webhook delivery and signatures
* Simulate edge cases and failures

#### Deployment

* Separate deployment pipelines
* Independent monitoring systems
* Isolated webhook endpoints
* Environment-specific configurations

## Next steps

Ready to continue your integration? Follow these recommended steps:

#### Set up authentication

Configure [OAuth 2.0 authentication](/api-guide/getting-started/authentication) for your sandbox environment

#### Make your first payment

Complete the [step-by-step tutorial](/api-guide/getting-started/making-your-first-payment) to process a test payment

#### Plan production migration

Review [sandbox to production](/api-guide/getting-started/sandbox-to-production) requirements and timeline