Documentation

    Documentation

    Documentation

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    2. /
    3. /Payments Overview
    Updated Jun 30, 20262 min listen
    2. /
    3. /Payments Overview
    Updated Jun 30, 20262 min listen
    2. /
    3. /Payments Overview
    Updated Jun 30, 20262 min listen

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Architecture
    Data Model
    Real Time
    Discovery Mutation Sync
    Security
    Backend Services
    k8s-postgres-fcm Mode
    Firebase Integration
    Features
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Wallet & Credit System
    Multi-Vendor Store
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payments Overview
    PaymentConductor
    SubscriptionConductor
    VideoConductor
    News Module - Digital Newspaper Experience
    Member Blogs
    Public Profile Pages
    Username Reservation System
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Branding
    Themes
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Examples
    Quick Start
    White Label
    Real World
    Integrations
    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Architecture
    Data Model
    Real Time
    Discovery Mutation Sync
    Security
    Backend Services
    k8s-postgres-fcm Mode
    Firebase Integration
    Features
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Wallet & Credit System
    Multi-Vendor Store
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payments Overview
    PaymentConductor
    SubscriptionConductor
    VideoConductor
    News Module - Digital Newspaper Experience
    Member Blogs
    Public Profile Pages
    Username Reservation System
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Branding
    Themes
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Examples
    Quick Start
    White Label
    Real World
    Integrations
    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Architecture
    Data Model
    Real Time
    Discovery Mutation Sync
    Security
    Backend Services
    k8s-postgres-fcm Mode
    Firebase Integration
    Features
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Wallet & Credit System
    Multi-Vendor Store
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payments Overview
    PaymentConductor
    SubscriptionConductor
    VideoConductor
    News Module - Digital Newspaper Experience
    Member Blogs
    Public Profile Pages
    Username Reservation System
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Branding
    Themes
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Examples
    Quick Start
    White Label
    Real World
    Integrations
    Ethereum wallets (Wagmi v3)

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Docs
    Features
    Docs
    Features
    Docs
    Features

    Payments Overview

    Ring Platform v1.6 routes all card and credit flows through PaymentConductor (lib/payments/conductor/). WayForPay is the primary PSP for Ukraine; Stripe is supported for international rails.

    Deep dive: PaymentConductor feature · Architecture · SubscriptionConductor

    Use Founder / Developer tabs in the docs sidebar to filter this page.

    What PaymentConductor covers

    PurposeDescriptionPSP
    Store checkoutProduct purchases via cart → checkoutWayForPay / Stripe
    Membership upgradesRole upgrade (e.g. SUBSCRIBER → MEMBER)WayForPay / Stripe
    News promotionNews Kingdom sponsored articlesWayForPay / Stripe
    Internal creditCredit balance wallet spendInternal
    RING tokenOn-chain Solana token paymentsRING

    What founders get

    • One payment layer for everything — store, membership, and news use the same payment_transactions ledger.
    • Config-driven gateway selection — set PAYMENT_DEFAULT_PROCESSOR in env; override per-purpose with PAYMENT_STORE_PROCESSOR, PAYMENT_MEMBERSHIP_PROCESSOR, PAYMENT_NEWS_PROCESSOR.
    • Net revenue per transaction — gross, fee, and net displayed on the admin dashboard per payment.

    Ring-config.json payment section

    Architecture

    Key modules

    ModulePathRole
    Conductorlib/payments/conductor/payment-conductor.tsRoutes payments by purpose + processor
    Configlib/payments/payment.config.tsReads ring-config.json + env overrides
    WayForPaylib/payments/processors/wayforpay.processor.tsHMAC verify, form generation, webhook
    Stripelib/payments/processors/stripe.processor.tsStripe Checkout, webhook
    Internal creditlib/payments/processors/internal-credit.processor.tsCredit balance deduction
    Webhooksapp/api/payments/wayforpay/webhook, app/api/payments/stripe/webhookUnified dispatcher

    Environment variables

    Database

    Related

    PaymentConductor

    Deep-dive: architecture, rails, and webhook flows.

    SubscriptionConductor

    Multi-provider membership billing with recurring revenue.

    WayForPay integration

    HMAC verification, idempotent orderReference, 3DS handling.

    Wallet & Credits

    Credit balance and internal payment methods.

    Payments Overview

    Ring Platform v1.6 routes all card and credit flows through PaymentConductor (lib/payments/conductor/). WayForPay is the primary PSP for Ukraine; Stripe is supported for international rails.

    Deep dive: PaymentConductor feature · Architecture · SubscriptionConductor

    Use Founder / Developer tabs in the docs sidebar to filter this page.

    What PaymentConductor covers

    PurposeDescriptionPSP
    Store checkoutProduct purchases via cart → checkoutWayForPay / Stripe
    Membership upgradesRole upgrade (e.g. SUBSCRIBER → MEMBER)WayForPay / Stripe
    News promotionNews Kingdom sponsored articlesWayForPay / Stripe
    Internal creditCredit balance wallet spendInternal
    RING tokenOn-chain Solana token paymentsRING

    What founders get

    • One payment layer for everything — store, membership, and news use the same payment_transactions ledger.
    • Config-driven gateway selection — set PAYMENT_DEFAULT_PROCESSOR in env; override per-purpose with PAYMENT_STORE_PROCESSOR, PAYMENT_MEMBERSHIP_PROCESSOR, PAYMENT_NEWS_PROCESSOR.
    • Net revenue per transaction — gross, fee, and net displayed on the admin dashboard per payment.

    Ring-config.json payment section

    Architecture

    Key modules

    ModulePathRole
    Conductorlib/payments/conductor/payment-conductor.tsRoutes payments by purpose + processor
    Configlib/payments/payment.config.tsReads ring-config.json + env overrides
    WayForPaylib/payments/processors/wayforpay.processor.tsHMAC verify, form generation, webhook
    Stripelib/payments/processors/stripe.processor.tsStripe Checkout, webhook
    Internal creditlib/payments/processors/internal-credit.processor.tsCredit balance deduction
    Webhooksapp/api/payments/wayforpay/webhook, app/api/payments/stripe/webhookUnified dispatcher

    Environment variables

    Database

    Related

    PaymentConductor

    Deep-dive: architecture, rails, and webhook flows.

    SubscriptionConductor

    Multi-provider membership billing with recurring revenue.

    WayForPay integration

    HMAC verification, idempotent orderReference, 3DS handling.

    Wallet & Credits

    Credit balance and internal payment methods.

    Payments Overview

    Ring Platform v1.6 routes all card and credit flows through PaymentConductor (lib/payments/conductor/). WayForPay is the primary PSP for Ukraine; Stripe is supported for international rails.

    Deep dive: PaymentConductor feature · Architecture · SubscriptionConductor

    Use Founder / Developer tabs in the docs sidebar to filter this page.

    What PaymentConductor covers

    PurposeDescriptionPSP
    Store checkoutProduct purchases via cart → checkoutWayForPay / Stripe
    Membership upgradesRole upgrade (e.g. SUBSCRIBER → MEMBER)WayForPay / Stripe
    News promotionNews Kingdom sponsored articlesWayForPay / Stripe
    Internal creditCredit balance wallet spendInternal
    RING tokenOn-chain Solana token paymentsRING

    What founders get

    • One payment layer for everything — store, membership, and news use the same payment_transactions ledger.
    • Config-driven gateway selection — set PAYMENT_DEFAULT_PROCESSOR in env; override per-purpose with PAYMENT_STORE_PROCESSOR, PAYMENT_MEMBERSHIP_PROCESSOR, PAYMENT_NEWS_PROCESSOR.
    • Net revenue per transaction — gross, fee, and net displayed on the admin dashboard per payment.

    Ring-config.json payment section

    Architecture

    Key modules

    ModulePathRole
    Conductorlib/payments/conductor/payment-conductor.tsRoutes payments by purpose + processor
    Configlib/payments/payment.config.tsReads ring-config.json + env overrides
    WayForPaylib/payments/processors/wayforpay.processor.tsHMAC verify, form generation, webhook
    Stripelib/payments/processors/stripe.processor.tsStripe Checkout, webhook
    Internal creditlib/payments/processors/internal-credit.processor.tsCredit balance deduction
    Webhooksapp/api/payments/wayforpay/webhook, app/api/payments/stripe/webhookUnified dispatcher

    Environment variables

    Database

    Related

    PaymentConductor

    Deep-dive: architecture, rails, and webhook flows.

    SubscriptionConductor

    Multi-provider membership billing with recurring revenue.

    WayForPay integration

    HMAC verification, idempotent orderReference, 3DS handling.

    Wallet & Credits

    Credit balance and internal payment methods.

    Apply data/migrations/004_payment_transactions.sql before enabling the conductor in production. All transactions are persisted in the payment_transactions collection with the DatabaseService result contract { success, data, error }.

    Per-purpose processor override

    json
    
