What Victava doesn't do yet

Victava defends disputes on Stripe today, and we ship to the Stripe App Marketplace first. We’d rather be excellent on one processor than mediocre across five. Everything below is either something we’ll build fast when a customer needs it, or deliberately out of scope — we’d rather tell you up front than surprise you after you connect.

Out of scope today

• Other processors (Adyen, Braintree, etc.). Victava hooks into Stripe’s chargeback API today, so we don’t defend disputes that settle outside Stripe yet. But if one of these is your processor, tell us — we ship processor support fast for our first merchants (support@victava.com).
• PayPal disputes. PayPal’s dispute API is structurally different from a card-network chargeback, so it’s not live yet. If PayPal is where your disputes land, tell us and we’ll prioritize building it.
• Shopify Payments stores. We pull data from Shopify (orders, fulfillment, tracking) to win your Stripe disputes today. Run on Shopify Payments instead of Stripe? It's not live yet — tell us and we'll build it; we ship processor support fast for our first merchants (support@victava.com). Shopify Payments runs card processing through Shopify’s Stripe-on-Connect setup — a different OAuth path than a direct Stripe account.
• Non-US merchants. Network-rule pre-checks are tuned for the Visa/Mastercard US chargeback flow. International merchants on Stripe will technically connect, but the classifier and rebuttal templates are US-rule-tuned. Need international tuning? Tell us and we’ll build it.
• ACH disputes. ACH return codes (incorrect_account_details, insufficient_funds, etc.) aren’t card-network chargebacks and have a different remediation flow. Out of scope.
• Klarna / Affirm / BNPL. Each BNPL has its own dispute API. Not supported.
• Card-present (in-store) disputes. Victava assumes card-not-present (online) commerce. CP-only EMV shifts are out of scope.
• Self-service disconnect. Email support@victava.com to revoke the integration; we do it the same business day. A self-service settings button is coming as we grow.
• Per-merchant rate negotiation. 20% on a win (or 10% for the founding cohort), $0 on a loss. No bespoke rates.
• Enterprise SLA. Best-effort support during US business hours. No 24/7 phone support today.

Reason codes that aren’t auto-handled

Victava’s classifier maps inputs to seven Stripe-normalized categories (see /help/reason-codes). Anything that doesn’t fit — generic customer_initiated without a network reason, retrieval requests routed without a Stripe webhook, EFW that falls outside our policy auto-refund logic — falls through to manual handling. The dashboard surfaces these asneeds_info, not represent.

What we will not build, ever

• Auto-submission without merchant approval. Mandatory human approval is an architectural rule, not a default we flipped on or a setting you can leave off. Nothing reaches the bank without your click.
• LLM-fabricated factual claims. ”Never Generate, Only Retrieve” is a permanent design rule.
• Hidden fee structures. Your rate is disclosed up front and honored per your contract — founding merchants keep 10% for their guaranteed first 12 months. We never silently flip a flag to change what you pay.

Run into something you wish Victava handled? Email support@victava.com. We build by what merchants actually ask for, not by a tidy-looking wishlist.