Weave Code
Asaas Sdk Php Laravel Laravel Package
jetimob/asaas-sdk-php-laravel
Laravel integration for the Asaas payment gateway that wraps the Asaas PHP SDK with package configuration and service bindings, making it easier to manage customers, payments, subscriptions, and related billing operations in Laravel applications.
Sdk para se comunicar com a API da asaas de forma mais simples
Frequently asked questions about Asaas Sdk Php Laravel
- How do I install jetimob/asaas-sdk-php-laravel in a Laravel application?
- Install the package with Composer using composer require jetimob/asaas-sdk-php-laravel. Publish the package configuration if needed for your Laravel version, then set your Asaas API credentials for sandbox or production. The package provides Laravel service bindings so the Asaas client can be resolved from the container instead of wiring HTTP calls manually.
- Which Laravel and PHP versions does this Asaas SDK package support?
- The provided overview does not list exact PHP or Laravel version constraints. Check the package composer.json on GitHub or Packagist before installing, especially if you are upgrading from v1.8.1.0 to v1.9.0.0. Confirm the constraints against your application's Composer lock and CI matrix.
- What can I manage with this Laravel Asaas integration?
- The package wraps the Asaas PHP SDK and is intended for customers, payments, subscriptions, and related billing operations. It adds Laravel configuration and service bindings around the underlying SDK. For maintainable code, treat it as an infrastructure adapter behind your own payment gateway interface rather than calling it directly from controllers or domain models.
- What is externalReference in Asaas, and how should I use it with this package?
- externalReference is best treated as a correlation identifier between your internal records, such as orders, invoices, subscriptions, or tenants, and Asaas entities. v1.9.0.0 adds support for the field, but you should define a tenant-safe reference format before using it widely. Prefer opaque UUIDs or a controlled format such as tenant:entity:id only if Asaas length and character limits allow it. Avoid embedding personal data in the reference.
- Does version 1.9.0.0 support externalReference on all Asaas endpoints?
- The changelog only states that support for the externalReference field was added. It does not confirm which Asaas endpoints or request DTOs expose it. Verify the package source and Asaas documentation for payments, subscriptions, customers, charges, and transfers before relying on it in each flow.
- Does this package validate the externalReference field before sending it to Asaas?
- The overview does not state whether the package validates the field or simply passes it through to Asaas. Inspect the relevant request builders or DTOs in the package source to confirm behavior. In most integrations you should still validate length, allowed characters, tenant isolation, and uniqueness rules in your application before calling Asaas.
- Does Asaas return externalReference in API responses or webhook payloads?
- This must be confirmed against Asaas documentation and tested in the Asaas sandbox. Do not assume the field is echoed in responses or webhook payloads just because the package accepts it in requests. Validate response and webhook behavior before designing reconciliation around externalReference.
- How can I test Asaas payments and externalReference without hitting production?
- Use Asaas sandbox credentials in your Laravel environment and run contract or integration tests against the sandbox. Verify that the package sends externalReference as expected and check whether Asaas returns it in responses or webhooks. Keep production credentials out of test environments and confirm PHP and Laravel version constraints in CI.
- Is upgrading from v1.8.1.0 to v1.9.0.0 backward compatible?
- The release is likely a minor, non-breaking feature addition because it adds externalReference support. Still verify that the package follows semantic versioning and that existing calls without externalReference continue to work. Update in a branch, run your test suite, and compare config and facade signatures before deploying to staging and production.
- Is jetimob/asaas-sdk-php-laravel actively maintained, and what are the alternatives?
- The package has a low integration and maintenance burden for Laravel services already using Asaas, but the release adds a new contributor and a single feature PR, so monitor dependency health. Alternatives include using the underlying Asaas PHP SDK directly, building a small custom HTTP client, or evaluating other community Laravel packages. Whichever option you choose, confirm externalReference support, version constraints, tests, and documentation before committing.
Weaver
How can I help you explore Laravel packages today?