Overview

Connector Service

One integration. Any payment processor. Zero lock-in.

License: Apache 2.0arrow-up-right

A high-performance payment abstraction library, and part of Juspay Hyperswitcharrow-up-right β€” the open-source, composable payments platform with 40,000+ GitHub stars, trusted by leading brands worldwide.

GitHubarrow-up-right Β· Websitearrow-up-right Β· Documentationarrow-up-right


🎯 Why Connector Service?

Integrating multiple payment processors shouldn't require months of engineering effort. Yet every PSP has different APIs, error codes, authentication methods, and idiosyncrasies.

Connector Service solves this with a unified schema that works across all payment providers.

❌ Without Connector Service
βœ… With Connector Service

πŸ—‚οΈ 50+ different API schemas

πŸ“‹ Single unified schema

⏳ Months of integration work

⚑ Hours to integrate

πŸ”— Brittle, provider-specific code

πŸ”“ Portable, provider-agnostic code

🚫 Hard to switch providers

πŸ”„ Change providers in 1 line


✨ Features

  • πŸ”Œ 50+ Connectors β€” Stripe, Adyen, Braintree, PayPal, Worldpay, and more

  • 🌍 Global Coverage β€” Cards, wallets, bank transfers, BNPL, and regional methods

  • πŸš€ Zero Overhead β€” Rust core with native bindings, no overhead

  • πŸ”’ PCI-Compliant by Design β€” Stateless, no data storage


πŸ—οΈ Architecture

Payment & Capture Flow Sequence

spinner

πŸš€ Quick Start

Basic Usage

Node.js

Java


πŸ”„ Switching Providers

One of Connector Service's core benefits: switch payment providers by changing one line.

No rewriting. No re-architecting. Just swap the connector.


🌊 Abstracted Payment Flows

Connector Service unifies complex payment operations across all processors:

Core Payment Operations

Flow
Description

Authorize

Hold funds on a customer's payment method

Capture

Complete an authorized payment and transfer funds

Void

Cancel an authorized payment without charging

Refund

Return captured funds to the customer

Sync

Retrieve the latest payment status from the processor

Advanced Flows

Flow
Description

Setup Mandate

Create recurring payment authorizations

Incremental Auth

Increase the authorized amount post-transaction

Partial Capture

Capture less than the originally authorized amount

Each flow uses the same unified schema regardless of the underlying processor's API differences. No custom code per provider.


One integration pattern. Any service category.


πŸ› οΈ Development

Prerequisites

  • Rust 1.70+

  • Protocol Buffers (protoc)

Building from Source

Project Structure


πŸ”’ Security

  • Stateless by design β€” No PII or PCI data stored

  • Memory-safe β€” Built in Rust, no buffer overflows

  • Encrypted credentials β€” API keys never logged or exposed

Reporting Vulnerabilities

Please report security issues to [email protected]envelope.


⬆ Back to Top

Made with by Juspay hyperswitcharrow-up-right

Test Sync

This is a test to verify docs sync workflow.

Test auto-trigger

Last updated

Was this helpful?