Hyperswitch Prism

Product Introduction

1. Definition: Hyperswitch Prism is a stateless, open-source, multi-language software development library designed for payment processing integrations. Technically, it functions as a unified API abstraction layer, translating a single, consistent request schema into the diverse native APIs of various payment service providers (PSPs) or "connectors."
2. Core Value Proposition: It exists to eliminate the immense technical debt and development complexity of integrating and maintaining multiple payment gateways. By providing "one integration for any payment processor," Prism enables developers to achieve payment processor redundancy, implement smart routing rules, and switch providers with minimal code changes, thereby reducing lock-in and operational risk.

Main Features

1. Unified Payment API Schema: Prism defines a single, type-safe data structure (using Protocol Buffers) for core payment operations like authorize, capture, and refund. This schema remains constant regardless of the underlying payment processor (e.g., Stripe, Adyen, Braintree). How it works: A developer's application sends a payment request in Prism's unified format. The library's core logic then transforms this request into the specific HTTP request format, authentication method, and data model required by the target connector.
2. Stateless & PCI Scope-Reducing Architecture: The library is deliberately designed to be stateless; it does not store transaction data, logs Personally Identifiable Information (PII), or persist payment credentials between requests. How it works: Credentials and sensitive data are passed in via the request object and exist only for the lifetime of the API call within the client. This design choice helps merchants reduce their PCI DSS compliance scope, as card data can be routed directly to a PCI-certified vault (the processor's or their own) without touching the merchant's infrastructure via Prism.
3. Polyglot SDK Support with Native Implementations: Prism offers officially supported Software Development Kits (SDKs) for Node.js, Python, Java/Kotlin, and Rust. These are not thin wrappers but are built to provide idiomatic, type-safe interfaces in each language. How it works: The core business logic and connector integrations are written in Rust for performance and safety. Language-specific SDKs are generated and/or implemented to provide a native-feeling API, handling serialization, gRPC communication (where applicable), and error mapping for the developer.

Problems Solved

1. Pain Point: The extreme fragmentation and inconsistency of payment processor APIs. Each PSP has unique endpoints, authentication (API keys, digital signatures), error code formats, idempotency handling, and undocumented behavioral quirks, making integrations brittle, time-consuming, and expensive to maintain.
2. Target Audience: Development teams at digital-native businesses (SaaS companies, DTC e-commerce, fintech startups), platform engineers building payment services, and in-house payments engineers at larger merchants who manage direct PSP integrations. The primary persona is a "Full-Stack or Backend Developer" tasked with implementing payments.
3. Use Cases: 1) Multi-Processor Redundancy: A merchant integrates with Stripe and Adyen via Prism. If Stripe experiences an outage, a routing rule can failover payments to Adyen instantly. 2) Regional Payment Optimization: An e-commerce site uses Prism to route EUR transactions to Adyen (strong in Europe) and USD transactions to Stripe, based on currency. 3) Legacy System Modernization: A company replacing an old, monolithic payment system can use Prism as a new, unified integration layer to add modern PSPs without rewriting core logic.

Unique Advantages

1. Differentiation: Unlike full-stack Payment Orchestration Platforms (POPs) which are stateful SaaS services or platforms requiring vendor lock-in, Prism is a lightweight, open-source (Apache 2.0) library. It provides the core transformation and unification logic without mandating a specific database, retry engine, or UI. Developers embed it directly into their application stack.
2. Key Innovation: It is "extracted from production hardening." Prism's connector logic is not built from API specs alone; it is distilled from years of iterative bug fixes, performance tuning, and validation against real sandbox and production environments within Juspay Hyperswitch (a large-scale open-source payments platform). This means its integrations battle-test common real-world edge cases and discrepancies between documentation and actual PSP behavior.

Frequently Asked Questions (FAQ)

1. How does Hyperswitch Prism handle PCI DSS compliance? Prism is designed as a PCI scope-reduction tool. It does not store, log, or process card data by default. You can choose to send card data directly through Prism to a PSP's vault (keeping it off your servers) or use your own vault and pass only tokens. Its stateless nature means it does not retain sensitive authentication data.
2. Can I use Hyperswitch Prism with my existing payment gateway? Yes, if the payment gateway (connector) is already implemented in Prism's supported list. You would configure your existing gateway credentials in the ConnectorConfig object. If your gateway is not supported, you would need to implement a new connector using Prism's Rust framework, which involves mapping its API to the unified schema.
3. What is the difference between Hyperswitch Prism and Juspay Hyperswitch? Juspay Hyperswitch is a full-featured, self-hostable open-source payments platform that includes a stateful router, database, analytics dashboard, and retry logic. Hyperswitch Prism is a stateless library extracted from Hyperswitch's connector layer. Think of Hyperswitch as the complete car and Prism as the highly-tuned, universal transmission you can install in your own vehicle.
4. Does Prism support recurring payments and subscriptions? The current focus of Prism, as indicated in the documentation, is on core payment processing flows (auth, capture, refund). Support for broader commerce operations like subscriptions, fraud, and payouts is noted as a future aspiration. You would need to verify the specific payment method support (like saved cards) for subscription use cases with your target connector.
5. Is there a cost to using Hyperswitch Prism? No. Hyperswitch Prism is open-source software released under the permissive Apache License 2.0. There are no licensing fees. You incur only the infrastructure costs of running your application and the standard processing fees charged by your chosen payment service providers.