Docs / Plugin guide / WooCommerce

This plugin guide should tell you exactly what to verify before WooCommerce routes a live order into Payvra settlement.

The WooCommerce integration is an installable payment gateway that hands shoppers to the Payvra hosted checkout and relies on signed callbacks to update order state. Use this page to prove the install path, payment-state reconciliation, and the exact switches you flip when the store moves from sandbox to live.

Create free sandbox Review API reference

Treat the gateway like any other payment rail: install it cleanly, confirm one full sandbox order lifecycle, and only then swap the API key and webhook secret to live values.

What this guide proves

Checkout redirect

Confirm the WooCommerce gateway appears at checkout, creates a Payvra payment, and redirects the shopper into the hosted checkout without breaking the cart or order reference.

Signed callback

Verify the WordPress callback endpoint receives the signed Payvra webhook and updates the WooCommerce order only after the signature is accepted.

Refund route

Confirm the refund action from the WooCommerce order page maps back to the matching Payvra payment so operators are not forced into manual off-platform support work.

Operator facts

Runtime model

Installable WordPress plugin inside the WooCommerce store.

Checkout route

WooCommerce checkout -> Payvra hosted checkout -> signed callback to the store.

Store requirement

WordPress 6+, WooCommerce 8+, PHP 7.4+, and HTTPS on the storefront.

Live promotion

Swap the Payvra API key and webhook secret after the sandbox order path is verified.

Overview

Treat this page as an operator checklist. Each section below maps one part of the plugin path you should verify before you promote checkout traffic to live funds.

Checkout redirect

Confirm the WooCommerce gateway appears at checkout, creates a Payvra payment, and redirects the shopper into the hosted checkout without breaking the cart or order reference.

Signed callback

Verify the WordPress callback endpoint receives the signed Payvra webhook and updates the WooCommerce order only after the signature is accepted.

Refund route

Confirm the refund action from the WooCommerce order page maps back to the matching Payvra payment so operators are not forced into manual off-platform support work.

Store listing

The exact distribution surface operators reach for when they install the plugin. The card below mirrors the listing fields shoppers and merchants verify before adopting a payment path.

WordPress.org plugin directoryVerified publisher

Payvra. Distributed as a packaged WordPress plugin zip.

Payvra Crypto Payment Gateway for WooCommerce

Operators install the gateway directly from the WordPress admin or by uploading the packaged zip, the same artifact used in production.
The plugin registers a WooCommerce payment method, so it slots into the existing checkout configuration without a separate theme integration.
Updates ride the WordPress plugin update channel, which keeps store owners on a known-good gateway version without manual rebuilds.

Download the WooCommerce plugin

Listing facts

Distribution: Plugin directory + zip
Tested up to: WooCommerce 8.x
Requires PHP: 7.4 or later
Requires WP: 6.0 or later
Cost: Free

Requirements

Make sure the store, hosting, and account prerequisites are in place before you install the plugin path.

•

WordPress 6.0 or later.

•

WooCommerce 8.0 or later.

•

PHP 7.4 or later.

•

A Payvra account with sandbox credentials.

•

HTTPS enabled on the storefront.

Setup

Get the plugin or bridge installed first. Then verify that the store can hand checkout traffic to Payvra before you spend time on live credentials.

Download the plugin package

Start from the packaged gateway zip so the plugin path you test is the same artifact operators install later in production.

Plugin package

1/downloads/payvra-gateway.zip

Upload and activate it in WordPress

In WordPress admin, go to Plugins, upload the zip, install it, and activate the gateway. If you prefer manual deployment, upload the payvra-gateway folder into wp-content/plugins/ first.

Confirm the payment method appears in WooCommerce

Open the WooCommerce payments settings and verify the Payvra gateway can be enabled. Do this before you wire live credentials so the storefront configuration issue is separated from payment-mode issues.

Keep the first install in sandbox mode

Use the plugin to prove the redirect and callback flow before real funds are involved. The production cutover should only change the Payvra secret material, not the installation flow.

Configuration

Keep the runtime settings explicit so operators can tell which key, secret, and settlement target a store is using at a glance.

Enable gateway

Turn on the WooCommerce payment method only after the plugin is installed and the store is ready to test a checkout path.

Sandbox mode

Keep this enabled while you rehearse one complete order lifecycle. The goal is to validate store behavior, not just that the settings save correctly.

API key

Start with sk_test_.... Replace it with sk_live_... only after the signed webhook path is stable and the WooCommerce order transitions are correct.

Webhook secret

