WooCommerce plugin (beta)
Version: 1.0.0-beta.1
Download the WooCommerce plugin ZIP.
The plugin is a public beta, not a statement that every WooCommerce extension or checkout combination is qualified. Test your store's checkout, refunds, webhooks and order lifecycle in sandbox before enabling it for customers. Production checkout requires Peak-issued production credentials and approved processing readiness.
Requirements
- WordPress 6.8+.
- WooCommerce 10.0+.
- PHP 8.2+, 64-bit, with the sodium extension.
- An HTTPS store and an approved Gateway location.
Install and connect
- Download the ZIP above. In WordPress, open Plugins → Add New Plugin → Upload Plugin, select the ZIP, install it and activate it.
- Open WooCommerce → Settings → Payments → Peak Gateway with an administrator account authorized to manage both WordPress and WooCommerce.
- Select Staging, enter the sandbox location ID and a location-scoped API key. Create the key with all six scopes:
hosted-payments:read,hosted-payments:write,transactions:read,transactions:write,webhooks:readandwebhooks:write. - Save to verify location ownership, processing readiness and webhook registration. Use a dedicated location if another integration already owns the location's webhook endpoint; do not replace another integration's endpoint.
- Choose Hosted payment page or Embedded secure checkout. Enable the payment method only after readiness checks succeed for the order currency.
- Exercise the sandbox cards, webhook delivery, cancellation, lost-response reconciliation and refunds on your own store before selecting Production with production credentials.
Beta and operational boundaries
Registration alone does not authorize processing. Check the connection/readiness message if checkout is unavailable. Keep credentials on the server; the plugin protects the stored key and does not display it again.
The compatibility qualification matrix remains open. Validate your theme, checkout mode and extensions rather than assume universal support. Disconnect disables new checkout but retains protected credentials and webhooks to reconcile existing orders. Do not revoke that key while outstanding financial operations still need it.