Завантаження документації...
Підготовка контенту платформи Ring
Підготовка контенту платформи Ring
Підготовка контенту платформи Ring
Підготовка контенту платформи Ring
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Ring v1.6.0 routes card and credit flows through PaymentConductor — one ledger (payment_transactions), one webhook dispatcher, config-driven processors. Operators configure env vars and PSP dashboards; developers read PaymentConductor architecture.
Purposes, rails, env overview
Handlers, ledger, idempotency, API routes
Full PAYMENT_* and PSP secrets
| Purpose | Typical use | Handler |
|---|---|---|
store_order | Multi-vendor store checkout | handlers/store-order.ts |
membership_upgrade | SUBSCRIBER → MEMBER | handlers/membership-upgrade.ts |
news_promotion | News Kingdom paid promotion | handlers/news-promotion.ts |
wallet_topup | Wallet credit top-up | conductor + wallet services |
Processors: WayForPay (default), Stripe, internal credit. PayPal is not in the OSS tree.
Rails: merchant_redirect · internal_credit (PAYMENT_STORE_ALLOW_CREDIT) · native_token (PAYMENT_STORE_ALLOW_TOKEN=true).
Apply data/migrations/004_payment_transactions.sql before production payments.
Full commented block: Environment — PaymentConductor.
Register canonical URLs in your PSP merchant cabinet (replace yourdomain.com):
| Provider | Service URL / endpoint |
|---|---|
| WayForPay | https://yourdomain.com/api/payments/wayforpay/webhook |
| Stripe | https://yourdomain.com/api/payments/stripe/webhook |
Legacy paths /api/payments/wayforpay/callback, /success, /failure — not implemented in v1.6.
Deprecated aliases (still work — migrate when convenient):
/api/store/payments/wayforpay/webhook/api/news/promotion/wayforpay-webhookRecommended for: Ukraine / Europe — hosted cards, Apple Pay, Google Pay.
Create a merchant account at wayforpay.com — complete KYC and note merchant account, secret key, approved domain.
Set Ring env vars:
In the WayForPay cabinet, set service URL (callback):
Verify in staging: migration 004 applied → test checkout → confirm payment_transactions row + fulfillment (order paid / role upgraded / promotion active).
Migration 004_payment_transactions.sql applied on production Postgres.
PAYMENT_* and PSP credentials in secrets manager (never commit .env.local).
Canonical webhook URLs registered; WAYFORPAY_DOMAIN matches approved merchant domain.
Staging smoke: store checkout, membership upgrade, news promotion (if used).
Post go-live: monitor payment_transactions for stuck pending / redirected rows.
Membership flow and overview
Checkout and order endpoints
Apply order including migration 004
Need hands-on help? Ring customization opportunities
Ring v1.6.0 routes card and credit flows through PaymentConductor — one ledger (payment_transactions), one webhook dispatcher, config-driven processors. Operators configure env vars and PSP dashboards; developers read PaymentConductor architecture.
Purposes, rails, env overview
Handlers, ledger, idempotency, API routes
Full PAYMENT_* and PSP secrets
| Purpose | Typical use | Handler |
|---|---|---|
store_order | Multi-vendor store checkout | handlers/store-order.ts |
membership_upgrade | SUBSCRIBER → MEMBER | handlers/membership-upgrade.ts |
news_promotion | News Kingdom paid promotion | handlers/news-promotion.ts |
wallet_topup | Wallet credit top-up | conductor + wallet services |
Processors: WayForPay (default), Stripe, internal credit. PayPal is not in the OSS tree.
Rails: merchant_redirect · internal_credit (PAYMENT_STORE_ALLOW_CREDIT) · native_token (PAYMENT_STORE_ALLOW_TOKEN=true).
Apply data/migrations/004_payment_transactions.sql before production payments.
Full commented block: Environment — PaymentConductor.
Register canonical URLs in your PSP merchant cabinet (replace yourdomain.com):
| Provider | Service URL / endpoint |
|---|---|
| WayForPay | https://yourdomain.com/api/payments/wayforpay/webhook |
| Stripe | https://yourdomain.com/api/payments/stripe/webhook |
Legacy paths /api/payments/wayforpay/callback, /success, /failure — not implemented in v1.6.
Deprecated aliases (still work — migrate when convenient):
/api/store/payments/wayforpay/webhook/api/news/promotion/wayforpay-webhookRecommended for: Ukraine / Europe — hosted cards, Apple Pay, Google Pay.
Create a merchant account at wayforpay.com — complete KYC and note merchant account, secret key, approved domain.
Set Ring env vars:
In the WayForPay cabinet, set service URL (callback):
Verify in staging: migration 004 applied → test checkout → confirm payment_transactions row + fulfillment (order paid / role upgraded / promotion active).
Migration 004_payment_transactions.sql applied on production Postgres.
PAYMENT_* and PSP credentials in secrets manager (never commit .env.local).
Canonical webhook URLs registered; WAYFORPAY_DOMAIN matches approved merchant domain.
Staging smoke: store checkout, membership upgrade, news promotion (if used).
Post go-live: monitor payment_transactions for stuck pending / redirected rows.
Membership flow and overview
Checkout and order endpoints
Apply order including migration 004
Need hands-on help? Ring customization opportunities
Ring v1.6.0 routes card and credit flows through PaymentConductor — one ledger (payment_transactions), one webhook dispatcher, config-driven processors. Operators configure env vars and PSP dashboards; developers read PaymentConductor architecture.
Purposes, rails, env overview
Handlers, ledger, idempotency, API routes
Full PAYMENT_* and PSP secrets
| Purpose | Typical use | Handler |
|---|---|---|
store_order | Multi-vendor store checkout | handlers/store-order.ts |
membership_upgrade | SUBSCRIBER → MEMBER | handlers/membership-upgrade.ts |
news_promotion | News Kingdom paid promotion | handlers/news-promotion.ts |
wallet_topup | Wallet credit top-up | conductor + wallet services |
Processors: WayForPay (default), Stripe, internal credit. PayPal is not in the OSS tree.
Rails: merchant_redirect · internal_credit (PAYMENT_STORE_ALLOW_CREDIT) · native_token (PAYMENT_STORE_ALLOW_TOKEN=true).
Apply data/migrations/004_payment_transactions.sql before production payments.
Full commented block: Environment — PaymentConductor.
Register canonical URLs in your PSP merchant cabinet (replace yourdomain.com):
| Provider | Service URL / endpoint |
|---|---|
| WayForPay | https://yourdomain.com/api/payments/wayforpay/webhook |
| Stripe | https://yourdomain.com/api/payments/stripe/webhook |
Legacy paths /api/payments/wayforpay/callback, /success, /failure — not implemented in v1.6.
Deprecated aliases (still work — migrate when convenient):
/api/store/payments/wayforpay/webhook/api/news/promotion/wayforpay-webhookRecommended for: Ukraine / Europe — hosted cards, Apple Pay, Google Pay.
Create a merchant account at wayforpay.com — complete KYC and note merchant account, secret key, approved domain.
Set Ring env vars:
In the WayForPay cabinet, set service URL (callback):
Verify in staging: migration 004 applied → test checkout → confirm payment_transactions row + fulfillment (order paid / role upgraded / promotion active).
Migration 004_payment_transactions.sql applied on production Postgres.
PAYMENT_* and PSP credentials in secrets manager (never commit .env.local).
Canonical webhook URLs registered; WAYFORPAY_DOMAIN matches approved merchant domain.
Staging smoke: store checkout, membership upgrade, news promotion (if used).
Post go-live: monitor payment_transactions for stuck pending / redirected rows.
Membership flow and overview
Checkout and order endpoints
Apply order including migration 004
Need hands-on help? Ring customization opportunities