Sandbox & Production Environments

Our integration platform provides separate sandbox and production environments, creating a reliable and secure foundation for testing and deploying your solutions. The sandbox environment is designed to closely replicate production conditions, allowing you to thoroughly test and refine your integrations before transitioning to the live production environment.

Environment URLs

Use the following sandbox and production URLs to connect to their respective services.

Sandbox URLs

Service	URLs
Onboarding	https://boarding-sb.clearent.net/
Payments	http://gateway-sb.clearent.net/
Hosted Payment Page	https://hpp-sb.clearent.net/hpp/{MID}/{TID}

Coming Soon: We are developing an enhanced Integration (INT) environment that will replace the current sandbox. This new environment will more precisely mirror production conditions and provide expanded testing capabilities, further improving the developer experience.

Production URLs

Service	URLs
Onboarding	https://boarding.clearent.net/
Payments	https://gateway.clearent.net/
Hosted Payment Page	https://hpp.clearent.net/hpp/{MID}/{TID}

Go-Live Checklist

Ensure the following items are completed before transitioning to production:

1

Certification testing completed

Your integration must pass the required certification process before moving to production. For details, refer to the Integration Process article.

2

Sandbox URLs updated to production URLs

Update all API calls to use production URLs by removing -sb from your sandbox endpoints and src in your code.

3

Sandbox API keys replaced with production API keys

Sandbox keys will not work in production. Production API keys will be sent either to:

• The email address you provided, or

• A webhook URL you specify for your newly onboarded merchants

Your integration won’t begin hitting the production environment until both the API URLs are updated and the production API keys are being used.

4

Additional operational go-live details reviewed

Confirm all operational readiness steps, including:

• Terminal deployment settings

• Support and escalation procedures

• Internal team availability to support your merchants at launch