This product is only available to customers with a verified ID.
``` This is the middle ground between gating only the checkout button and gating your whole storefront. It lets you hide the age-restricted parts of a page without forcing every visitor to register and verify before they can see anything — which is the trade-off the [before viewing store](./before-viewing-store.md) flow asks you to make. :::caution This hides content, it doesn't protect it The element is hidden in the browser, but its markup is still present in the page source, and any URL it links to still resolves for an unverified visitor. Use `hidden-until-verified` for presentation. If a visitor genuinely must not reach the content — age-restricted goods, regulated material, anything with a compliance obligation — use [before viewing store](./before-viewing-store.md) or enforce it server-side with the [REST API](../api/checks.mdx). ::: ## Styling the start verification button The button that starts verification is customizable without code through the [appearance section in the settings](../theming/branding.md). But if that doesn't meet your exact criteria, you can use CSS within your site's theme to modify additional properties such as the border, border radius, shadows and more. The Real ID verification button has the class name `.real-id-start-verification`, which you can use to apply custom styling via CSS rules. Here is an example: ``` button.real-id-start-verification { border-radius: 5px; /* Adjust the value to control the amount of rounding */ } ``` ## Troubleshooting ### Occasionally unverified customers checkout If your seeing orders come through occasionally where customers can still checkout without completeing their ID check, you can follow these steps.Loading...
{% endif %} // highlight-endThis product is only available to customers with a verified ID.
``` This is the lighter-touch option when forcing every visitor through a full-page gate would cost you too much traffic. The same caveat applies — it's presentation, not enforcement. ## Option 2: Server-Side Enforcement For a gate that actually holds, keep the check ID in the visitor's session and confirm its status with the REST API before rendering protected routes. ```javascript // Middleware example (Express.js) async function requireVerification(req, res, next) { const checkId = req.session.realIdCheckId; if (checkId) { const response = await fetch( `https://real-id.getverdict.com/api/v1/checks/${checkId}`, { headers: { Authorization: `Bearer ${process.env.REAL_ID_API_TOKEN}` } } ); const { check } = await response.json(); if (check.step === "completed") { return next(); // Allow access } } // Redirect to verification page res.redirect("/verify"); } // Apply to protected routes app.use("/shop", requireVerification); app.use("/products", requireVerification); ``` A check reaches `step: "completed"` when the customer passes your rules **or** when a staff member [manually approves it](/help/docs/for-merchants/overridding-results). ### Verification Page Create a dedicated route that creates the check and hands the visitor to the hosted flow: ```javascript // /verify route — create the check server-side, then redirect app.get("/verify", async (req, res) => { const response = await fetch("https://real-id.getverdict.com/api/v1/checks", { method: "POST", headers: { Authorization: `Bearer ${process.env.REAL_ID_API_TOKEN}`, "Content-Type": "application/json", }, body: JSON.stringify({ customer: { email: req.query.email } }), }); const { check } = await response.json(); req.session.realIdCheckId = check.id; res.redirect(`https://verify.getverdict.com/${check.id}`); }); ``` You can also embed the flow on your own `/verify` page with `RealID.createFlow()` and pass the `checkId`, rather than redirecting off-site. ### Reacting to the result Use a [webhook](/help/docs/api/webhooks) so your app learns the outcome immediately: ```javascript app.post("/webhooks/realid", (req, res) => { const { event, check } = req.body; if (event === "check.completed") { // Mark this check as verified in your database — the visitor can now // access protected content on their next request. markVerified(check.id); } res.sendStatus(200); }); ``` Always [verify the `X-Real-ID-Signature` header](/help/docs/api/webhooks#verifying-webhooks) before trusting a webhook payload. ## Remembering Verified Visitors Real ID already tracks returning customers for you — by browser cookie, by logged-in account, and by email address (with a 6-digit confirmation code). See [Remember verified customers](/help/docs/flows/remember-repeat-customers) for how each method behaves and how to turn the confirmation code off. If you're enforcing server-side, store the outcome yourself as well: ```javascript // Store on the user record for logged-in visitors await db.users.update({ where: { id: userId }, data: { idVerified: true, idVerifiedAt: new Date(), realIdCheckId: checkId, }, }); ``` :::note IDs expire A driver's licence that's valid today may be expired next year. Real ID invalidates checks once the document's expiry date passes, so re-read the check status rather than caching "verified" forever. ::: ## Excluding Pages Let visitors reach your policy, contact and verification pages without being gated: ```javascript const publicPaths = ["/privacy", "/terms", "/contact", "/verify"]; function requireVerification(req, res, next) { if (publicPaths.includes(req.path)) { return next(); // Skip verification } // ... verification logic } ``` ## Verification Rules Since there's no order involved, verification is based on the visitor alone: - **Age verification** — require a minimum age - **Face match** — require a selfie matching the ID photo - **Document types** — specify accepted ID types Configure these in your Real ID dashboard under **Settings → Rules**. ## Testing 1. Clear your cookies or use an incognito window 2. Visit a protected page 3. Complete verification using [test mode](/help/docs/getting-started/test-mode) 4. Confirm you can now access the protected content 5. Refresh to confirm the verification is remembered :::tip See it running first The [SDK Playground store gate demo](/help/sdk-playground?scenario=store-gate) runs this exact pattern against a mock landing page, so you can watch the reveal happen before building it. That link opens the scenario directly — handy for sharing. ::: [View full JS SDK documentation →](/help/docs/js) --- // File: getting-started/_steps/_store-gate-shopify # Set Up Store Gate The "Before Viewing Store" flow requires all visitors to verify their identity before they can browse your products. This is ideal for age-restricted stores or exclusive membership sites. ## How It Works 1. When a visitor arrives at your store, they see a verification prompt instead of your products 2. The visitor completes ID verification 3. Once verified, they can browse and shop normally 4. Verified visitors are remembered and won't be prompted again ## Enable the Store Gate 1. Open the Real ID app in your Shopify admin 2. Go to **Settings** → **Automations** 3. Enable **Automated ID checks** 4. Select **Before viewing store** as the flow ## Add the Theme Block For the store gate to work, you need to add the Real ID block to your theme: 1. Go to **Online Store** → **Themes** in Shopify admin 2. Click **Customize** on your active theme 3. In the theme editor, go to **App embeds** (or **Theme settings**) 4. Enable the **Real ID Store Gate** embed 5. Click **Save** :::tip The store gate uses a full-page overlay that covers your store content until the visitor is verified. ::: ## Customize the Gate You can customize what visitors see on the verification gate: 1. Go to **Settings** → **Appearance** in Real ID 2. Edit the **Welcome message** to explain why verification is required 3. Upload your logo so visitors recognize your brand 4. Choose colors that match your store theme ## Verification Rules Since there's no order at this point, verification is based on the customer only: - **Age verification** - Check if the visitor meets your minimum age requirement - **Face match** - Require a selfie to match the ID photo - **Document types** - Choose which ID types to accept :::note Location-based age rules will use the address on the customer's ID document, since there's no shipping address available. ::: ## Remembering Verified Visitors Once a visitor completes verification: - A cookie remembers them on that device/browser - If they create an account, verification is linked to their customer profile - They won't need to verify again unless they clear cookies or use a new device ## Testing To test the store gate: 1. Open your store in an incognito/private browser window 2. You should see the verification prompt 3. Complete verification using [test mode](/help/docs/getting-started/test-mode) 4. After verification, you should be able to browse the store [Learn more about the Before Viewing Store flow →](/help/docs/flows/before-viewing-store) --- // File: getting-started/_steps/_store-gate-woocommerce # Set Up Store Gate The "Before Viewing Store" flow requires all visitors to verify their identity before they can browse your products. This is ideal for age-restricted stores or exclusive membership sites. ## How It Works 1. When a visitor arrives at your store, they see a verification prompt instead of your products 2. The visitor completes ID verification 3. Once verified, they can browse and shop normally 4. Verified visitors are remembered and won't be prompted again ## Enable the Store Gate 1. Go to **Real ID** → **Settings** in your WordPress admin 2. Navigate to the **Automations** tab 3. Enable **Automated ID checks** 4. Select **Before viewing store** as the flow 5. Click **Save** ## How the Gate Displays Real ID automatically adds a full-page overlay to your site that: - Covers all store content until verification is complete - Shows your logo and custom welcome message - Provides the verification flow inline The gate is injected via JavaScript, so no theme modifications are required. ## Customize the Gate You can customize what visitors see on the verification gate: 1. Go to **Real ID** → **Settings** → **Appearance** 2. Edit the **Welcome message** to explain why verification is required 3. Upload your logo so visitors recognize your brand 4. Choose colors that match your store theme ## Exclude Specific Pages You may want to allow access to certain pages without verification (like your privacy policy or contact page): 1. Go to **Real ID** → **Settings** → **Automations** 2. Find the **Excluded pages** setting 3. Add the page slugs or IDs you want to exclude Common pages to exclude: - `/privacy-policy/` - `/terms-of-service/` - `/contact/` ## Verification Rules Since there's no order at this point, verification is based on the customer only: - **Age verification** - Check if the visitor meets your minimum age requirement - **Face match** - Require a selfie to match the ID photo - **Document types** - Choose which ID types to accept :::note Location-based age rules will use the address on the customer's ID document, since there's no shipping address available. ::: ## Remembering Verified Visitors Once a visitor completes verification: - A cookie remembers them on that device/browser - If they're logged in, verification is linked to their WordPress user account - They won't need to verify again unless they clear cookies or use a new device ## Testing To test the store gate: 1. Log out of WordPress (or use incognito mode) 2. Visit your store's homepage 3. You should see the verification prompt 4. Complete verification using [test mode](/help/docs/getting-started/test-mode) 5. After verification, you should be able to browse the store [Learn more about the Before Viewing Store flow →](/help/docs/flows/before-viewing-store) --- // File: getting-started/_steps/_triggers-bigcommerce # Configure Verification Triggers Triggers determine which orders require ID verification. You can enable multiple triggers - if any trigger matches, the customer will be prompted to verify their ID. ## Access Trigger Settings 1. Log in to your Real ID dashboard 2. Navigate to **Settings** → **Automations** 3. Ensure **Enable automated ID checks** is turned on ## Available Triggers ### All Orders Enable this to verify every customer who places an order. Best for: - Age-restricted product stores - High-security requirements - Compliance mandates ### High Value Orders Verify orders above a specified total amount. Great for: - Reducing fraud on expensive items - Protecting against chargebacks Set your threshold (e.g., orders over $200) in the settings. ### Specific Products Verify only when certain products are in the cart: 1. Go to the **Filters** section in settings 2. Select the products that require verification 3. Orders containing those products will trigger verification ### Shipping Location Verify orders shipping to specific regions: - All U.S. orders - Specific U.S. states - Useful for location-based age requirements ## Order Status Syncing BigCommerce orders can be automatically updated based on verification status: 1. Go to **Settings** → **Order Statuses** 2. Configure which BigCommerce status to use for: - Orders pending verification - Orders that passed verification - Orders that failed verification [Learn more about order status syncing →](/help/docs/bigcommerce/order-statuses) ## Exceptions You can exclude orders from verification based on: - **Already verified customers** - Don't re-verify repeat customers - **Specific shipping methods** - Exclude certain delivery types ## Custom Trigger Scripts For advanced trigger logic, BigCommerce supports custom scripts. See our [BigCommerce custom trigger documentation](/help/docs/bigcommerce/after-checkout#custom-trigger-scripts) for examples. ## Next Steps After setting up triggers, we'll customize how the verification appears to your customers. --- // File: getting-started/_steps/_triggers-custom # Triggering ID Verification With a custom integration you decide when verification is required. There are two places to make that decision: on your server with the REST API, or in the browser with the JS SDK. ## Creating an ID Check (server-side) Use the REST API when your own backend already knows the order or customer should be verified: ```javascript // Server-side example (Node.js) const response = await fetch("https://real-id.getverdict.com/api/v1/checks", { method: "POST", headers: { Authorization: `Bearer ${process.env.REAL_ID_API_TOKEN}`, "Content-Type": "application/json", }, body: JSON.stringify({ customer: { first_name: customer.firstName, last_name: customer.lastName, email: customer.email, phone: customer.phone, // enables SMS delivery }, order: { name: order.number, // human-readable order reference }, }), }); const { check } = await response.json(); console.log("Created ID check:", check.id); ``` Real ID delivers the check to the customer by email and/or SMS using your notification templates. You can also hand them the link directly: ``` https://verify.getverdict.com/{checkId} ``` :::note Only `customer.email` or `customer.phone` is required Everything else is optional — but the more you send, the better Real ID can personalize the notification and run [cross-checking rules](/help/docs/rules/cross-checking-orders) against the ID. ::: ## Common Trigger Patterns Because you own the condition, any signal in your system can gate verification. ### Order-Based Triggers ```javascript // Trigger based on order value if (order.total > 200) { await createIdCheck(customer, order); } // Trigger based on products const requiresId = order.items.some((item) => item.categories.includes("age-restricted") ); if (requiresId) { await createIdCheck(customer, order); } // Trigger based on customer history if (customer.orderCount === 1) { // First-time customer await createIdCheck(customer, order); } ``` ### Risk-Based Triggers ```javascript // Trigger based on fraud score (from your fraud detection system) if (order.fraudScore > 0.7) { await createIdCheck(customer, order); } // Trigger based on address mismatch if (order.billingAddress.country !== order.shippingAddress.country) { await createIdCheck(customer, order); } ``` ### Location-Based Triggers ```javascript // Trigger based on shipping state (for age verification) const ageRestrictedStates = ["CA", "NY", "TX"]; if (ageRestrictedStates.includes(order.shippingAddress.state)) { await createIdCheck(customer, order); } ``` ## Triggering from the browser If the decision happens client-side — a cart that just picked up a restricted item, for example — mount the SDK instead of calling your backend. ### Gate a button with `mode: "modal"` `modal` mode replaces the target element until the customer passes, then restores it: ```javascript if (cartContainsAgeRestrictedItem()) { RealID.createFlow({ target: "#checkout-button", mode: "modal", publicKey: "pk_your-public-key-here", email: customerEmail, }); } ``` Listen for the verification events on `window` to run your own logic: ```javascript window.addEventListener("real-id-check-passed", (event) => { const { check } = event.detail; console.log("ID check passed", check.id); enableCheckoutButton(); }); window.addEventListener("real-id-check-failed", (event) => { const { check } = event.detail; console.log("ID check failed", check.id, "step:", check.step); showVerificationRequired(); }); ``` ### Decide without rendering anything `RealID.createCheck()` creates the check and returns a status without mounting any UI — useful when you want to own the button and the redirect: ```javascript const result = await RealID.createCheck({ publicKey: "pk_your-public-key-here", email: customerEmail, }); switch (result.status) { case "already_verified": case "not_required": proceedToCheckout(); break; case "verification_required": window.open(result.url, "_top"); // hosted flow URL for this check break; case "requires_2fa": // returning customer matched by email — send them to result.url to confirm break; case "error": console.error("Real ID:", result.code, result.message); break; } ``` :::info `createCheck` never throws for a known outcome It always resolves to a result object — switch on `result.status`. See the [full status table](/help/docs/js#responses). ::: ## Next Steps After implementing triggers, we'll customize how the verification appears to your customers. --- // File: getting-started/_steps/_triggers-shopify-after-checkout # Configure After Checkout Verification You've selected the **After Checkout** flow. Let's configure when and how ID verification appears to your customers. ## Step 1: Enable After Checkout Flow 1. Open the Real ID app in your Shopify admin 2. Navigate to **Settings** → **Automations** 3. Enable **Automated ID checks** 4. Select **After Checkout** as your verification flow 5. Click **Save**  ## Step 2: Add Checkout Extensions (Recommended) For the best customer experience, add the Real ID checkout extensions to display verification directly on the Thank You and Order Status pages: 1. In Shopify admin, go to **Settings** → **Checkout** 2. Click **Customize** next to your checkout 3. Navigate to the **Thank you** page 4. Click **Add app block** and select **Real ID** 5. Repeat for the **Order status** page 6. Click **Save** :::tip Without checkout extensions, Real ID will still work by sending verification links via email and SMS. The extensions provide an inline experience that increases completion rates. ::: [Learn more about Checkout Extensions →](/help/docs/flows/during-checkout) ## Step 3: Configure Triggers Triggers determine which orders require ID verification. You can enable multiple triggers - if any trigger matches, the customer will be prompted to verify their ID. ## Available Triggers ### All Orders Enable this to verify every customer who places an order. Best for: - Age-restricted product stores - High-security requirements - Compliance mandates ### High Value Orders Verify orders above a specified total amount. Great for: - Reducing fraud on expensive items - Protecting against chargebacks Set your threshold (e.g., orders over $200) in the settings. ### High Risk Orders Automatically verify orders flagged as medium or high risk by Shopify's fraud analysis. This works with: - Shopify's built-in fraud detection - Third-party fraud prevention apps ### Specific Products or Collections Verify only when certain products are in the cart: 1. Create a collection for products requiring verification 2. In Real ID settings, select that collection 3. Orders containing those products will trigger verification :::tip Create a hidden collection called "ID Required" to easily manage which products need verification. ::: ### Mismatching Billing/Shipping Verify when the billing name or address doesn't match the shipping address. Helps catch potential fraud. ### Shipping Location Verify orders shipping to specific regions: - All U.S. orders - Specific U.S. states - Useful for location-based age requirements ## Exceptions You can exclude orders from verification based on: - **Already verified customers** - Don't re-verify repeat customers - **In-store pickup** - Skip verification for pickup orders - **Specific shipping methods** - Exclude certain delivery types - **Payment gateways** - Skip orders paid via PayPal, etc. - **Sales channels** - Exclude marketplace orders (Amazon, Walmart) ## Advanced: Shopify Flow For complex trigger logic, use [Shopify Flow integration](/help/docs/shopify/flow) to create custom conditions. ## Next Steps After setting up triggers, we'll customize how the verification appears to your customers. --- // File: getting-started/_steps/_triggers-shopify-after-registration # Configure After Registration Verification You've selected the **After Registration** flow. This flow verifies customers when they create an account on your store, rather than during the checkout process. ## Step 1: Enable After Registration Flow 1. Open the Real ID app in your Shopify admin 2. Navigate to **Settings** → **Automations** 3. Enable **Automated ID checks** 4. Select **After Registration** as your verification flow 5. Click **Save** ## Step 2: How It Works When a customer creates an account on your store: 1. They complete Shopify's standard account registration 2. Real ID sends them a verification request via email 3. The customer completes ID verification 4. Their account is marked as verified with a customer tag ## Step 3: Configure Customer Tags Real ID uses Shopify customer tags to track verification status: 1. In Real ID settings, go to **Tags & Feedback** 2. Configure the tags for: - **Verified customers** - Tag applied when verification passes - **Pending verification** - Tag applied when awaiting verification - **Failed verification** - Tag applied when verification fails You can use these tags in Shopify to: - Grant access to exclusive content or products - Apply special pricing or discounts - Filter customers in your admin [Learn more about customer tags →](/help/docs/shopify/tags) ## Available Triggers For After Registration, triggers work differently than order-based flows: ### All Registrations Verify every new customer account created on your store. Best for: - Age-gated stores requiring verified customers - Membership sites - B2B stores requiring identity verification ### Specific Customer Groups You can configure verification based on: - Customer location (shipping address country/state) - Email domain filtering - Custom conditions via Shopify Flow ## Exceptions You can exclude accounts from verification based on: - **Previously verified** - Skip customers already verified from orders - **Specific email domains** - Allow certain domains without verification ## Integration with Checkout If you also want to verify at checkout: - After Registration ensures all account holders are verified - You can combine with After Checkout for guest purchases - Verified customers skip checkout verification automatically [Learn more about the After Registration flow →](/help/docs/flows/after-registration) ## Next Steps After setting up triggers, we'll customize how the verification appears to your customers. --- // File: getting-started/_steps/_triggers-shopify-before-checkout # Configure Before Checkout Verification You've selected the **Before Checkout** flow. Let's configure when and how ID verification appears to your customers. ## Step 1: Enable Before Checkout Flow 1. Open the Real ID app in your Shopify admin 2. Navigate to **Settings** → **Automations** 3. Enable **Automated ID checks** 4. Select **Before Checkout** as your verification flow 5. Click **Save** ## Step 2: Add Checkout Extensions (Required) Before Checkout verification uses Shopify's checkout extensions to display the verification form during checkout. This is required for the Before Checkout flow to work: 1. In Shopify admin, go to **Settings** → **Checkout** 2. Click **Customize** next to your checkout 3. In the checkout editor, click **Add app block** 4. Select **Real ID** from the list 5. Position the block where you want verification to appear (typically in the contact or shipping section) 6. Click **Save** :::warning The Before Checkout flow requires checkout extensions to be enabled. Without this, customers won't see the verification form during checkout. ::: [Learn more about Checkout Extensions →](/help/docs/flows/during-checkout) ## Step 3: Configure Triggers Triggers determine which checkouts require ID verification. You can enable multiple triggers - if any trigger matches, the customer will be prompted to verify their ID before completing checkout. ## Available Triggers ### All Orders Enable this to verify every customer at checkout. Best for: - Age-restricted product stores - High-security requirements - Compliance mandates ### High Value Orders Verify checkouts above a specified total amount. Great for: - Reducing fraud on expensive items - Protecting against chargebacks Set your threshold (e.g., orders over $200) in the settings. ### Specific Products or Collections Verify only when certain products are in the cart: 1. Create a collection for products requiring verification 2. In Real ID settings, select that collection 3. Checkouts containing those products will trigger verification :::tip Create a hidden collection called "ID Required" to easily manage which products need verification. ::: ### Shipping Location Verify checkouts shipping to specific regions: - All U.S. orders - Specific U.S. states - Useful for location-based age requirements ## Exceptions You can exclude checkouts from verification based on: - **Already verified customers** - Don't re-verify repeat customers - **In-store pickup** - Skip verification for pickup orders - **Specific shipping methods** - Exclude certain delivery types ## Checkout Experience With Before Checkout verification: - Customers verify their ID during the checkout process - Verification is completed before payment is processed - Orders are only created for verified customers - No need to hold or cancel orders post-purchase [Learn more about the Before Checkout flow →](/help/docs/flows/before-checkout) ## Next Steps After setting up triggers, we'll customize how the verification appears to your customers. --- // File: getting-started/_steps/_triggers-woocommerce # Configure Verification Triggers Triggers determine which orders require ID verification. You can enable multiple triggers - if any trigger matches, the customer will be prompted to verify their ID. ## Access Trigger Settings 1. In your WordPress admin, go to **Real ID** → **Settings** 2. Navigate to the **Automations** tab 3. Ensure **Enable automated ID checks** is turned on ## Available Triggers ### All Orders Enable this to verify every customer who places an order. Best for: - Age-restricted product stores - High-security requirements - Compliance mandates ### High Value Orders Verify orders above a specified total amount. Great for: - Reducing fraud on expensive items - Protecting against chargebacks Set your threshold (e.g., orders over $200) in the settings. ### Specific Product Categories Verify only when products from certain categories are in the cart: 1. Go to the **Filters** section in Automations settings 2. Enable the **Categories** filter 3. Select the categories that require verification :::tip Create a category called "Age Restricted" or "ID Required" to easily manage which products need verification. ::: ### Specific Products You can also select individual products that require verification, independent of their category. ### Mismatching Billing/Shipping Verify when the billing name or address doesn't match the shipping address. Helps catch potential fraud. ### Shipping Location Verify orders shipping to specific regions: - All U.S. orders - Specific U.S. states - Useful for location-based age requirements ## Order Status Integration WooCommerce orders can be automatically held or updated based on verification status: 1. Go to **Real ID** → **Settings** → **Order Statuses** 2. Configure which WooCommerce status to use for: - Orders pending verification - Orders that passed verification - Orders that failed verification [Learn more about order status syncing →](/help/docs/woocommerce/order-statuses) ## Exceptions You can exclude orders from verification based on: - **Already verified customers** - Don't re-verify repeat customers - **Specific shipping methods** - Exclude certain delivery types - **Payment gateways** - Skip orders paid via PayPal, etc. ## Next Steps After setting up triggers, we'll customize how the verification appears to your customers. --- // File: getting-started/test-mode # Test Mode When you first install Real ID to your store, the app is in **Test Mode**. In test mode, you're granted all features for free and can also send test ID checks at no charge. This gives you the opportunity to sample all of Real ID's features and verify it works correct with your store and theme before choosing a plan. If the app is in test mode, you'll see this banner at the top of each page:  :::tip Real ID is free to install on any Shopify store, including [Development Stores](https://help.shopify.com/en/partners/dashboard/managing-stores/development-stores). Test mode will still activate triggers like [ID verification on specific types or orders](./../flows/after-checkout.mdx), or flows like [ID verification before checkout](./../flows/before-checkout.mdx). We recommend you install Real ID on a development store first in order to trial these features before applying it to your live store. ::: ## Restrictions In test mode, you'll be able to use all **Pro** level features as well as send ID checks. However, there are a few restrictions: * All ID checks sent in test mode will have mock fake data and will always pass * Enterprise features are not included in test mode :::info ID checks sent during test mode will have mock data that represents what the app could read. The images of the ID and headshot will also be blurred. ::: ## Notifications in Test Mode In test mode, **no emails or SMS messages are sent to your customers**. Instead, notification emails are redirected to your store's [contact email](/help/docs/for-merchants/id-check-notifications) with a **[TEST]** prefix in the subject line. This means you can: * Safely create test ID checks using real customer order data without worrying about customers receiving unexpected messages * Preview exactly what the customer email looks like in your own inbox * Easily identify test emails by the **[TEST]** tag in the subject line :::note SMS notifications are skipped entirely in test mode since they cannot be redirected. Only email notifications are sent (to the merchant contact email). Automatic reminders are also not scheduled for test mode checks. ::: ## Going live After you've had a chance to try out the features and decide which plan fits best for your needs, click the **Go Live** button on the left hand side menu:  After picking a plan, you'll be able to send real ID checks with actual results and unblurred photos. :::note You're only able to go into test mode once. But you can downgrade or upgrade your plan at any time. ::: --- // File: id-check-process # ID check process Real ID uses the latest computer vision and A.I. technologies to quickly verify and extract details from ID documents like Driver's Licenses, Passports and Residence Cards. It can be set up to verify IDs before checkout, after checkout or even before being allowed to view your store. Additionally, you can have it set up to only trigger ID verification on specific high risk triggers like total order value or Shopify Fraud Analysis flags. You also can require additional documentation like a corresponding live headshot photo, Proof of Address, and eSignature. The entire process can be completed in as little as a few minutes, and it's entirely automated. But staff can override the automatic results at any time. ## How it works The way a customer is presented with their ID check depends on which flow you choose. But the process is roughly the same for each. First, the customer opens their unique ID check associated with their account. Then they're guided through capturing the photos required according to your rules. Computer vision techniques during the process help guide the customer to take the best photo possible for the best results. Then, the customer will be either automatically approved, or placed into review. :::tip These are not the exhaustive list of methods Real ID uses to verify identity, but a general overview of the various technologies and techniques in place. ::: ## Autocapturing ID photos and headshots Real ID uses A.I. during the capturing of ID photos and headshots to help guide the user to take the best possible photo to optimize for their chance of passing ID verification. This A.I. running on the customer's phone during the ID verification process helps guide them to place their ID within the camera frame at the correct position. It will help guide customers by giving them feedback to show the ID, move it closer or further way from the camera for focus. This helps vastly improve photo quality and helps guide customers to take the best possible photo of their ID A similar A.I. model is used to help guide customers to take a headshot, if required by your rules. :::note The ID autocapture will allow customers to manually capture a photo of their ID after a certain period of time. This is to help customers in extraordinary circumstances still submit photos of their IDs. Then you'll be able to take the final judgement and approve or reject these submissions manually. The Real ID dashboard will show you if a submission was manually captured instead of automatically captured. ::: ## How is an ID accepted or rejected? During verification, an ID is accepted when all required fields such as name, address, date of birth, and date of expiration can be read with high confidence and meet your additional rules such as [cross checking order details](./rules/cross-checking-orders.md), [biometric verification](#face-match), and [age verification](./rules/age-verification.md). Real ID uses multiple A.I. models to determine the validity and liveness of the photos as well as models to extract the fields from the ID into a standard format. But this confidence is customizable, you can lower or raise the threshold of confidence required for an accepted ID. Additionally, you can manually override the results at any time, even if the system is unable to automatically verify it. :::note Hard rules Some rules don't rely on confidence alone, such as detecting expired ID documents. Adjusting the confidence threshold for your ID checks won't affect the expiration date checks for example. ::: ## Maximum soft retries During the ID check process, customers are given 3 attempts per stage to take a high quality, readable and usable photo. For example, if the ID check requires both the ID photo and a portrait photo to face match against, then customers are given 3 tries to take a good quality photo of their ID as well as 3 photos of their face. These "soft" retries do not incur extra charges. Customers can use all 3 attempts per stage, and you'll only be charged once for the entire check. If customers fail all soft retries in a particular stage, then they'll allowed to move onto the next stage. This allows customers to still continue through the flow in case they have a document that isn't supported like a temporary issued Drivers License, or damaged ID, and gives you a chance to [override the failed ID checks](./for-merchants/overridding-results.md). If you still want to allow customers to try again with a "hard" retry, where customers can try again with a new fresh ID check, [please see this article](./for-merchants/retrying-id-checks.md). ## Allowed captured methods By default Real ID allows customers to both capture photos using their device's camera only. This is the most secure option, since it requires customers to take a live photo of their ID document, as well as take a live selfie photo. [However you can enable manual photo uploading](./rules/control-capture-methods.md). This allows customers to upload photos from their camera roll if they don't have their ID phyiscally available because it's lost or stolen. However, manual file uploads bypass the ID and headshot photo Autocapture feature, which may lead to bad quality photos or a higher chance of failing the ID check. Additionally, disabling the manual file uploads helps increase security because it helps narrow down the possibility of a bad actor using a stolen images. :::tip The Real ID dashboard will show if photos from the ID check were uploaded via a file or captured from the user's camera. In general, photos captured in real time from the camera are more trustworthy than file uploads. ::: ## Face Match If you enable the headshot requirement, Real ID will also verify the headshot matches the headshot physically printed on the ID document. You'll be able to see the similiarity confidence of the captured headshot against the headshot on the ID document from 0% to 100% within the ID check details in the dashboard. If the ID check passes, yet the headshot cannot be confidently matched, then the entire ID check is rejected. :::tip Even if a ID check is rejected to a mismatching photo, you'll be able to override the results in the dashboard. ::: ## Text Extraction Real ID uses modern computer vision techniques to read text fields on the verified ID photo. Real ID can read text fields from Driver's Licenses, Passports, etc like: - `First Name` - `Middle Name` - `Last Name` - `Document Number` - `Address` - `Date of Birth` - `Date of Expiration` - `Endorsements` - `Classes` These fields are especially useful for applying a minimum age verification to your products, or rejecting expired ID documents, or verifying that the shipping or payment details match up with the customer's ID. :::note Some fields like the `First Name` and `Last Name` fields are required in order for the ID check to pass automatically. If an ID check fails because one or more required fields are covered, missing or are inlegible, then you'll see that reason within the ID check details in the dashboard. ::: ## Completed When the customer submits their required information, their photos will undergo additional processing with A.I. models running in Real ID's private cloud. Then Real ID will use the combination verdicts from these models and the results of the [enabled additional rules](./rules/cross-checking-orders.md) to determine if the ID check passes or fails. If the customer fails, they're shown feedback that their ID wasn't able to be automatically passed. If the customer passes, they're shown a call to action to return to the order status page, or return to the cart to checkout, or to notify them they can browse and checkout within your store. Each depends on which ID verification flow you've choosen. :::tip By default Real ID does _not_ cancel or modify the order in any way, even if the ID check failed. Real ID will update metadata, tags and metafields on the orders with ID checks - regardless if the ID check passed or failed. ::: ## What happens after automatic verification Once a customer submits their photos, every ID check ends up in one of a few outcomes. The diagram below shows how a check moves from submission to a final result, and where your staff can step in. ```mermaid flowchart TD A[Customer submits photos] --> B{Automatic verification} B -->|Passes rules & confidence| C([Verified]) B -->|Low confidence, missing fields,We require all customers to verify their ID as a part of account registration.
This one time ID verification is instant and secure through our partner Real ID.
