> ## Documentation Index
> Fetch the complete documentation index at: https://glide-9da73dea.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a connector

> Adapt the TestPay example and test its manifest, capability implementations and observed network calls.

The TestPay example demonstrates a connector with banking and screening capabilities. Its accounts, transfer results and screening decisions are fixtures. They do not establish live banking or sanctions-screening coverage.

## Start from the example

Copy `examples/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)` and `initiateTransfer(ctx, args)`.
* **Screening:** `screen(ctx, subject)`.

Read `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:

```bash theme={null}
pnpm --filter @glide-examples/build-a-connector-stripe-clone test
```

The suite checks manifest validity, the presence of declared capability implementations and the network targets supplied to the test harness. Override `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.

## Prepare for review

Follow the repository's contribution requirements. Document your connector's credentials, supported methods, failure handling and demo limits. Keep mock status explicit until real integration is verified. Publication and a trust-tier change require the applicable repository and vendor review.

## Source

[Read the TestPay example](https://github.com/glide-co/glide-mono/tree/main/examples/build-a-connector-stripe-clone). Source access is required.

## Next

* [Connector manifest](https://glide-9da73dea.mintlify.site/oss/standards/connector-manifest.md)
* [Capability interfaces](https://glide-9da73dea.mintlify.site/oss/connectors/extending.md)
* [Trust tiers](https://glide-9da73dea.mintlify.site/oss/standards/trust-tier.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.