integration-builder

Scaffolding a provider integration requires running the project generator to create a consistent npm workspace package under packages/<provider>. The generator outputs a ready-to-register marketplace integration package with adapters, credentials, and dependency injection wiring.

Adding a new external service like a payment or shipping provider requires scaffolding a provider package that implements adapters, credentials schemas, and webhook processing. The Integration Builder standardizes this scaffolding to ensure the new service adheres to marketplace contracts and patterns.

Yes, the Integration Builder generates webhook processing and health check components alongside adapters, credentials schemas, and i18n files. These components are scaffolded to align with marketplace contracts and reference patterns, ensuring the integration is fully formed and testable.

Yes, scaffolding includes internationalization (i18n) and test scaffolds alongside adapters and widget injection. The generated package mirrors the gateway-stripe reference patterns, providing a fully-formed integration provider package with all necessary metadata and testing frameworks pre-configured.

A provider integration should follow the documented integration contract and mirror the gateway-stripe reference patterns. This ensures the scaffolded package includes correct metadata, dependency injection wiring, and health checks, resulting in a ready-to-register marketplace integration that meets compliance requirements.

Creating a marketplace integration from scratch is boilerplate-heavy and error-prone because it requires manually wiring adapters, credentials, and webhooks. The Integration Builder standardizes scaffolding to eliminate these manual errors and ensure marketplace contracts are followed consistently across provider packages.