{
  "payment": {
    "cardPaymentProcessor": "wayforpay",
    "supportedMethods": ["wayforpay", "credit_balance", "native_token"],
    "futureMethods": ["stripe", "paypal", "nft_gate"],
    "gateways": {
      "wayforpay": { "enabled": true, "feePercent": 2.5, "currency": "UAH" },
      "stripe": { "enabled": false, "feePercent": 2.9, "feeFixedCents": 30, "currency": "USD" },
      "credit_balance": { "enabled": true, "feePercent": 0, "currency": "USD" },
      "native_token": { "enabled": true, "feePercent": 0, "currency": "RING", "label": "Tokens" }
    }
  }
}
    bash
    
PAYMENT_DEFAULT_PROCESSOR=wayforpay
WAYFORPAY_MERCHANT_ACCOUNT=your_merchant
WAYFORPAY_SECRET_KEY=your_secret
STRIPE_SECRET_KEY=sk_live_...
STRIPE_WEBHOOK_SECRET=whsec_...
PAYMENT_FIAT_CURRENCY=USD
    text
    
Checkout / upgrade / promotion
        ↓
lib/payments/conductor/payment-conductor.ts
        ↓
Processors: wayforpay | stripe | internal_credit
        ↓
payment_transactions (PostgreSQL, migration 004)

    Apply data/migrations/004_payment_transactions.sql before enabling the conductor in production. All transactions are persisted in the payment_transactions collection with the DatabaseService result contract { success, data, error }.

    Per-purpose processor override

    json
    
