Process and Environments

Our goal is to give you all the support you need throughout the integration. This page sets expectations for what to expect during the integration process.

Environments

Environment	URL	Description
Development	earn-api-dev.partner.env.tesseractinvestment.dev	Environment to develop against. All APIs are available but Tesseract does not settle its side of the outstanding balance.
Test	earn-api-test.partner.env.tesseractinvestment.dev	Copy of production where the partner can develop and test daily settlement with small amounts of real crypto (no test net support). Product list is a subset of production.
Production	earn-api.tesseractinvestment.com	Live partner integration.

Process

Intro call

The purpose of the call is to get the project started on the right foot. Topics typically covered:

• Walk through the integration process and developer site contents.

• Address questions raised while reading the documentation.

• Agree on the communication channel between engineering teams.

• Agree on the practicalities of authentication credential delivery and exchange of settlement wallet addresses.

• Discuss integration timeline.

Prerequisite: a mutual NDA has been signed.

Authentication credentials delivery

Authentication credentials are delivered to partners using Bitwarden Send. Recipients should store credentials in a password manager or similar. Development credentials can be used from developer workstations; Test and Production credentials should only be used in cloud-based systems.

Exchange of settlement wallet addresses

Both parties need a wallet address per currency for outstanding-balance settlement in Test and Production. Tesseract sends Test environment addresses as soon as development has started. Tesseract can finalize Test configuration once the partner's wallet addresses are received.

Gate to production

Once all tasks in Solution Architecture are done, the partner should test in the Test environment. Tesseract can help verify reception of assets and check report contents. Once the partner believes testing is complete, Tesseract performs a final check before preparing access to Production.

Authentication credential delivery and wallet address exchange happen the same way as for Test.

Prerequisite for production access: an Alliance Agreement is signed.

Acceptance test

Acceptance tests are done in the Production system to verify a solid integration and correct configuration of the wallet addresses on both sides. See Acceptance Testing for details.

Go-live

The service can be opened as soon as the acceptance test result is satisfactory for both parties.