Weave Code
Laravel Pagseguro Laravel Package
artistas/laravel-pagseguro
Laravel package for integrating the PagSeguro payment gateway. It provides a simple API for creating checkout requests, querying transactions, handling payment notifications, and configuring sandbox or production credentials, making PagSeguro payments easier to add to Laravel applications.
Checkout Transparente e Pagamentos Recorrentes (Assinaturas)
Frequently asked questions about Laravel Pagseguro
- How do I install artistas/laravel-pagseguro in a Laravel app?
- Install it with Composer using composer require artistas/laravel-pagseguro. Laravel auto-discovers the service provider, and you normally publish the package config with php artisan vendor:publish before setting credentials. Because the last release is from March 2021, verify that its illuminate, PHP, and Guzzle constraints resolve against your application before committing to it.
- Does this package support Laravel 10, Laravel 11, and PHP 8.2+?
- Do not assume so. The package’s last release was March 2021, so its illuminate, PHP, and Guzzle constraints likely reflect Laravel 8-era versions rather than Laravel 10 or 11 on PHP 8.2+. Run Composer resolution first; expect to fork and relax constraints if the package is otherwise acceptable.
- How do I configure sandbox and production PagSeguro credentials?
- Publish the package config file and set the sandbox or production mode plus the merchant credentials or tokens required by the integration. Keep those values in environment variables rather than committed config, and confirm that the selected mode points at the correct PagSeguro or PagBank endpoints. A config-first check with a harmless query or sandbox checkout is the safest validation.
- How do I create a transparent checkout payment with this package?
- Use the package’s exposed checkout API to submit the cart items, payer data, payment method, reference, and any required card tokenization details to PagSeguro. The package is a thin wrapper over the upstream HTTP API, so the returned checkout code or payment status drives your application flow. Wrap the call in your own payment service so domain code does not depend directly on this package.
- Does artistas/laravel-pagseguro support recurring payments and subscriptions?
- The package is intended for checkout transparente and recurring payments, and it targets PagSeguro’s pre-approval and subscription-style APIs. You still need to confirm that your PagBank merchant account has legacy recurring API entitlement and a usable sunset runway. Also verify which payment methods are covered, since a 2021 build may not include newer Pix flows.
- How should I handle PagSeguro payment notifications with this package?
- Expose a notification endpoint, receive PagSeguro’s notification code, and query the transaction or subscription before changing order state. Treat notifications as untrusted until verified, process them idempotently, and queue slow work so webhook latency stays within your SLOs. Log notification codes and responses for reconciliation and incident review.
- Can I test this PagSeguro integration without real charges?
- Use PagSeguro’s sandbox environment and sandbox credentials to exercise checkout and notification flows without real charges. In automated tests, mock the package’s HTTP boundary or place it behind your own gateway interface rather than calling PagSeguro from unit tests. Include failure cases such as declined payments, duplicate notifications, and timeout responses.
- Is artistas/laravel-pagseguro still maintained and compatible with PagBank’s new API?
- The package has a March 2021 last release, a small maintainer surface, and no evident security patch cadence, so treat it as code you would own. PagSeguro has been folded into PagBank, and legacy transparent checkout and recurring APIs have been superseded by newer Orders and Checkout APIs on a deprecation timeline. Confirm your merchant account’s legacy entitlement and contractual sunset date before relying on it.
- What alternatives should I consider to this Laravel PagSeguro package?
- The realistic alternatives are adopting it as-is for a time-boxed pilot, forking it into your organization, or replacing it with a maintained official PagBank SDK or direct Orders API integration. Whichever route you choose, put the vendor behind your own PaymentGateway interface so you can swap providers without changing domain code. Multi-gateway abstraction is worth considering if failover or negotiating leverage matters.
- Does transparent checkout with this package affect PCI DSS compliance?
- Yes, transparent checkout puts card data flow inside your PCI scope, and this package reduces integration effort but not compliance obligations. Review whether card data touches your servers, how tokenization is handled, and whether hosted fields or redirect flows would shrink scope. Document the data flow and confirm requirements with your security or compliance owner before production use.
Weaver
How can I help you explore Laravel packages today?