Ubuntu server and DNS base. Keep the main and verify apps on the server you control.
Fast path · WooCommerce-first · No API keys needed for the basic widget path
Quick start
Run Vraimony with WooCommerce, ServerAvatar, and Hetzner without overcomplicating the first setup.
The basic path should work immediately after download: install the WordPress plugin ZIP, activate it, add the shortcode, and keep verification on the official Vraimony domain. Only add REST API keys or WooCommerce webhooks when you need deeper or repeated automation.
Recommended topology
Keep each layer in its lane.
App and domain management for www.vraimony.com and verify.vraimony.com.
Checkout and store workflow. Start with the plugin helper before trying deeper automation.
Fastest path
What should work immediately after download
1
Upload the plugin ZIP
WordPress Admin → Plugins → Add New → Upload Plugin → activate vraimony-wordpress-plugin.zip.
2
Use the helper as shipped
The current plugin is iframe-only and verify-first. For the basic path you do not need REST API keys or a webhook just to show Vraimony verify or evidence links.
3
Place the shortcode
Add the shortcode to an order-status page, customer help page, or internal admin note flow.
4
Keep verification on the official domain
Use https://verify.vraimony.com for public checking. Keep admin only on www.vraimony.com.
Copy-paste basics
Use these values as the safe default map.
Main app
https://www.vraimony.com
Verify front door
https://verify.vraimony.com
Admin
https://www.vraimony.com/admin/
Store / Woo path
Keep checkout in WooCommerce. Use Vraimony for review, evidence packaging, and verification.
Advanced path
Only add WooCommerce REST API keys or webhooks when repeated integration is already justified.
REST API
Use this for deeper store-to-core workflows, repeated syncing, or partner-grade integrations. Do not require it for the first install if the helper is enough.
Webhooks
Use WooCommerce webhooks only when you want event-driven delivery into a deeper licensed or integrator setup. The first save should target a stable delivery URL and be tested before broad rollout.
What not to do
Do not make the first setup heavier than the first value.
- Do not start with custom automation if the iframe-only helper already solves the first proof problem.
- Do not put admin, verify, and checkout on the same confused path.
- Do not force partner or embedded language into the first merchant install.
- Do not expose keys or internal trust controls in the store-side helper.