Payment infrastructure without vendor lock-in

What's under the hood

interface SubscriptionProvider {
  id: 'demo' | 'wayforpay' | 'stripe';
  isConfigured(): boolean;
  createCheckout(args): Promise<{ url }>;
  createPortal(args): Promise<
    | { kind: 'hosted'; url }
    | { kind: 'unsupported'; reason }
  >;
}

type RefundProviderId =
  | 'liqpay'    | 'monobank'
  | 'stripe'    | 'manual';

executePaymentRefund(provider, {
  paymentIntentId,
  amountUah,
  reason,
  idempotencyKey,
}) => Promise<RefundResult>

Codebase open on GitHub — apps/orchestrator/src/billing/.

FAQ — Payments

• Why don't you use Stripe as primary, like all Western SaaS?

  Stripe for UA ФОП-3 requires either an EU LLC (Estonia OÜ / Poland sp. z o.o.) or Stripe Atlas (US LLC). Both paths cost money and time we're currently investing in the product. WayForPay accepts Ukrainian ФОП-3, integrates with ПРРО for automatic receipts, and has native UAH recurring without FX exchanges. Stripe remains in the codebase — we'll activate it in Y2 EU expansion.

• Is it safe to pay via WayForPay?

  WayForPay has PCI DSS Level 1 certification (the highest level for payment providers). Card data never touches our servers — you enter it on WayForPay's hosted checkout; we receive only a tokenized identifier for recurring charges. 3-D Secure 2.0 is mandatory. Same for LiqPay, Monobank.

• How are refunds (returns) automated?

  Refunds route to whichever payment provider an order was paid with. If the order was charged via LiqPay, refund via LiqPay's refund API. If via WayForPay, via WayForPay's refund API, etc. The AI agent recognizes a return event via KeyCRM and automatically triggers the refund through the recorded payment provider. Refund logs track all transactions with idempotency — no duplicate charges.

• What about ПРРО (software cash register) and fiscal receipts?

  WayForPay has native ПРРО integration (Cabinet of Taxpayer) — each subscription automatically issues a fiscal receipt to the customer via email. Activated during KYC. For ФОП-3 on the simplified system (5%) selling services to Ukraine residents, this is mandatory. We pass order metadata (service category, VAT rate "VAT-exempt for ФОП-3"), the rest is WayForPay automation.

• Can I pay with crypto / Apple Pay / Google Pay?

  Apple Pay + Google Pay — yes, via WayForPay native wallet support. Cryptocurrencies — no in V1; we'll consider in Y2 when regulatory clarity emerges on NBU directive regarding virtual assets.

• What if WayForPay is temporarily unavailable?

  The architecture is provider-agnostic (see ADR-039) — we can emergency-switch to Stripe with a single env var (BILLING_PROVIDER=stripe) if WayForPay has an extended outage. Existing subscriptions stay with WayForPay; new signups route through Stripe until recovery. This is documented in the production-deploy runbook.

• How much does WayForPay take? Will it affect my price?

  WayForPay commission ~2.7–3% of amount + ПРРО fee (~₴1–2 per receipt). We cover these costs from marketplace margin; your Unitelia price doesn't change. For comparison: Stripe for UA ФОП — 2.9% + $0.30 fixed fee per transaction, which for a $49/mo plan is ~$1.72 vs WayForPay ~$1.32–1.47. Cheaper for small amounts.

• Do you issue invoices, acts, VAT invoices?

  Subscriptions on ФОП-3 — we are ФОП-3 on the simplified system (5%), VAT-exempt. WayForPay automatically generates a fiscal receipt via ПРРО — it is legally a closing document for most cases. If your accounting requires a service agreement in docx format — write to m.nazar77@gmail.com, we'll issue it manually. For legal entities with VAT (rare for UA SMB) — a separate path, not optimized at launch.