Verify AI
Platform · Integrations

A Shopify app, and one endpoint for everything else.

Verify AI reads orders after they are created. Nothing about your storefront, your payment provider, or your fulfilment has to change before it can start scoring.

Start freeSee the API
Being straight about this

Most integration pages are a wall of logos.

They imply certified apps and one-click installs, and then the fine print says webhook.

So here it is plainly. There is one native app, for Shopify, and it is genuinely native: extensions on the order page, automatic scoring, and write-back. Everything else is a REST call, which works with every platform on the market including the ones a logo grid would not have listed.

That is a deliberate trade. Building eight shallow connectors would have cost the depth of the one that carries most of the work.

Surfaces

Every way an order reaches the engine

Shopify
A native app. Automatic scoring from the orders/create webhook, the assessment on the order page, an action on orders and draft orders, and a risk tag your Flow rules can act on.
WooCommerce
Hook woocommerce_checkout_order_processed, POST the order, and set the order status from the band. Around forty lines of PHP.
BigCommerce
Take the order-created webhook, fetch the order, POST it, and move high and critical orders to Awaiting Review.
Custom checkouts
Anything that can make an HTTPS request can score an order. Call it after the order is created, from a queue rather than from the buyer’s request.
TDCCommerce Unified ERP
Verify AI is part of the TDCCommerce platform, so the same scoring is available natively to teams running the unified ERP and storefront.
Warehouses and internal tools
Everything readable in the dashboard is readable through the API, so pulling scores and log rows into your own reporting is a scheduled script.
What the Shopify app adds, surface by surface
Example

WooCommerce, end to end

The shape is the same on every platform: take the order-created hook, POST the payload, act on the band.

functions.php
add_action('woocommerce_checkout_order_processed', function ($order_id) {
  $order = wc_get_order($order_id);

  $response = wp_remote_post(VERIFY_AI_ENDPOINT, [
    'headers' => [
      'Authorization' => 'Bearer ' . VERIFY_AI_KEY,
      'Content-Type'  => 'application/json',
    ],
    'body' => json_encode(verify_ai_payload($order)),
  ]);

  $result = json_decode(wp_remote_retrieve_body($response), true);
  $level  = $result['data']['riskLevel'] ?? null;

  if ($level === 'high' || $level === 'critical') {
    $order->update_status('on-hold', 'Verify AI: ' . $level . ' risk');
  }
});

Run this from an async hook or a queued job rather than inline. The analysis takes 15 to 30 seconds, and the order already exists by the time it starts.

In practice

What this looks like on your stack

Shopify

Install, approve the scopes, done. Automatic scoring and tagging are on by default.

Another hosted platform

Take the order-created webhook, POST the order, and set the order status or add a note from the band.

Headless or custom

Score from the same worker that sends the confirmation email. Nothing needs to sit in the checkout path.

Marketplace or multi-channel

One key per organization, so orders from several channels land in one log with one balance behind them.

An internal ops tool

Score on demand from an admin screen, which is often the fastest first integration for a team already reviewing by hand.

TDCCommerce

Already there. Same engine, same log, no integration to write.
Integrations

The honest answers

Is there an app for platforms other than Shopify?
Not today. Shopify got a native app because that is where the demand was; everything else goes through the API, which is one endpoint and one response shape. If a native connector for your platform would change your decision, tell sales which platform, because that is how the roadmap gets ordered.
Do we have to replatform?
No, and that would be an absurd thing to ask in exchange for a fraud score. Verify AI sits beside whatever runs your checkout and reads orders after they are created.
Can it write into our system?
Only Shopify, and only the risk tag and app metafields. Everywhere else it returns the assessment and your side decides what to do with it, which keeps the write path under your control and your audit.
Where in our flow should the call go?
After the order is created, from a background job. A verification takes 15 to 30 seconds, and holding a buyer at the payment step for that long costs more in abandoned carts than the fraud it prevents.
What if our platform cannot run background jobs?
Send the order to a queue you control, or to a small function, and call from there. The one pattern to avoid is calling synchronously from the checkout request itself.

Score twenty orders from last week.

Whichever path you would use in production, the free credits cover a real test of it.

Start freeRead the docs

5 credits on signup · no card required