3neti/voucher

Digital voucher module for issuance, redemption, and lifecycle management

v1.0.0-beta.1 2026-07-31 08:07 UTC

Requires

• php: ^8.3
• 3neti/cash: ^1.3
• 3neti/contact: ^1.2
• 3neti/emi-core: ^2.0@beta
• 3neti/laravel-model-input: ^1.2
• 3neti/laravel-vouchers: ^1.2
• 3neti/settlement-envelope: ^1.2
• 3neti/wallet: ^2.0@beta
• brick/money: ^0.10.1
• lorisleiva/laravel-actions: ^2.9
• propaganistas/laravel-phone: ^6.0
• spatie/laravel-medialibrary: ^11.17
• spatie/laravel-model-status: ^1.18
• spatie/laravel-tags: ^4.10

Requires (Dev)

• laravel/pint: ^1.0
• orchestra/testbench: ^10.3 || ^11.0
• pestphp/pest: ^3.8 || ^4.0
• pestphp/pest-plugin-laravel: ^3.2 || ^4.0

Suggests

• 3neti/report-registry: Required for built-in voucher report resolvers and YAML report drivers

proprietary

• Lester Hurtado

• payments
• laravel
• wallet
• voucher
• redemption
• issuance

Published on Packagist.org on 2026-07-31 08:10 UTC

README

3neti/voucher defines the Pay Code instruction, issuance, claim, execution, and redemption domain used by x-change.

Capabilities

• Typed cash, input, validation, feedback, Rider, claim, and execution instructions
• Redeemable, payable, and settlement voucher policies
• Partial, divisible, and terminal redemption lifecycles
• Driver-composed execution through stored-value and settlement-envelope contracts
• Explicit onboarding and claim-outcome instructions
• Sanitized operational summaries and immutable instruction hydration

The package owns voucher-domain behavior. Provider calls, Cockpit screens, commercial pricing, and host authentication remain outside this package.

Installation

composer require 3neti/voucher

Laravel discovers VoucherServiceProvider automatically. Consuming packages must publish or run their own installation workflow for migrations and host UI.

Compatibility

• PHP 8.3 or newer
• Laravel 12 or 13
• EMI Core 2.0 beta or a compatible 2.x release
• Wallet 2.0 beta or a compatible 2.x release

Verification

composer test
composer pint -- --test
composer validate --strict
composer audit

Security Boundary

Voucher instructions describe authorized behavior; they do not prove provider settlement, authorize arbitrary account credit, or substitute for execution driver policy. Raw provider evidence and credentials must never be embedded in voucher metadata or public summaries.

License

Proprietary.