ShipToVerified -- WordPress 插件

开发者	shiptoverified pitchercompany
更新时间	2026年7月10日 06:14
PHP版本:	8.0 及以上
WordPress版本:	6.9
版权:	GPLv2 or later
版权网址:	版权信息

ShipToVerified connects your WooCommerce store with the ShipToVerified service to automate identity verification and adult signature compliance for regulated product shipments. The plugin handles the full verification lifecycle:

Evaluates whether an order requires adult signature or identity verification based on the customer's shipping destination and cart contents.
Exposes the store's WordPress customer roles to the ShipToVerified portal and includes the customer's roles in the order data, so merchants can scope the ID Verification rules to specific customer roles (with explicit "All" and "Guest" options) under Settings → Platforms → WooCommerce.
Notifies the ShipToVerified service when a qualifying order is placed.
Renders a secure identity verification widget on the order confirmation and account pages (and, optionally, the order tracking page) so the customer can complete verification without leaving your store.
Receives signed webhook events from ShipToVerified when a customer completes verification or when the verified shipping address changes, and updates the WooCommerce order record accordingly.
Gives store administrators a manual verification option and a verification status panel directly inside the WooCommerce order screen.
Adds a custom "Awaiting Verification" order status (wc-await-verify) that qualifying orders are placed into until verification completes, so unverified orders are easy to spot and filter in WooCommerce.

Who needs this plugin? Retailers that ship age-restricted, regulated, or compliance-sensitive products (such as firearms accessories, tobacco, cannabis, or adult goods) to jurisdictions that require adult signature delivery or government-issued identity verification at the point of purchase. How it works

The merchant connects the store to ShipToVerified via an OAuth flow in WooCommerce > ShipToVerified.
When a customer reaches the checkout page, the plugin sends the cart's shipping state, order total, and product details to the ShipToVerified API to determine whether the cart requires an adult signature fee or identity verification notice.
When the customer places an order and it moves to processing or completed status, the plugin notifies ShipToVerified with the order ID so that a verification requirement can be assigned.
On the order confirmation page (and optionally the account order-detail or order tracking page), the plugin loads an identity verification widget served by ShipToVerified that guides the customer through document capture and liveness checks.
Once the customer completes the verification flow, ShipToVerified sends a signed webhook back to the store. The plugin validates the signature, marks the order as verified, and stores the verified name and address in the order meta.

