TrustComponent
Laravel
TrustCaptcha · Bot protection

Laravel CAPTCHA Integration

Add a Laravel CAPTCHA to a controller, or more cleanly to a custom Form Request validation rule, in a few lines of PHP. It stops bot spam on logins, sign-ups and contact forms and leaves @csrf and your existing validation pipeline as they are. EU-hosted, GDPR-compliant, no image puzzles.

Quickstart

How the integration works

1. Create a CAPTCHA

Create a user account or log in with an existing one. Then create a new CAPTCHA or pick an existing one. If you want to try TrustCaptcha first, every plan comes with a 14-day free trial.

The CAPTCHA overview page shows your site key and license key, and you create your API key there. Add your website’s domains to the authorized domains in the CAPTCHA security rules so they can use your CAPTCHA.

Start of the CAPTCHA creation form.
CAPTCHA security rules of a demo CAPTCHA.

2. Add the CAPTCHA widget to your Blade template

Drop the TrustCaptcha widget into the Blade template that renders your form. The widget runs the CAPTCHA in the background and adds a hidden tc-verification-token field on submit, which arrives on $request like any other input.

resources/views/contact.blade.php
HTML
<script type="module" src="https://cdn.trustcomponent.com/trustcaptcha/3.0.x/trustcaptcha.esm.min.js"></script>

<form method="POST" action="{{ route('contact.submit') }}">
    @csrf
    <input type="email" name="email" required>
    <trustcaptcha-component sitekey="<your_site_key>"></trustcaptcha-component>
    <button type="submit">Send</button>
</form>

The CAPTCHA widget will then be displayed inside your form:

CAPTCHA start

Need detailed information about the CAPTCHA widget integration?
Our documentation has the full widget reference, including themes, languages and custom design.

Read the documentation

3. Validate the token in your Laravel controller

In your Laravel controller, take the verification token from $request, look up the result via our PHP library, and decide whether to accept the request.

First, install our TrustCaptcha PHP library:

Install
bash
composer require trustcomponent/trustcaptcha-php:^3.0

Then validate the token inside your controller and act on the result:

ContactController.php
PHP
use Illuminate\Http\Request;
use TrustComponent\TrustCaptcha\TrustCaptcha;

public function submit(Request $request)
{
    $token = $request->input('tc-verification-token');

    try {
        $trustCaptcha = new TrustCaptcha('<your_api_key>');
        $result = $trustCaptcha->getVerificationResult($token);
    } catch (\Throwable $e) {
        return back()->withErrors(['captcha' => 'CAPTCHA verification failed.']);
    }

    if (!$result->verificationPassed || $result->score > 0.5) {
        return back()->withErrors(['captcha' => 'CAPTCHA verification failed.']);
    }

    // CAPTCHA passed — process the request
    return back()->with('status', 'Thanks!');
}

Need detailed information about the Laravel CAPTCHA integration?
For full step-by-step instructions, including a reusable Form Request rule for projects with several protected endpoints, please read our documentation.

Read the documentation

Other backend framework instead of Laravel?
If you use a different framework, pick the matching recipe here. If your framework isn’t listed, your software developers can integrate the verification themselves using our documentation or ask our support team for a pre-built integration.

Actix Web
ASP.NET Core
Axum
Django
Echo
Express
FastAPI
Fastify
Fiber
Flask
Gin
Hapi
Laravel
Micronaut
NestJS
Next.js
Quarkus
Ruby on Rails
Sinatra
Spring Boot
Symfony

4. Test your integration

TrustCaptcha is now active. Send a test request and check that it goes through.

CAPTCHA done

Switching from reCAPTCHA in Laravel

If your Laravel app runs reCAPTCHA today, the switch touches the same two places as the steps above: the Blade template and the code that checks the token. In the template, remove the reCAPTCHA script and widget and add <trustcaptcha-component> in their place. Your controller or validation rule then reads tc-verification-token instead of g-recaptcha-response, and calls getVerificationResult() from our PHP library where it used to call Google’s verification endpoint. Mind the score direction: in reCAPTCHA v3, a reCAPTCHA score of 1.0 means likely human, while the TrustCaptcha bot score uses 0 for a likely human, which is why the controller above rejects anything over 0.5. Keep @csrf as it is; the full checklist is in our reCAPTCHA migration guide.

FAQs

Where does the Laravel CAPTCHA verification go?
Inside the controller method that receives the form submission, before saving any model or sending mail. The CAPTCHA token comes in as a regular request input; read it with $request->input('tc-verification-token').
Can I keep my Laravel reCAPTCHA package and its validation rule?
No. Laravel reCAPTCHA packages such as biscolab/laravel-recaptcha send the token to Google's verification endpoint, so they cannot check a TrustCaptcha token. Remove the package together with its rule and config entries, and validate tc-verification-token with our PHP library instead, for example in the custom Form Request rule described in the next question.
Can I plug the CAPTCHA check into Form Request validation?
Yes, and it's the cleanest pattern. Build a custom rule (php artisan make:rule TrustCaptchaToken) that calls our PHP library inside its validate() method, then add it to your Form Request's rules() array. The verification then runs as part of $request->validated() like any other rule.
Does TrustCaptcha replace Laravel's @csrf protection?
No. CSRF and TrustCaptcha are independent layers, and both should stay enabled. Keep @csrf in your Blade form and the VerifyCsrfToken middleware in your kernel. The CAPTCHA token only confirms that a human submitted the form.
Where should I store the CAPTCHA API key?
Add TRUSTCAPTCHA_API_KEY to your .env file and expose it through config/services.php under 'trustcaptcha.api_key'. Read it with config('services.trustcaptcha.api_key') and never commit the raw key to your repo.
Why does the field name contain a dash (tc-verification-token)?
It's the default field name the widget posts. Laravel's $request->input() and validation rules accept dashed input keys without a problem. If you'd rather use camelCase, set token-field-name="trustcaptchaToken" on the widget and adapt the controller / rule accordingly.
Losing leads to CAPTCHAs?

TrustCaptcha blocks spam and bots, not customers. No puzzles, GDPR-compliant, EU-hosted.

CAPTCHA start
CAPTCHA done
No puzzles for visitors
The check runs in the background while visitors type, so more people finish your forms instead of giving up.
GDPR-compliant
Hosted in the EU, no cookies, encrypted transmission and automatic data deletion. Every customer gets a Data Processing Agreement.
Multi-layer security
Adaptive proof-of-work and risk scoring stop abuse early, even when attack traffic spikes.
Full control
Set the sensitivity, keep allow and block lists and use geoblocking. You decide how strict the check is.

Protect your Laravel application with TrustCaptcha in just a few steps!

  • EU-hosted & GDPR-compliant
  • No puzzles
  • Try free for 14 days