Start from the example
Copyexamples/build-a-connector-stripe-clone from the product repository into your working package. Rename the package and update src/manifest.ts.
The manifest describes identity, capabilities, supported regions and currencies, network hosts and vendor permissions. Replace fictional vendor and licensing data with verified information for your integration. A manifest entry does not itself establish a license or supported payment route.
Implement the capabilities
The example uses the interfaces in@repo/connectors-base:
- Banking:
listAccounts(ctx)andinitiateTransfer(ctx, args). - Screening:
screen(ctx, subject).
src/capabilities/banking.ts and src/capabilities/screening.ts. Replace their fixture responses with the relevant vendor calls. Preserve the distinction between pending, settled and failed transfers, and handle uncertain responses before retrying.
Run contract tests
With the repository dependencies installed, run from its root:getRecordedFetchTargets() with captured requests to test egress hosts. Its default empty list does not prove that all possible network calls are declared.
Passing fixture tests does not verify a live vendor integration. Exercise the required account, payment and screening paths against the vendor’s supported test environment before using real funds.