Skip to content
  • There are no suggestions because the search field is empty.

Integrations | Veriscan Integration

BLAZE's Veriscan Integration v1 connects BLAZE USA POS with VeriScan Cloud via a secure webhook. When a customer's ID is scanned using the Veriscan mobile app, it creates or matches a member profile in BLAZE, adds the customer to the walk-in queue, and can initiate an order — all without any manual staff input.

Prerequisites

Features & Benefits

How to Configure the Veriscan Webhook

Queue Behavior

FAQ: Setup & Configuration

FAQ: Queue & Workflow

FAQ: Troubleshooting

Prerequisites

  • App: VeriScan Cloud & Veriscan Mobile App
  • App: BLAZE USA POS
  • Requirement: VeriScan Developer Key and Terminal ID


NOTE: Configuration is done entirely within VeriScan Cloud by the dispensary. Because this requires access to your VeriScan account, BLAZE cannot complete this setup on your behalf.

Features & Benefits

Feature Benefit
Instant Queue Placement Scanned customers are automatically added to the walk-in queue; no manual check-in is required.
Auto-Member Creation New customers are registered in BLAZE on their first scan; returning customers are matched automatically.
Auto-Populated Profiles Date of birth and ID details are pulled directly from the scan, drastically reducing data entry errors.
Auto-Order Creation Orders can be initiated automatically upon scan, accelerating the queue-to-counter workflow.
Flexible Setup Endpoint naming can match the shop’s location (e.g., "California", "SoCal") for clear organization.
Per-Device Configuration Each Veriscan device is individually credentialed, giving shops precise control over their hardware.

How to Configure the Veriscan Webhook

Follow these steps to set up the integration inside your VeriScan Cloud account:

  1. Log into your VeriScan Cloud account.
  2. Navigate to Integrations > Webhooks > Enable Webhooks > Add Endpoint.
  3. Set the URL to the designated BLAZE webhook endpoint. Choose the URL based on the environment you are configuring:
Environment Webhook URL
Production (Live) [https://api.blaze.me/api/v1/webhooks/veriscan]
  1. Add the required Authorization header using your dispensary's developer key.
  2. (Optional) Add the X-Terminal-ID header with your specific terminal ID.
  3. Define the location. The endpoint naming is flexible and is typically based on your location (e.g., "California" or "SoCal").
  4. Click Save.
  5. Configure each physical Veriscan device using the credentials provided by Veriscan. Shops receive a fixed number of device slots per their VeriScan agreement.

Queue Behavior

The integration is specifically designed to push scanned customers into the walk-in queue, not the check-in queue. This reflects a seamless walk-in workflow where customers arrive, are scanned at the door, and instantly appear in the queue for service. Staff can then proceed through the normal POS order workflow from there.

FAQ: Setup & Configuration

Q: How do I configure the Veriscan webhook integration in BLAZE?

A: Configuration is done entirely within VeriScan Cloud. Navigate to Integrations > Webhooks > Enable Webhooks > Add Endpoint. Set the URL to the BLAZE production endpoint, add your Authorization header using your developer key, and optionally add your X-Terminal-ID. Once saved, Veriscan will begin sending scan events to BLAZE automatically.

Q: Where do I find my developer key and terminal ID?

A: Your developer key and terminal ID are provided by VeriScan as part of your account credentials. Log into VeriScan Cloud and navigate to your account or integration settings to locate them. If you cannot find them, contact VeriScan support directly.

Q: Can BLAZE set up the webhook on my behalf?

A: No. The webhook configuration must be completed by the dispensary directly inside VeriScan Cloud. BLAZE does not have access to your VeriScan account and cannot perform this setup for you.

Q: How do I name my webhook endpoint, and does it matter?

A: The endpoint naming convention is completely flexible and does not affect functionality. It is typically named based on the shop's location for easy identification (e.g., "California" or "SoCal"). Choose a name that makes sense for your operational setup.

Q: How many devices can I configure?

A: Each shop receives a VeriScan-allotted number of devices as part of their Veriscan account. Each device must be individually configured with the shop's VeriScan credentials to enable scanning. Contact VeriScan directly for questions about your device allotment.

Q: What is the difference between the production and staging webhook URLs?

A: Use the staging URL when initially setting up and testing the integration to avoid affecting live store data. Switch to the production URL once you have confirmed the integration is working correctly in staging.

FAQ: Queue & Workflow

Q: Why does a scanned customer go to the walk-in queue and not the check-in queue?

A: The Veriscan integration is designed to push scanned customers directly into the walk-in queue. This reflects a walk-in workflow where customers arrive and are scanned at the door before being served. The check-in queue is intended for a different flow and is not triggered by Veriscan scan events.

Q: What customer data is automatically populated when a scan is successful?

A: On a successful scan, the following data is automatically populated in BLAZE: the customer's name, date of birth, and ID details (pulled directly from the scanned document). If the customer already exists in BLAZE, their profile is matched. If they are new, a member record is auto-created with the scanned information.

Q: What happens if the same customer is scanned twice?

A: The system includes retry-blocking logic to prevent duplicate queue events. If the same customer is scanned again within a short window, BLAZE will not create a duplicate queue entry. However, scanning different, unique IDs will successfully produce separate queue entries.

Q: Can the integration be used across multiple locations?

A: Yes. Each location can be configured as a separate endpoint within VeriScan Cloud using a location-based name. Each location's endpoint should utilize the appropriate developer key and terminal ID specific to that site.

FAQ: Troubleshooting

Q: What should I check if a scan is not adding a customer to the queue or creating a member?

A: First, verify that webhooks are enabled in VeriScan Cloud and that the endpoint URL is correctly set to the BLAZE production URL. Confirm the Authorization header is present and the developer key value is strictly correct. Check that the X-Terminal-ID (if used) matches the configured terminal. If everything looks correct, test using the staging URL to isolate whether the issue is with the configuration or the connection.

Q: Why is my webhook not receiving events from VeriScan Cloud?

A: Common causes include: webhooks not being enabled in VeriScan Cloud, an incorrect endpoint URL, a missing or incorrect Authorization header, or the physical device not being configured with the correct VeriScan credentials. Confirm all four items are correct before escalating to support.

Q: What should I check if an order is not being created after a scan?

A: Confirm that the scan is successfully adding the customer to the walk-in queue first. If the queue entry appears but no order is generated, check whether the auto-order creation setting is enabled for the relevant POS configuration in BLAZE. If the queue entry is not appearing at all, refer to the webhook troubleshooting steps above.

Q: How do I verify my Authorization header and developer key are correctly configured?

A: In VeriScan Cloud, open your webhook endpoint settings and confirm the header name is exactly Authorization (case-sensitive) and the value matches the developer key provided by VeriScan. A mismatch in either the header name or value will cause the webhook to be rejected by BLAZE.