# Product Overview ### What is Prism? Prism is a stateless, unified connector library to connect with any payment processor. It is extracted out of the hardened integrations through continuous testing & iterative bug fixing over years of usage within [Juspay Hyperswitch](https://github.com/juspay/hyperswitch). #### Why are payment processor integrations such a big deal? Every payment processor has diverse APIs, error codes, authentication methods, pdf documents to read, and behavioural differences between the actual environment and documented specs. A small mistake or oversight can create a huge financial impact for businesses accepting payments. Thousands of enterprises around the world have gone through this learning curve and iterated and fixed payment systems over many years. All such fixes/improvements/iterations are locked-in as tribal knowledge into Enterprise Payment Platforms and SaaS Payment Orchestration solutions. Hence, **Prism** - to open up payment diversity to the entire world as a simple, lightweight, zero lock-in, developer friendly payments library. **Prism is extracted, built and maintained by the team behind** [**Juspay Hyperswitch**](https://github.com/juspay/hyperswitch) **- the open-source payments platform with 40K+ Github stars and used by leading enterprise merchants around the world.** **Note:** In all honesty, payments are not more complicated than database drivers. It is simply just that the industry has not arrived at a standard (and it never will!!). ### What does Prism do well? * **One request schema** for every payment. The same authorize call works against Stripe, Adyen and many more without additional lines of code. * **Stateless. No database, no stored PII.** Credentials are not stored/ logged by the library. It lives only up to the lifetime of your HTTP client. * **PCI scope reduction.** The card data flowing/ not flowing into the library is your choice. You can choose to leverage any payment processor vault or your own PCI certified vault. Nothing is logged or stored by the library. ### Integrations - Status Prism supports **multiple connectors** with varying levels of payment method and flow coverage. Each connector is continuously tested against real sandbox/ production environments. **Legend:** ✓ Supported | x Not Supported | ⚠ In Progress | ? Needs Validation | Status | Description | | ------ | -------------------------------------------------------- | | ✓ | Fully implemented and tested | | x | Not applicable or unsupported by processor | | ⚠ | Implementation in progress or partial | | ? | Implementation needs validation against live environment | [**View Complete Connector Coverage →**](https://github.com/juspay/hyperswitch-docs/blob/main/integration-space/prism/docs-generated/all_connector.md) ### What Prism does not do (yet)? * **Built-in vault or tokenization service.** This is a design choice. You may bring your own vault, or use the payment processor's vault. * **Retry or routing logic.** It lives in [Juspay Hyperswitch](https://github.com/juspay/hyperswitch). Prism is only the transformation layer. * **Beyond payments.** The diversity exists beyond payments - in subscriptions, fraud, tax, payouts. And it is our aspiration, to evolve Prism into a stateless commerce library. ### Architecture A very high level overview of the Prism architecture and components. To understand more [refer docs](https://docs.hyperswitch.io/integrations/prism/architecture) ``` ┌─────────────────────────────────────────────────────────────────┐ │ Your Application │ └───────────────────────────────┬─────────────────────────────────┘ │ ▼ ┌─────────────────────────────────────────────────────────────────┐ │ Prism Library │ │ (Type-safe, idiomatic interface, Multi-language SDK) │ └────────────────────────────────┬────────────────────────────────┘ │ ▼ ┌───────────────────────┼───────────────────────┬───────────────────────┐ ▼ ▼ ▼ ▼ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ Stripe │ │ Adyen │ │ Braintree│ │ + more │ └──────────┘ └──────────┘ └──────────┘ └──────────┘ ``` *** ### 🚀 Quick Start **Before integrating**, read the SDK guide for your language — it covers connector authentication configs, required fields per connector, sandbox test cards, status codes, and common runtime pitfalls. | Language | SDK Integration Guide | | ----------- | --------------------------------------------------------------------------------------------------------------------------------- | | **Python** | [sdk/python/README.md](https://github.com/juspay/hyperswitch-docs/blob/main/integration-space/prism/sdk/python/README.md) | | **Node.js** | [sdk/javascript/README.md](https://github.com/juspay/hyperswitch-docs/blob/main/integration-space/prism/sdk/javascript/README.md) | | **Java** | [sdk/java/README.md](https://github.com/juspay/hyperswitch-docs/blob/main/integration-space/prism/sdk/java/README.md) | | **Rust** | [sdk/rust](https://github.com/juspay/hyperswitch-docs/blob/main/integration-space/prism/sdk/rust/README.md) | **Demo Application**: Checkout the [E-Commerce Demo](https://github.com/juspay/hyperswitch-docs/blob/main/integration-space/prism/demo/e-commerce/README.md) for a complete working example with Stripe and Adyen integration. #### Install the Prism Library Start by installing the library in the language of your choice. **Node.js** ```bash npm install hyperswitch-prism ``` **Python** ```bash pip install hyperswitch-prism ``` **Java/Kotlin** Add to your `pom.xml`: ```xml io.hyperswitch prism 0.0.4 ``` For detailed installation instructions, see [Installation Guide](https://docs.hyperswitch.io/integrations/prism/prism/installation). *** #### Make a Payment **Node.js** ```typescript import { PaymentClient, types, IntegrationError, ConnectorError } from 'hyperswitch-prism'; let config: types.ConnectorConfig = { connectorConfig: { stripe: { apiKey: { value: "sk_test_" } } } } const main = async () => { try { let client = new PaymentClient(config) let request: types.PaymentServiceAuthorizeRequest = { merchantTransactionId: "authorize_123", amount: { minorAmount: 1000, // $10.00 currency: types.Currency.USD, }, captureMethod: types.CaptureMethod.AUTOMATIC, paymentMethod: { card: { cardNumber: { value: "4111111111111111" }, cardExpMonth: { value: "12" }, cardExpYear: { value: "2050" }, cardCvc: { value: "123" }, cardHolderName: { value: "Test User" }, }, }, authType: types.AuthenticationType.NO_THREE_DS, address: {}, orderDetails: [], } let response: types.PaymentServiceAuthorizeResponse = await client.authorize(request); switch (response.status) { case types.PaymentStatus.CHARGED: console.log("success"); break; default: console.error("failed"); } } catch (e: any) { //handle error } } main() ``` ### 🤖 Building with AI Assistants If you are building with AI assistants, point at the `curl` to fetch the complete SDK reference: > ```bash > curl -fsSL https://raw.githubusercontent.com/juspay/hyperswitch-prism/main/llm/llm.txt > ``` This file contains complete SDK documentation including installation, payment operations, error handling, connector configuration, field probe data, and examples for all payment processors. ### 🔄 Routing between Payment Providers Once the basic plumbing is implemented you can leverage Prism's core benefit - **switch payment providers by changing one line**. ```typescript // Routing rule: EUR -> Adyen, USD -> Stripe const currency = types.Currency.USD; let stripeConfig: types.ConnectorConfig = { connectorConfig: { stripe: { apiKey: { value: process.env.STRIPE_API_KEY! } } } } let adyenConfig: types.ConnectorConfig = { connectorConfig: { adyen: { apiKey: { value: process.env.ADYEN_API_KEY! }, merchantAccount: { value: process.env.ADYEN_MERCHANT_ACCOUNT! } } } } const config = currency === types.Currency.EUR ? adyenConfig : stripeConfig; const client = new PaymentClient(config); // Authorize call from previous step ``` You may just swap the client with any business rules and smart retry logic for payment processor routing. Each flow uses the same unified schema regardless of the underlying processor's API differences. If you wish to learn more about routing logic and smart retries, you can checkout [intelligent routing](https://docs.hyperswitch.io/explore-hyperswitch/workflows/intelligent-routing) and [smart retries](https://docs.hyperswitch.io/explore-hyperswitch/workflows/smart-retries). It can help configure and manage diverse payment acceptance setup, as well as improve conversion rates. *** ### 🛠️ Development #### Prerequisites * Rust 1.70+ * Protocol Buffers (protoc) #### Building from Source ```bash # Clone the repository git clone https://github.com/juspay/hyperswitch-prism.git cd hyperswitch-prism # Build cargo build --release # Run tests cargo test ``` *** ### 💻 Platform Support The `hyperswitch-prism` SDK contains platform-specific native libraries compiled for following platforms and architectures. | Platform | Architecture | | --------------------- | ------------ | | macOS (Apple Silicon) | arm64 | | Linux | x86\_64 | #### Reporting Vulnerabilities Please report security issues to . --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hyperswitch.io/integrations/prism/prism.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.