PayVizio is an India-first payment orchestration layer. You integrate once with our APIs and hosted checkout; we route each transaction to the acquirer or gateway endpoint that matches your rules (health, cost, method, geography, and more). You keep a single integration surface while operating multiple downstream connections.

Growing merchants and platforms that want to reduce dependence on a single PSP, improve authorization rates, tune costs, and avoid rebuilding integrations every time they add or change an acquirer. Typical users include marketplaces, SaaS billers, insurers, and ecommerce brands processing meaningful INR volume.

Both patterns are supported. Many teams start with hosted checkout for fastest time-to-PCI-safe launch, then add server-side order creation and webhooks for deeper control. The same order and routing model applies whether the customer completes payment on our hosted page or you drive the flow via API + redirects.

Teams often ship a first sandbox payment in under a day: create API keys, create an order, redirect to checkout or complete a server-driven flow, and verify webhooks. Production readiness depends on your risk review, acquirer onboarding, and settlement setup — we align those steps during onboarding.

Yes. State-changing operations are designed to be safely retried using idempotency keys so network blips or client timeouts do not double-charge or duplicate orders. Follow the idempotency guidelines in the API reference for key scope and TTL.

We publish SDKs and examples for common server runtimes (including Node and others). Where we do not ship a first-party SDK, the REST API and OpenAPI specification are stable integration surfaces. Browser-side code should never hold live secrets — always create orders from your server.

Yes. PayVizio sits between your application and your connected acquirers. Enabling or prioritizing an acquirer is primarily a configuration change in the merchant dashboard (subject to your contracts and onboarding with each acquirer). Your checkout integration and API surface stay the same.

You define rules and weights: by payment method, card BIN or network, amount bands, geography, time windows, or acquirer health signals. The orchestrator evaluates eligible routes per transaction, applies fallbacks when an acquirer is degraded or unavailable, and retries according to your policy — without exposing that complexity to your app.

A single PSP gives you one integration but also a single point of failure for pricing negotiation, uptime, and authorization behavior. Orchestration keeps one integration on your side while letting you diversify acquirers, compare performance, and shift traffic when conditions change.

Settlement cadence follows each acquirer's cycle and your agreement with them; PayVizio surfaces gross amounts, fees, refunds, chargebacks, and tax components in reporting. Standard settlement is typically on a daily reconciliation cycle with downloadable breakdowns. Instant or on-demand settlement may be available where supported — fees and eligibility vary.

We normalize settlement files and transaction feeds from connected acquirers, match them to your ledger entries, and flag mismatches for review. The goal is a single place to see what cleared, what is pending, and what needs adjustment — instead of stitching spreadsheets per PSP.

Refunds are asynchronous, idempotent, and support full or partial amounts. You call one refunds API; PayVizio routes the refund to the original acquirer and emits signed webhooks when the refund reaches a terminal state. Partial refunds update the remaining refundable balance on the payment.

Chargeback events differ by network and acquirer; we expose lifecycle updates via webhooks and dashboard views where available so your ops team can track deadlines and upload evidence according to acquirer rules. Exact capabilities depend on the acquirers you enable.

For standard redirect and hosted flows, card data does not touch your servers or PayVizio's servers in a way that expands PCI scope like raw PAN entry on your domain would. UPI, netbanking, and wallets follow redirect or app intent patterns. Your acquirer remains responsible for card authorization UI where applicable; always confirm scope with your QSA for your exact integration pattern.

Secrets are encrypted at rest using strong algorithms (e.g. AES-GCM) with key management that can integrate with your KMS posture. Live keys can be restricted by IP allow-lists; sensitive fields are redacted in logs. Rotate keys from the dashboard if they may have leaked.

PayVizio is built with India-first deployments and data residency expectations for regulated workloads. Specific regions and subprocessors are documented in our agreements and privacy materials; ask sales if you need a formal mapping for vendor review.

Yes. Test API keys use the same orchestration paths as live with isolated data — no real money moves. Use test keys in staging, drive test transactions through sandbox acquirer behavior, and validate webhooks before rotating to live keys.

Typically: completed KYC/business verification, executed agreements, live acquirer MID or gateway credentials where applicable, production API keys with IP restrictions, webhook endpoints over HTTPS, and a short parallel monitoring window. We provide a checklist during onboarding.

We deliver HTTPS callbacks for payment, refund, dispute, and related lifecycle events. Payloads are signed (e.g. HMAC) so you can verify authenticity. Implement idempotent handlers and return 2xx quickly; defer heavy work to your queue to avoid timeouts and unnecessary retries.

Failed deliveries are retried with backoff according to our retry policy. Monitor failure rates in the dashboard, fix endpoints promptly, and use replay tools where offered to recover missed events after an outage.

Pricing is generally a platform fee per successful transaction on top of acquirer MDR, with tiers that improve at volume. There is typically no large upfront setup fee for standard integrations. Exact quotes depend on your payment mix, volumes, and support tier — see our payment gateway page for public anchors or request a demo for a tailored proposal.

Integration questions route through docs and engineering support during onboarding; production merchants receive dashboard-assisted ticketing with severity-based response targets per plan. Critical payment outages are escalated according to your contract.

Contact us via the contact form or email listed on the Contact page. For integration specifics, linking to request IDs and timestamps helps us trace issues quickly.