Environments
EFIcyent provides two dedicated environments to help you build, test and launch with confidence. Each environment is purpose-built for a different stage of your integration journey, starting from sandbox development to live production deployment.
Sandbox Environment:
The sandbox is your safe space for development and testing. It mirrors the core behavior of the production environment, allowing you to mirror end-to-end flows without triggering the actual transactions or modifying the live data.
Use the Sandbox to:
- Build and test your workflows.
- Validate API requests and responses.
- Run QA checks before going live.
- Replicate user journeys and transaction outcomes.
A Customer Success Manager (CSM) can help you get started. They will give you test credentials, assist you with setting up your sandbox account and control user access. Throughout your integration phase, our team will also keep you informed on key updates related to compliance, legal and technical requirements.
Base URLs for Sandbox:
Parameter | URL |
---|---|
Demo Frontend | https://eficyent-app.rare-able.com |
API Endpoint | https://admin-eficyent.rare-able.com/api |
Production Environment
After your integration has been thoroughly tested and found to be compliant, you can go to production, which is the live setting where actual transactions and user data are handled.
Before moving to the production stage, ensure the following steps are completed:
- Onboarding and identity verification such as KYC and AML checks.
- Legal documentation and agreement signing.
- Successful testing in sandbox
- Implementation of security protocols like IP whitelisting.
Production is strictly secured, audited and optimized for performance, reliability and compliance. All live API activity will reflect in real-time dashboards and user accounts.
Base URLs for Production:
Frontend App | API Endpoint |
---|---|
Demo Frontend | https://app.eficyent.com |
API Endpoint | https://v1-ocnetwewez.eficyent.com/api/ |
Execution Tips:
- Make sure to conduct full testing in the sandbox before deploying to the production.
- Keep your API keys separate for every environment.
- Make sure environment-specific settings, such as IP whitelists and callback URLs, are mapped accurately.
- Avoid utilizing the sandbox with actual user data.