{
  "payment": {
    "cardPaymentProcessor": "wayforpay",
    "supportedMethods": ["wayforpay", "credit_balance", "native_token"],
    "futureMethods": ["stripe", "paypal", "nft_gate"],
    "gateways": {
      "wayforpay": { "enabled": true, "feePercent": 2.5, "currency": "UAH" },
      "stripe": { "enabled": false, "feePercent": 2.9, "feeFixedCents": 30, "currency": "USD" },
      "credit_balance": { "enabled": true, "feePercent": 0, "currency": "USD" },
      "native_token": { "enabled": true, "feePercent": 0, "currency": "RING", "label": "Tokens" }
    }
  }
}
    bash
    
PAYMENT_DEFAULT_PROCESSOR=wayforpay
WAYFORPAY_MERCHANT_ACCOUNT=your_merchant
WAYFORPAY_SECRET_KEY=your_secret
STRIPE_SECRET_KEY=sk_live_...
STRIPE_WEBHOOK_SECRET=whsec_...
PAYMENT_FIAT_CURRENCY=USD
    text
    
Checkout / upgrade / promotion
        ↓
lib/payments/conductor/payment-conductor.ts
        ↓
Processors: wayforpay | stripe | internal_credit
        ↓
payment_transactions (PostgreSQL, migration 004)

    Apply data/migrations/004_payment_transactions.sql before enabling the conductor in production. All transactions are persisted in the payment_transactions collection with the DatabaseService result contract { success, data, error }.

    Per-purpose processor override

    json
    
{
  "payment": {
    "cardPaymentProcessor": "wayforpay",
    "supportedMethods": ["wayforpay", "credit_balance", "native_token"],
    "futureMethods": ["stripe", "paypal", "nft_gate"],
    "gateways": {
      "wayforpay": { "enabled": true, "feePercent": 2.5, "currency": "UAH" },
      "stripe": { "enabled": false, "feePercent": 2.9, "feeFixedCents": 30, "currency": "USD" },
      "credit_balance": { "enabled": true, "feePercent": 0, "currency": "USD" },
      "native_token": { "enabled": true, "feePercent": 0, "currency": "RING", "label": "Tokens" }
    }
  }
}
    bash
    
PAYMENT_DEFAULT_PROCESSOR=wayforpay
WAYFORPAY_MERCHANT_ACCOUNT=your_merchant
WAYFORPAY_SECRET_KEY=your_secret
STRIPE_SECRET_KEY=sk_live_...
STRIPE_WEBHOOK_SECRET=whsec_...
PAYMENT_FIAT_CURRENCY=USD
    text
    
Checkout / upgrade / promotion
        ↓
lib/payments/conductor/payment-conductor.ts
        ↓
Processors: wayforpay | stripe | internal_credit
        ↓
payment_transactions (PostgreSQL, migration 004)
    bash
    
PAYMENT_STORE_PROCESSOR=stripe        # Override store checkout to Stripe
PAYMENT_MEMBERSHIP_PROCESSOR=stripe   # Override membership to Stripe
PAYMENT_NEWS_PROCESSOR=wayforpay      # News stays on WayForPay
    bash
    
PAYMENT_STORE_PROCESSOR=stripe        # Override store checkout to Stripe
PAYMENT_MEMBERSHIP_PROCESSOR=stripe   # Override membership to Stripe
PAYMENT_NEWS_PROCESSOR=wayforpay      # News stays on WayForPay
    bash
    
PAYMENT_STORE_PROCESSOR=stripe        # Override store checkout to Stripe
PAYMENT_MEMBERSHIP_PROCESSOR=stripe   # Override membership to Stripe
PAYMENT_NEWS_PROCESSOR=wayforpay      # News stays on WayForPay