> For the complete documentation index, see [llms.txt](https://docs.one-cp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.one-cp.com/integration-and-development/testing.md).

# Testing & Development

Testing and development resources for 1-CP Corporate Checkout

This section provides everything you need to test and validate your 1-CP Corporate Checkout integration, from environment setup to certification requirements.

## 🌍 Environment Overview

1-CP operates two main environments to support your development lifecycle:

### Staging Environment (`*.1-cp.io`)

* **Purpose**: Development, testing, and integration validation
* **Dashboard**: [dash.1-cp.io](https://dash.1-cp.io)
* **API Base**: `https://api.1-cp.io`
* **Features**: Full feature parity with production, safe for testing

### Production Environment (`*.1-cp.com`)

* **Purpose**: Live transactions and production workloads
* **Dashboard**: [dash.1-cp.com](https://dash.1-cp.com)
* **API Base**: `https://api.1-cp.com`
* **Features**: Live payment processing, real money transactions

## 📋 Testing Workflow

### 1. Environment Setup

Start by configuring your staging environment with test credentials and business units.

**→** [**Test Environment Setup**](/integration-and-development/testing/test-credentials.md)

### 2. Integration Testing

Validate your integration using our comprehensive test scenarios and provider-specific test cards.

**→ Payment Provider Test Cards:**

* [Stripe Test Credentials](/configuration-and-setup/payment/receiving/stripe-test-credentials.md)
* [Gateway Test Credentials](/configuration-and-setup/payment/receiving/gateway-test-credentials.md)

### 3. Error Handling

Ensure your application handles all error scenarios gracefully.

**→** [**Error Messages & Troubleshooting**](/integration-and-development/testing/error-messages.md)

### 4. Certification

Complete our certification process to validate your integration before going live.

**→** [**Certification Process**](/integration-and-development/testing/certification.md)

## 🔧 Testing Best Practices

### Comprehensive Test Coverage

* ✅ **Happy Path**: Successful transaction flows
* ✅ **Error Scenarios**: Payment failures, network issues, validation errors
* ✅ **Edge Cases**: Expired cards, insufficient funds, currency mismatches
* ✅ **User Experience**: Loading states, error messages, mobile responsiveness
* ✅ **Webhooks**: Event delivery, retry logic, signature verification

### Data Management

* Use realistic but obviously fake test data
* Implement proper data cleanup procedures
* Test with various currencies and payment methods
* Validate tax calculation scenarios

### Security Testing

* Verify SSL/TLS implementation
* Test webhook signature validation
* Validate input sanitization
* Check authorization and authentication flows

## 🚀 Ready to Start Testing?

1. [**Set up your test environment**](/integration-and-development/testing/test-credentials.md) with staging credentials
2. **Configure payment methods** using provider-specific test cards
3. **Run through certification scenarios** to validate your integration
4. **Handle error cases** to ensure robust error handling

Need help? Contact our support team at <support@one-cp.com> or check our comprehensive error handling guide.