External services This plugin connects to the ShipToVerified API (https://api.shiptoverified.com). A ShipToVerified merchant account is required. Connection is established by the store administrator during initial setup via OAuth. Checkout eligibility check Triggered automatically on the checkout page for every customer session (including guests) while the plugin is active and connected. This call determines whether the current cart requires an adult signature fee or identity verification notice.

When it runs: the first time a customer reaches checkout, and again whenever the relevant cart details change (shipping state, cart total, or cart contents). Results are cached for the duration of the customer's session — keyed on a hash of the cart, shipping state, and total — so a repeat checkout page load with an unchanged cart does not trigger another API call.
Data sent: customer's shipping state (two-letter US state code), cart grand total, and line items (product ID, product name, quantity, and product category names).
Why it is sent: ShipToVerified maintains up-to-date jurisdiction rules for regulated products. Sending the cart snapshot allows the service to evaluate applicable state laws without storing a static ruleset inside the plugin.
Data received: a boolean indicating whether an adult signature fee and/or a verification notice should be displayed.

Order created notification Triggered once per order, when the order status first moves to processing or completed.

Data sent: WooCommerce order ID and store URL.
Why it is sent: this tells ShipToVerified to create a verification record linked to the order so it can manage the customer-facing verification flow and track completion.
Data received: a flag indicating whether the order requires identity verification.

Widget initialization Triggered on the order confirmation page (and optionally the account order-detail or order tracking page) when an order requires identity verification.

Data sent: WooCommerce order ID and store URL.
Why it is sent: ShipToVerified generates a short-lived, single-use widget token scoped to that order so that the verification session cannot be replayed or hijacked.
Data received: a widget token and a flag confirming verification is required.
A JavaScript file (/widget.js) is then loaded directly from https://api.shiptoverified.com to render the verification interface. This file is served by the ShipToVerified service and is part of the core service functionality (similar to how payment processors serve their checkout scripts).

Webhook (inbound) ShipToVerified sends a signed POST request to /wp-json/shiptoverified/v1/webhook when a verification event occurs (e.g., the customer completes verification, the verified shipping address changes, the address cannot be validated, or address validation is awaiting customer input).

Supported events: verification.completed, address.updated, address.unverified, address.review_required.
Data received: event type, event ID, order ID, verification ID, verified customer name, and verified shipping address. For the address events the payload instead carries a human-readable reason and/or a suggested address — address.updated sends the corrected address, address.unverified sends a reason, and address.review_required sends a reason plus an optional suggested_address.
For address.review_required, the plugin adds a private order note recording the pending state and any suggested address, and takes no other action (the order stays awaiting the customer's response).
All webhook payloads are validated with an HMAC-SHA256 signature before processing.
Each event is idempotent: duplicate event IDs are ignored.

Order data endpoint (inbound) ShipToVerified may request full order details via GET /wp-json/shiptoverified/v1/order/{id} to display order context inside the ShipToVerified merchant dashboard.

Data returned: order ID, order status, order total and currency, the customer's billing email address (personally identifiable information), the customer's name, account ID, and WordPress roles, the full shipping address (name, street, city, state, postcode, country), and line items (product ID, name, quantity, and product category names).
Authentication: requires the store's API key in the X-API-Key header.

Store roles endpoint (inbound) ShipToVerified may request the store's configured WordPress roles via GET /wp-json/shiptoverified/v1/roles so a merchant can scope ID Verification rules to specific customer roles in the ShipToVerified dashboard.

Data returned: the slug and display name of each WordPress role defined in the store. No customer-specific data is sent.
Authentication: requires the store's API key in the X-API-Key header.

Connection management (OAuth) Used once during initial setup and optionally to test or re-establish the connection.

Data sent: store URL, OAuth authorization code or callback parameters.
Data received: API key, webhook secret.

By installing, activating, and connecting this plugin, the store administrator consents to the transmission of the above data to ShipToVerified on behalf of the store and its customers, in accordance with the service terms.

Merchants are responsible for disclosing the use of this service to their customers in their store's privacy policy.

1.4.0

Feature - Order status changes are now gated by the merchant's "Statuses ShipToVerified may act on" allowlist: holds and releases only apply while the order is in an allowed status, so statuses set by fraud/payment tools (or cancellations) are never overwritten. The live status is re-read right before each write, and the status-changed listener runs at the lowest priority so other plugins act first.
Feature - Releases are idempotent per verification: a re-delivered or re-emitted completion event can no longer release the same order twice, and terminal statuses (cancelled, refunded, failed, completed, trash) are never released over.
Feature - When a status change is skipped, an order note explains why ("verification recorded; status change skipped"). Cancellation notifications fire once per verification cycle and never for already-verified orders.

1.3.2

Fix - Order edits now sync to ShipToVerified on a single save. The order-updated notification now fires after the order has fully saved and sends the edited shipping details inline, so the verification refreshes immediately instead of only after a second save (a read-after-write race with the previous mid-save callback).

1.3.1

Fix - Order update and cancellation sync now trigger for pending orders. The 1.3.0 handlers only fired once a verification id was stored on the order, which does not happen until verification completes, so edits/cancellations of still-pending orders were never sent to ShipToVerified. They now key off the requires-verification flag.

1.3.0

Order update sync. Editing an order's customer name or shipping address after checkout now notifies ShipToVerified so the verification is matched against the current details instead of the data captured at checkout.
Order cancellation sync. Cancelling an order now moves its pending verification to a failed (terminal) state instead of leaving it pending.

1.2.0

Customer role filter for ID Verification. A new /roles REST endpoint exposes the store's WordPress roles to the ShipToVerified dashboard, and order snapshots now include the customer's roles. Merchants can choose in the dashboard which customer roles the verification rules apply to (with explicit "All" and "Guest" options); orders whose customer role is excluded skip ID verification.

1.1.1

Webhook handler now supports address.review_required — fired when an address-only verification is sitting on customer interaction (suggestion to accept, candidate list to pick from, or a missing unit/apartment number). The plugin adds a private order note describing what Radar returned and what input is needed, so merchants see the pending state in the WooCommerce order admin without having to check the ShipToVerified dashboard. Note is posted once per order; duplicate event deliveries are ignored via the existing idempotency guard.

1.1.0

Add support for Radar-powered shipping address validation as a standalone post-checkout flow (separate from ID verification).
Webhook handler now supports two new events:
address.updated — fired when the customer accepts a Radar-suggested address or submits a corrected one. The plugin updates the WooCommerce shipping address and adds an order note with the new address.
address.unverified — fired when Radar cannot validate the shipping address. The plugin adds an order note flagging the order for manual review.
Widget injection no longer marks the order as _requires_id_verification when the verification flow is address-only. ID-only verifications continue to behave as before.
Webhook handlers defensively clear _requires_id_verification after a successful address validation so legacy/in-flight orders don't stay tagged as ID-pending.

1.0.0

Initial public release.

ShipToVerified

标签

下载

详情介绍:

安装:

常见问题:

更新日志: