XeroWP
STAMPT Verify — Human Identity, No Puzzles

STAMPT Verify — Human Identity, No Puzzles

0/5 (0 ratings) — active installs Updated Sep 8, 2026
anti-fraudbot protectioncaptcha alternativeIdentity Verificationspam protection
Download v1.0.1 Plugin Website

Stop asking humans to prove they’re human by clicking fire hydrants.

STAMPT Verify replaces CAPTCHAs with real identity verification backed by financial institutions. When a user clicks “Verify with STAMPT,” they securely connect a financial account to prove they’re a real person — once. After that, they’re verified across every site using STAMPT. No puzzles. No friction. No bots.

Why STAMPT Verify?

  • Bots can’t fake it — AI solves CAPTCHAs in milliseconds. No AI can fabricate a real bank connection.
  • Users verify once — One verification works across the entire STAMPT network. Zero repeat friction.
  • Know your users — Each verified user comes with a GEM trust tier so you know their financial profile.
  • Fully accessible — No images to identify, no puzzles to solve. Works for everyone.
  • Age verification built in — Optionally require age verification for alcohol, cannabis, gambling, or any age-restricted content.

Use Cases

  • Login and registration protection
  • Comment spam prevention
  • WooCommerce checkout fraud prevention
  • Age-gated content and products
  • Any form that bots abuse

How It Works

  1. Install the plugin and enter your API key
  2. Choose where to show the verify button (login, registration, checkout, or anywhere via shortcode)
  3. Users click “Verify with STAMPT” connect their identity in 30 seconds done forever

Shortcode

Place the verify button anywhere with [stampt_verify].

External services

This plugin relies on the STAMPT identity verification service, operated by STAMPT Technologies Inc.

Service: STAMPT Verify

  • Service name: STAMPT Verify
  • Service provider: STAMPT Technologies Inc.
  • Service URL: https://stampted.com

What data is transmitted

When a user clicks the “Verify with STAMPT” button, the following occurs:

  1. The plugin loads the STAMPT JavaScript SDK from https://stampted.com/stampt-verify.js. This script renders the verification button and manages the verification popup window.
  2. When the user initiates verification, a popup window opens to https://stampted.com/authorize where the user connects a financial account through a secure third-party banking connection.
  3. Upon successful verification, the following data is returned to your WordPress site:
    • A STAMPT verification token (pseudonymous identifier)
    • A STAMPT ID (e.g., STMPT-I-XXXXXXXX)
    • A GEM trust tier label (e.g., “emerald”)
    • A verification status (true/false)

When data is transmitted

Data is transmitted only when:
* The plugin loads on a page where the verification button is displayed (SDK script load)
* A user actively clicks the “Verify with STAMPT” button and completes the verification process

The plugin does not transmit data in the background, on page load without user interaction, or for analytics/tracking purposes.

Why data is transmitted

Data is transmitted to verify that the user is a real person backed by a real financial institution. This verification replaces traditional CAPTCHA challenges with bank-verified identity confirmation.

Where data is transmitted

  • SDK loaded from: https://stampted.com/stampt-verify.js
  • Verification popup: https://stampted.com/authorize
  • API validation: https://api.stampt.tech/api/sso/userinfo

Data privacy

Your WordPress site never receives the user’s personal financial data. No bank names, account numbers, balances, or transaction data are shared. Your site receives only a pseudonymous verification token, a trust tier label, and a pass/fail verification status.

STAMPT Terms of Service and Privacy Policy