Weave Code
Gu Payment Laravel Package
potelo/gu-payment
Laravel package that integrates the Gerencianet (Efí) payment gateway into your application, providing a simple, configurable API for creating charges, issuing boletos, processing credit card payments, and managing payment notifications.
GuPayment é um pacote para o Laravel que fornece uma interface para controlar assinaturas e pagamentos com o iugu.com
Frequently asked questions about Gu Payment
- What is potelo/gu-payment used for in Laravel?
- potelo/gu-payment is a Laravel-oriented adapter for iugu.com subscription billing. It provides an interface to manage subscriptions and payments, create charges, issue boletos, process credit card payments, and handle payment notifications. It fits Laravel monoliths or modular monoliths where iugu is the primary subscription provider. The provided overview and TPM assessment describe iugu, while the blurb mentions Gerencianet (Efí), so confirm the actual gateway before adopting.
- How do I install potelo/gu-payment with Composer?
- Install it with Composer, then publish the package configuration and migrations as directed by the repository. Configure iugu credentials in environment or secret management, and attach any required package trait or model behavior to your application models. Pin the Composer version and commit the lockfile. Validate the supported Laravel and PHP matrix before installing in a production branch.
- Which Laravel and PHP versions does GuPayment support?
- The exact Laravel and PHP version matrix is not specified in the provided context, so inspect the package composer.json, tags, and changelog before relying on it. The TPM assessment flags Laravel and PHP compatibility drift as a real risk. Test against the exact Laravel, PHP, database, queue, and cache versions in use. A sandbox spike and code review are required before committing.
- How do I configure iugu credentials for GuPayment?
- Keep iugu API credentials in environment variables or a secret manager rather than in source code. Publish the package configuration and set the required account or API token values there. Verify whether the package supports multiple iugu accounts or multi-tenancy, because the provided context does not confirm that capability. Review the package code to confirm how credentials are loaded and whether any sensitive values are logged.
- Does GuPayment handle iugu webhooks securely?
- The package exposes webhook handling for payment notifications, but the provided context does not document how iugu webhooks are authenticated, retried, deduplicated, or ordered. You must review the package code and iugu webhook signing or verification expectations before relying on it. Implement idempotent webhook processing and replayable queue handling around the package. Treat webhook authenticity and replay protection as production blockers until verified.
- Can GuPayment manage subscriptions, cancellations, proration, and refunds?
- The package is intended to control subscriptions and payments with iugu, but exact coverage for idempotency, cancellation, proration, refunds, dunning, and payment-method updates is not confirmed in the provided context. Validate each operation against the iugu API and the package methods through a sandbox spike. Build a thin internal adapter around the package so product code depends on subscription operations rather than GuPayment classes. Add tests for duplicate requests, failed payments, and cancellation flows.
- Is potelo/gu-payment safe for production use?
- The TPM assessment rates technical risk as medium-high because the package has low community signal, 78 stars, zero listed dependents, and apparent single-maintainer ownership. The stated last release date, 2026-10-15, is future-dated relative to the current date and should be treated as anomalous metadata until verified against tags and changelog. The MIT license allows forking, but that creates internal ownership. Require a sandbox spike, dependency and security review, code review, and a rollback plan before production use.
- How should I test GuPayment before migrating existing subscriptions?
- Start with a non-production iugu sandbox account and a pinned Composer version. Publish and review migrations and configuration in a branch, map existing customer and subscription identifiers to iugu IDs, and define a backfill and reconciliation process. Run a read-only comparison between the current system and iugu during a pilot, use a feature flag for new subscriptions, and migrate existing subscriptions in batches with replayable webhook processing. Avoid dual-writing subscription state and keep a rollback plan.
- What are alternatives to potelo/gu-payment for iugu in Laravel?
- A direct iugu SDK or API integration behind an internal SubscriptionGateway adapter is the safest alternative when you want fewer package assumptions. If the estate is polyglot, likely to add another gateway, or needs a provider-neutral billing domain, prefer a dedicated billing service or a direct integration rather than an opinionated Laravel package. If the application is Laravel-based and iugu is already chosen, the package can be used behind an internal boundary. Confirm whether the actual target gateway is iugu or Gerencianet (Efí), because the provided context contains conflicting provider names.
- Who maintains GuPayment and what if the package is abandoned?
- The package appears to depend on a single upstream maintainer and has little public evidence of production adoption, with 78 stars and zero listed dependents. Its future-dated release metadata should be verified against tags and changelog before relying on it. The MIT license makes forking possible, but you should plan explicit internal ownership, pin the package, and monitor upstream activity. Maintain a fork with a named owner and security process if the upstream package stalls.
Weaver
How can I help you explore Laravel packages today?