Product Decisions This Supports

Brazilian market readiness: Supports CPF/CNPJ and related document validation in Laravel/PHP products, reducing custom validation code for onboarding, registration, checkout, billing, and KYC-lite flows.
Roadmap compliance planning: The 3.12.0 release adds alphanumeric CNPJ validation, which is relevant for products that must prepare for evolving Brazilian CNPJ formats. This can inform roadmap work for tax, invoicing, ERP, and customer-entity data capture.
Build vs. buy: For standard Brazilian document validation, this package is a candidate to buy/use instead of building and maintaining regex and checksum logic in-house. Keep custom logic only where business rules or official specification requirements exceed package behavior.
Feature prioritization: Teams can treat alphanumeric CNPJ support as a low-effort compliance enhancement for existing Laravel forms and APIs, rather than a separate validation project.
Use cases: Customer registration, supplier/vendor onboarding, billing and invoicing forms, marketplace seller verification, internal admin tooling, and API validation for Brazilian legal entities.

When to Consider This Package

Consider adoption when the product is Laravel/PHP-based, serves Brazilian users or companies, and needs reusable validation rules for documents such as CNPJ and CPF.
It is especially relevant if the roadmap includes alphanumeric CNPJ readiness or if current validation relies on brittle custom regex/checksum implementations.
Evaluate it when speed of integration and reduced maintenance matter more than a fully managed identity-verification platform.
Confirm before rollout: Laravel/PHP version compatibility, test coverage for alphanumeric CNPJ, expected validation behavior against official rules, and whether the package fits existing form request/API validation patterns.
Look elsewhere if the requirement is full KYC, sanctions screening, document OCR, address verification, fraud scoring, regulatory reporting, enterprise SLA/support, or non-Laravel/non-PHP architecture. Also avoid relying on it as the sole control for high-risk compliance decisions without independent verification.

To executives: This package helps us ship and maintain Brazilian document validation faster, and the new alphanumeric CNPJ support reduces future compliance rework for onboarding, billing, and entity management. It is a small dependency with a contained integration surface, but it should be treated as one input into compliance, not a complete KYC solution.
To engineering: Adopt the package where standard Laravel validation rules are useful, replace bespoke CNPJ/CPF regex where appropriate, and add tests for alphanumeric CNPJ inputs before relying on the new release. Keep version constraints explicit and verify behavior against official document rules and real form/API edge cases.