About Kraken
Kraken operates a digital-asset trading platform. The Crassula connector connects the supported provider services with the operational layer of a branded crypto product. Teams should confirm assets, trading pairs, account eligibility and payment routes for their deployment. The connection does not imply a fixed launch time, universal card payouts or access to every product offered by Kraken.
Connecting a digital-asset exchange journey
An exchange connector links a customer-facing product with the provider functions enabled for trading or conversion. Crassula provides the surrounding account and operational workflows for the agreed setup. A clear journey should show what the customer requested, how it was processed and what result was returned.
- Identify supported assets, pairs and account arrangements.
- Map customer requests to provider orders and references.
- Define handling for execution results and related balance updates.
Trading, custody and fiat payments are separate parts of a digital-asset product. Each needs an appropriate service and an agreed operating model. Planning the connections between them helps operators trace a customer request and explain the outcome without presenting an unconfirmed asset list, payment route or launch timeframe.
Working with the connector
Crassula provides the software layer for organising customer journeys and operational processes around the connected service. A team can bring the functions included in its implementation into a branded product, while retaining a common place to review customer information, service requests and the resulting operational records. The provider continues to deliver its part of the service under the relevant agreement.
A useful starting point is to map the customer journey from the initial request to its final outcome. Define which information is submitted, what response is expected, which status is shown to the customer and how an operator handles an exception. This makes it easier to design a clear experience and to identify where automated processing or human review is appropriate.
Planning your implementation
Agree the required functions with Crassula and the provider, then test the complete journey in the available test environment. Include successful requests, incomplete data, unsuccessful responses and recovery after an interruption. Establish responsibility for customer support, operational follow-up and changes to the provider service. The connector can then become part of a documented product workflow, with clear expectations for customers and the team operating it.
Provider and connector overview
The gallery gives a provider-specific visual overview. Official imagery is included where available, alongside a simplified explanatory diagram of the connector’s role in a Crassula product.
