Vraimony
WooCommerce Order Protection Layer

Install once.
Every order ready before a dispute happens.

The Vraimony WooCommerce plugin records a proof chain on every order status change — created, shipped, delivered. When a dispute opens, the case is already assembled. No scrambling. No missing proof.

Hash-only — no PII sent Privacy-first by design Case ready before the bank asks Works with all WooCommerce gateways
Get the plugin → Run free diagnostic first

◎ We record hashes. We do not store raw order data. We do not control the reviewer's decision.

Reactive vs Proactive

The difference between losing and winning disputes.

❌ REACTIVE (current for most merchants)
⚡
Dispute opens

Bank sends chargeback notification

🔍
Scramble for proof

Search emails, Woo dashboard, carrier portal, screenshots

📎
Assemble manually

Copy, paste, name files, write summary

⏱
Race the deadline

7–45 days depending on processor

❓
Result: often incomplete

Missing proof → chargeback lost

✓ PROACTIVE (with Vraimony plugin)
🛒
Order created → hash recorded

Buyer, items, price, address — hashed at creation

Automated
📦
Order shipped → hash recorded

Tracking, carrier, date — hashed at dispatch

Automated
✅
Delivered → hash recorded

Carrier confirmation — hashed at delivery

Automated
⚡
Dispute opens

Bank sends chargeback notification

⚡
Case assembled instantly

Proof chain already built. Send reviewer link.

Case ready
Technical design

Hash-only. No raw data leaves your server.

The plugin fires on woocommerce_order_status_changed. It hashes order data locally — in your WordPress environment — before sending anything to Vraimony. The Vraimony server never receives raw customer data.

// Plugin fires on every order status change add_action('woocommerce_order_status_changed', function($order_id, $old, $new) { // Hash computed locally — raw data never leaves your server $content_hash = hash('sha256', json_encode([ 'order_id' => $order_id, 'status' => $new_status, 'amount' => $order->get_total(), 'items_hash' => hash('sha256', json_encode($order->get_items())), 'timestamp' => time(), ])); // Only the hash is sent to Vraimony wp_remote_post('https://api.vraimony.com/v1/proactive/record', [ 'body' => json_encode([ 'source' => 'woocommerce', 'event' => 'order.' . $new_status, 'order_id' => (string)$order_id, 'content_hash' => $content_hash, // sha256 hex only 'timestamp' => gmdate('c'), ]) ]); }, 10, 3);
API endpoint:
POST /v1/proactive/record { "source": "woocommerce", "event": "order.shipped", "order_id": "WC-4521", "content_hash": "3a4b5c6d…" // sha256 hex — 64 chars } Response: { "ok": true, "record_id": "prv_a1b2c3…", "case_ready": false, // true when chain is complete "message": "Event recorded. Continue recording events to build the proof chain." }
When a dispute opens, call POST /v1/proactive/build-case/:order_id — the sealed case summary is returned instantly, ready to be sent to the reviewer.
Same engine — different trigger

WooCommerce orders. Supply chain shipments. Same proof chain model.

🛒 WOOCOMMERCE

Triggered by order status changes. Events: created → processing → shipped → delivered → refunded.

source: "woocommerce" events: order.created | order.shipped order.delivered | order.refunded
🚢 SUPPLY CHAIN SDK

Triggered by shipment milestones. Events: created → departed → arrived → delivered → exception.

source: "supply_chain_sdk" events: shipment.created | shipment.departed shipment.delivered | shipment.exception

Same /v1/proactive/record endpoint. Same proof chain logic. Same case-building on dispute. The source field routes the case to the right family and template.

What you see in WooCommerce

One column. Three states. No manual work.

Orders → Vraimony proof status column
#4521Delivered to customer · 2026-04-01✓ Case ready #4522Shipped via UPS · 2026-04-03⏳ Awaiting delivery #4523Dispute opened · 2026-04-05🔗 Send reviewer link → #4524Processing · 2026-04-05Recording…
Next capability — Pre-dispute Signal

Detect dispute risk before the chargeback is filed.

The plugin already records order events. The next layer adds risk detection — watching for early signals that a dispute is forming, before the bank ever sees it.

🔴
Signal detected

Refund request denied + delivery delay + no customer response in 72h

⚡
Case assembled

Proof chain already complete from proactive recording. No scrambling.

📨
Alert sent to merchant

"Order #4521 — dispute risk detected. Send the reviewer link before they file."

// Signals monitored by plugin
refund_request_denied: true
delivery_delay_days: > 3
customer_message_unanswered: true
→ trigger: "dispute_risk_detected"
→ action: assemble_case + notify_merchant

◎ This is a planned capability based on the proactive proof chain already built. Monitoring signals only — no customer tracking, no PII.

Install once. Every order protected.

Stop scrambling for proof when a dispute opens.

Get the WooCommerce plugin → Run free diagnostic first Fix one case manually — $19.99 Open reviewer verify surface →

◎ Hash-only. No raw data stored. No tracking. No outcome guarantee.