Woo Payram

What you get

• Payment gateway — “Payram (crypto)” under WooCommerce → Settings → Payments; customizable title, description, and thank-you instructions.
• Redirect checkout — Customer completes payment on your Payram flow and returns to your site.
• REST webhook — Stable endpoint for Payram to POST payment updates (best on public HTTPS).
• Thank-you page status checks — When webhooks aren’t reachable (e.g. local .test / LAN), orders can still progress via API polling on the order-received screen.
• WooCommerce Blocks — Block checkout integration where WooCommerce Blocks is available; compatibility declared for cart/checkout blocks and custom order tables (HPOS).
• Return URLs — Documented success and cancel URLs, including readable paths like /webhook/payram/success/; legacy query-style returns still supported.
• Hardened return handling — Validates session and order context rather than trusting a reference alone.
• USD mapping — Sends sensible USD amounts to Payram when the store currency isn’t USD.
• API client & order sync — Server-side calls to Payram for payment status; order meta updated consistently with webhook and poll paths.
• WooCommerce → Woo Payram — Dashboard page for gateway status, setup hints, and webhook reachability notes.
• Order screen tools — Payram payment snapshot on orders plus actions to refresh state from the API where appropriate.
• Connection test & logging — “Test API connection” from settings; optional debug logging under WooCommerce → Status → Logs (payram source).
• License & activation (paid builds) — Activate with your license key (and complete the in-dashboard signup where prompted). Payram checkout stays off until the license is valid if your build enforces licensing. You’ll find the license area in gateway settings and under WooCommerce → Woo Payram (account / activation as applicable).

Benefits

• Custody stays on Payram — WordPress doesn’t hold wallet keys; it coordinates orders and reacts to Payram’s signals.
• Standard Woo patterns — Gateway, webhooks, and return URLs—no bespoke theme hacks required.
• Operations-friendly — Dashboard, logs, and API test reduce time-to-diagnose when something misconfigures.
• GPL + commercial sales — Plugin code is GPLv2+; purchases typically include license keys, updates, and support on terms shown at checkout.

Prerequisites

• WordPress 6.5+ (see readme for “tested up to”).
• WooCommerce 8.0+ active.
• PHP 7.4+ (newer PHP strongly recommended).
• A running Payram deployment with API access (base URL, API key, optional webhook secret).
• HTTPS in production; webhooks need a URL Payram can reach from the internet.
• For purchased builds: use the license and setup instructions supplied with your order so checkout isn’t blocked by licensing.

Quick start

1. Install and activate Woo Payram with WooCommerce already active.
2. Paid builds: Enter your license key and finish activation where the plugin prompts you (WooCommerce → Settings → Payments → Payram and/or WooCommerce → Woo Payram).
3. Open WooCommerce → Settings → Payments → Payram.
4. Set Payram server URL to your API root (typically without trailing /api/v1—the plugin merges path segments). Dedicated ports and host vs IP are documented inline in settings.
5. Paste the API key; set webhook secret if Payram expects signed callbacks.
6. Copy the plugin’s webhook URL and the Success / Cancel URLs into Payram exactly as shown.
7. Save, run Test API connection, then place a test order. Visit WooCommerce → Woo Payram for a concise status/overview.

Payram server reference: docs.payram.com.

Privacy & data

The plugin exchanges order identifiers, amounts, and payment references with your configured Payram server. Review Payram’s privacy posture and your own store policy for end customers.

FAQs

Do I need a public website for webhooks?

For automatic status updates, Payram must POST to your site. On localhost, use a tunnel (e.g. ngrok) or rely on thank-you page polling until you deploy.

Does Blocks checkout work?

Yes—the plugin registers block integration when WooCommerce Blocks is present. Classic checkout is also supported.

Why is checkout disabled on my site?

On builds that enforce licensing, an inactive or expired license turns off Payram at checkout until you renew or enter a valid key. Use any seller-approved development-only bypass only on local sites—not in production.

Is this “Payram hosting my money”?

Settlement and asset flows are defined by your Payram deployment and networks. This plugin reflects Payram’s payment state inside WooCommerce.

What license is the plugin under?

GPL v2 or later, consistent with WordPress. Paid products still use license keys (and similar) for activation, updates, and support—that doesn’t change the GPL terms of the code you receive.

How do I get help?

For Woo Payram integration and licensing, contact [email protected]. For Payram server behaviour, use your operator or official Payram docs.