# Verified tracking, payment status and regional review

Source: https://frosvo.com/docs/verified-tracking-and-payment-status
Updated: 2026-11-08

Understand verified customer tracking, safe payment updates, gateway permissions and the difference between a region request and actual data placement.

Use this guide when setting up customer tracking, reviewing a payment request or requesting a different hosting region. These controls protect customer information and keep status messages accurate.

## Before you start

You need access to the relevant workspace and conversation. Owner-only actions, including manual payment adjustments and confirming a bug fix for customer notification, require the workspace owner. Connecting a service does not grant every agent access to every customer's records.

## How does a customer track a request?

1. Enable tracking for the appropriate website and configure its authorized data source.
2. Have the customer sign in through your verified customer-account integration.
3. Ask the customer to enter the exact reference for their order, invoice or service.
4. Display only the record authorized for that customer and website.

Typing an email address is not verification. An anonymous visitor or an unverified chat identity cannot use that address to access another customer's records. If sign-in is unavailable, offer ordinary support instead of promising that an email and reference are sufficient.

An external connector must return an account identity matching the verified customer. Unrelated items are not displayed when a reference does not match. A gateway response must contain the exact requested reference. Missing status information remains unknown rather than being labeled active.

## What does a payment status mean?

A payment link is a request to pay. Opening it does not prove a payment occurred. The widget displays payment requests belonging to the conversation the customer selected, rather than silently selecting a newer conversation.

If creating a request encounters a network failure, retry the same draft. The desk reuses its request identity, and a matching committed request is returned rather than posting another payment message. Reusing that identity with changed payment details is refused; start a new request deliberately if you intend a different offer.

Manual payment adjustments are restricted to the workspace owner. A custom signed merchant callback must identify the exact payment request, explicit status, matching amount and currency, and external payment identity. Incorrect or conflicting callbacks are refused for reconciliation. A refunded request cannot be changed back to paid by a delayed event.

Custom merchant callbacks are separate from a processor-native verified checkout integration. Do not describe an ordinary hosted URL or its iframe as a certified embedded processor checkout. Use the external checkout option until the supported processor integration has been accepted.

## How do gateway permissions work?

The selected scopes define what the gateway may answer. Clearing all scopes grants nothing. Invalid scopes do not restore default permissions. If the endpoint, key or permissions change during a request, stale results are refused; repeat the lookup using the current connection.

Gateway errors use safe categories. Check endpoint configuration and connection status without pasting credentials or customer response payloads into support messages.

## Does requesting a region move my data?

No. The region settings currently record a preference and a request for infrastructure review. Saving a preference or requesting review does not relocate the database, attachments, backups, queues or third-party processing. Immediate migration is unavailable without verified infrastructure and operator acceptance.

Wait for a separately verified deployment and migration process before promising data residency to your own customers. A country or region label alone is not evidence of physical placement.

## What happens when notifying customers about a bug fix?

The owner confirms the bug and its release information, then requests notifications for linked conversations. The reply and notification marker commit together. A failure before that transaction completes leaves the conversation eligible for another attempt; a committed reply is not created again on a repeated request.

The marker records reply creation, not proof that an email arrived in the customer's inbox. Delivery still follows the selected channel's rules and delivery state. Review uncertain external delivery rather than sending the same notification blindly.

## Common problems

- **Sign-in required:** use your verified account integration; entering a different email does not grant access.
- **No matching record:** confirm the exact reference and customer account; do not substitute unrelated account items.
- **Payment event refused:** reconcile identity, amount, currency and current state before resubmitting.
- **Gateway changed:** refresh the connection and retry the read-only lookup.
- **Regional migration unavailable:** submit a review request; no automatic data transfer is performed.

For setup details, see [tracking](/docs/visitor-order-and-service-tracking), [payment requests](/docs/payment-requests-in-chat), [gateway setup](/docs/customer-owned-integration-gateway), [regional review](/docs/regional-data-placement) and [bug-to-fix follow-up](/docs/bug-to-fix-customer-loop).

## Common questions

### Does typing an email address in the chat widget verify a customer's identity for order tracking?

No. Customer tracking requires a verified customer-account session and an exact reference that matches that authenticated account.

### Does saving a region preference immediately relocate my workspace database?

No. Region settings record a residency preference and review request; physical data migration requires verified regional infrastructure and operator execution.
