docs(prism): reformat markdown files with standardized frontmatter

prism/README.md

@@ -1,3 +1,7 @@
+---
+description: High-performance payment abstraction library for 100+ connectors with multi-language SDK support
+---
+
 <div align="center">
 
 

prism/api-reference/README.md

@@ -1,3 +1,7 @@
+---
+description: Complete reference for Prism gRPC API services including payment, refund, recurring, and dispute operations
+---
+
 # API Reference
 
 Complete reference for all Prism API services, request/response types, and error handling.

prism/api-reference/domain-schema/README.md

@@ -1,13 +1,8 @@
-# Domain Schema
-
-<!--
 ---
-title: Domain Schema
-description: Complete reference for all domain types, enums, and data structures used across Connector Service services
-last_updated: 2026-03-11
-generated_from: crates/types-traits/grpc-api-types/proto/
-auto_generated: false
-reviewed_by: engineering
+description: Complete reference for all domain types, enums, and data structures used across Connector Service
+---
+
+# Domain Schema
 reviewed_at: 2026-03-05
 approved: true
 ---

prism/architecture/README.md

@@ -1,3 +1,7 @@
+---
+description: Understand the Prism architecture with interface, binding, and core layers for unified payment processing
+---
+
 ## Architecture Overview
 
 If you've integrated multiple payment providers, you know the pain:

prism/blogs/why-we-built-a-unified-payment-integration-library.md

@@ -1,3 +1,7 @@
+---
+description: Learn why Juspay built Prism, a unified payment integration library to solve multi-processor complexity
+---
+
 # Why we built a Unified Payment Integration Library?
 
 If you have ever integrated a payment processor, you know the drill. You read through a PDF that was last updated in 2019, figure out what combination of API keys goes in which header, discover that "decline code 51" means something subtly different on this processor than the last one you dealt with, and then do it all over again when your business decides to add a second processor.

prism/connectors/adyen.md

@@ -1,3 +1,7 @@
+---
+description: Configure Adyen connector for payments, wallets, bank transfers, and recurring operations
+---
+
 # Adyen
 
 <!--

prism/connectors/paypal.md

@@ -1,3 +1,7 @@
+---
+description: Integrate PayPal payments with authorize, capture, refund, and wallet payment flows
+---
+
 # Paypal
 
 <!--

prism/connectors/stripe.md

@@ -1,3 +1,7 @@
+---
+description: Integrate Stripe payments with card, wallet, bank transfers, recurring payments, and tokenization support
+---
+
 # Stripe
 
 <!--

prism/connectors/zift.md

@@ -1,3 +1,7 @@
+---
+description: Configure Zift connector and integrate payment flows including authorize, capture, refund, and void operations
+---
+
 # Zift
 
 <!--

prism/getting-started/create-order.md

@@ -1,3 +1,7 @@
+---
+description: Create your first payment order and obtain session tokens for Stripe and Adyen integrations
+---
+
 # Quick Start
 
 Now that the library is installed and configured, let's create your first payment order (different payment processor's use different terminology - order, intent, transaction and so on). Conceptually, it represents the user's intent to start a payment session. 

prism/getting-started/extend-to-more-flows.md

@@ -1,3 +1,7 @@
+---
+description: Implement advanced payment flows including recurring payments, incremental authorization, partial capture, and webhooks
+---
+
 # Extending to More Flows
 
 You have implemented the basic plumbing for routing payment processor agnostic APIs. All methods work the same way with the single interface regardless of which payment processor you use. That's the power you get with the library.

prism/getting-started/first-payment.md

@@ -1,3 +1,7 @@
+---
+description: Process your first payment using the Prism library with authorization, capture, and refund flows
+---
+
 # First Payment
 
 In the next few steps you will authorize the payment, handle errors, capture funds, and process refunds. And then you will be ready to send payment to any payment processor, without writing specialized code for each.

prism/getting-started/installation.md

@@ -1,3 +1,7 @@
+---
+description: Install and configure the Hyperswitch Prism library for Node.js, Python, Java, and PHP
+---
+
 # Installation and Configuration