- What is sextanet/laravel-oneclick used for?
- It is a Laravel package for integrating Transbank Oneclick, according to its Composer overview. The package is distributed as sextanet/laravel-oneclick and is intended to fit into Laravel application workflows. Check the repository README for the exact endpoints and flow it exposes before adopting it.
- How do I install sextanet/laravel-oneclick?
- Install it with Composer using composer require sextanet/laravel-oneclick. After that, follow the repository README for any service provider registration, config publishing, or environment variables. Laravel package auto-discovery may handle registration, but verify it for your Laravel version.
- Which Laravel versions does sextanet/laravel-oneclick support?
- The provided context does not list a Laravel version constraint. Check the composer.json on the repository or Packagist for the required PHP and illuminate/support versions. Match those constraints to your application before running composer require.
- How do I configure Transbank Oneclick credentials?
- Configuration details are package-specific and should be confirmed in the README. Typically you will publish the package config and set Transbank Oneclick credentials in your .env file. Avoid committing secrets and use environment-specific values for sandbox and production.
- Can I test sextanet/laravel-oneclick without production credentials?
- Testing depends on whether the package documents a Transbank sandbox or fake mode. Look for test credentials, a sandbox endpoint, or HTTP fakes in the README and test suite. If none are provided, isolate the integration behind an interface so your application tests can mock it.
- Is sextanet/laravel-oneclick for passwordless login or payments?
- The Composer description says Transbank Oneclick, which indicates a payment gateway integration. The blurb about passwordless sign-in conflicts with that metadata, so verify the README before choosing it for authentication. For magic-link login, use a package explicitly built for passwordless auth.
- Is sextanet/laravel-oneclick suitable for production?
- Production suitability depends on the package's maintenance, test coverage, and how it handles Transbank credentials and callbacks. Review the repository's release history, issues, and security posture before deploying. Always test the full Oneclick flow in a sandbox first.
- How do I customize routes, views, or notifications in sextanet/laravel-oneclick?
- The context does not confirm which routes, views, or notifications the package publishes. Check the README for publishable assets and configuration options. If customization points are limited, wrap the package behind your own service classes rather than editing vendor code.
- What are alternatives to sextanet/laravel-oneclick?
- Alternatives include other Laravel packages that wrap Transbank Webpay or Oneclick, or a direct SDK integration maintained by your team. Compare supported Laravel versions, sandbox support, and recent commits. If the package is unmaintained, a thin in-house wrapper may be safer.
- How is sextanet/laravel-oneclick maintained and where do I report issues?
- Use the GitHub repository at github.com/sextanet/laravel-oneclick for issues, releases, and source review. Check commit activity and open issues to judge maintenance. For security concerns, follow the repository's disclosure guidance rather than opening a public issue with sensitive details.