Store the Payvra signing secret separately so operators can rotate it without changing the WooCommerce plugin install or other store settings.

Settlement currency

Choose the post-payment settlement target the merchant should receive after Payvra processes the payment and any conversion behavior.

Webhook setup

The plugin path is only production-safe once signed delivery is verified and the store can reconcile the final payment state automatically.

Copy the store callback URL

This is the endpoint Payvra signs and posts to when an order payment changes state.

Store webhook URL

1https://yourstore.com/wp-json/payvra/v1/webhook

Add the endpoint in the Payvra dashboard and subscribe to the order-facing events first: payment.confirmed, payment.completed, payment.failed, payment.expired, refund.completed, and refund.failed.

Verify the callback before order mutation logic runs

The plugin should reject stale or unsigned requests before it changes the WooCommerce order. If the signature is valid, the callback can safely move the order into the correct payment state.

Platform webhook quirks

Most WooCommerce delivery failures come from how WordPress hosting handles the REST callback URL, not from the Payvra signature itself.

Pretty permalinks

The callback path /wp-json/payvra/v1/webhook only resolves when WordPress is running pretty permalinks. Plain query-string permalinks return a 404 and the Payvra delivery log shows no payload reached the store.

Page-cache plugins

WP Super Cache, W3 Total Cache, and most managed-host page caches need an explicit bypass rule for the REST namespace. Otherwise a cached 404 or stale response is served back to Payvra and signed events look dropped.

Object cache invalidation

If Redis or Memcached object caching is enabled, WooCommerce order updates inside the callback can race the cache. Flush the order cache key after marking processing to keep the admin order screen consistent with the gateway log.

Multisite scope

On a WordPress multisite network the webhook URL is per-site. Configure one Payvra endpoint per blog so events do not get routed to the wrong store's order tables.

Testing in sandbox

Run one full rehearsal with test credentials and confirm the checkout handoff, payment confirmation, and order update path end to end.

Gateway visibility

Place a sandbox order and confirm the Payvra payment method appears and redirects the shopper into hosted checkout.

Lifecycle rehearsal

Watch the sandbox payment progress from pending to confirmed while you compare the storefront order state against the Payvra webhook delivery log.

Order resolution

The WooCommerce order should move to Processing or the configured paid state only after the signed event is received and accepted.

Refunds

Confirm the store-side refund action maps back to Payvra before you announce the plugin internally.

Trigger the refund from the WooCommerce order screen so the store and Payvra stay on the same source-of-truth path.

Use the Payvra refund action, not a manual WooCommerce-only refund, so the original payment reference and payout destination remain attached to the order.

Confirm the refund shows up in both WooCommerce order notes and the Payvra dashboard before the issue is handed back to support.

Promote to live

Only switch the credentials and webhook secret after the sandbox route is boring and repeatable.

Generate a live Payvra key and replace the sandbox sk_test_... value with sk_live_....

Create a live webhook for the same callback URL and paste the live whsec_... value into the WooCommerce plugin settings.

Disable sandbox mode only after the redirect, callback, and order-state path are all stable in rehearsal.

Run one low-risk production order and compare the WooCommerce order notes with the Payvra event log before wider rollout.

Troubleshooting

Use these checks when the plugin path stalls. Each item points to the fastest place to confirm whether the problem is in storefront setup, Payvra delivery, or the operator config.

Gateway does not appear at checkout

Check that the plugin is active, WooCommerce is enabled, the store is running over HTTPS, and the Payvra gateway itself is toggled on inside WooCommerce payment settings.

Orders stay pending after payment

This usually points to a webhook issue. Compare the Payvra webhook delivery log with the WordPress callback log to see whether the callback URL, signing secret, or order mutation failed.

Refund action cannot find the Payvra payment

Orders created before the plugin was installed, or payments that were not processed through Payvra, will not have the stored Payvra payment reference required for automated refunds.

Plugin installs but still fails in production

Re-check the credential mode. A surprisingly common cause is a live store still using sk_test_... or a stale sandbox webhook secret after the operator believes the store has been promoted.

Ready to validate the WooCommerce gateway?

Prove one sandbox order from checkout redirect to signed callback, then promote the same gateway to live mode by switching only the Payvra credentials and webhook secret.

Get sandbox keys Back to docs

This plugin guide should tell you exactly what to verify before WooCommerce routes a live order into Payvra settlement.

Treat the gateway like any other payment rail: install it cleanly, confirm one full sandbox order lifecycle, and only then swap the API key and webhook secret to live values.