How Integration Works

This section outlines the typical path teams follow when integrating the Lombard SDK, from initial alignment through production launch. It is intended for founders, product leaders, and technical decision-makers who want to understand the process end to end before diving into implementation details.

Integration at a Glance

The integration starts by defining the scope, expectations and product goals.

Teams typically:

Outline use cases and product goals
Review supported assets and chains
Align on security assumptions and operational boundaries
Discuss compliance and regulatory requirements
Receive a Partner ID or configure CAPTCHA requirements

This ensures both sides are clear on what’s being built before integration work begins.

Once aligned, teams explore the SDK and see how everything works in practice.

This involves:

Navigating the Playground
Testing the specific capabilities planned for launch
Understanding how different flows behave

The goal: validate assumptions and get comfortable with the SDK before committing to implementation.

With a clear target in mind, teams use the Playground to configure and test their integration.

At this stage:

Set parameters for selected flows
Validate execution paths
Simulate asset behavior and cross-chain routing
Generate example SDK code
Debug configurations in a non-production environment

This replaces trial-and-error in production and reduces launch risk.

The final step: launching your Bitcoin product to users.

At launch:

The SDK integrates into application logic
Users interact with Bitcoin features through the product’s UI
Lombard operates custody, validation, settlement, and monitoring in production
Results and lifecycle events surface through the SDK

How Integration Works

Integration at a Glance

Define the Product Requirements

Test the Capabilities

Configure and Validate Your Integration

Integrate and Ship