A test environment may be available depending on your organisation’s setup and the services being used.
Test environments can help organisations become familiar with BE Custody workflows, user roles, approval processes, and operational steps before using production services.
Availability, functionality, supported assets, and access arrangements may differ from the production environment.
What can a test environment be used for?
A test environment may be used to:
- Familiarise users with BE Custody
- Practise internal workflows
- Test operational processes
- Train users before production access
- Review transaction and approval flows in a non-production context
- Understand how different roles and permissions affect user actions
Is the test environment the same as production?
No. A test environment may not behave exactly like the production environment.
For example, there may be differences in:
- Available assets
- Available networks
- User access
- Transaction behaviour
- Approval workflows
- Data shown in reports or audit history
- Operational support arrangements
Users should not assume that all production features are available in the test environment.
Can I use real assets in the test environment?
No. A test environment should not be used to hold or transfer real assets.
Only use the test environment for its intended non-production purpose. If you are unsure whether you are using the correct environment, stop and check with your organisation’s administrator or Bitpanda Enterprise Custody Support before continuing.
How do I get access to a test environment?
Access to a test environment depends on your organisation’s setup and the services agreed with Bitpanda Enterprise Custody.
If you need access, contact your organisation’s administrator or Bitpanda Enterprise Custody Support.
What should I include in my request?
When requesting access to a test environment, include:
- Your organisation name
- Your name and work email address
- The reason access is required
- The users who need access
- The type of workflow or testing you want to perform
Do not include passwords, PINs, private keys, seed phrases, API keys, API secrets, or other sensitive authentication information in your request.