- What is buckaroo/sdk used for in a Laravel application?
- buckaroo/sdk is a PHP client for Buckaroo payment APIs. It wraps transaction creation, payment method handling, refunds, captures, status queries, and structured API responses. In Laravel it should be treated as a vendor transport library behind an application-owned payment gateway adapter, not as your billing architecture.
- How do I install and configure buckaroo/sdk in Laravel?
- Install it with Composer and supply Buckaroo sandbox or production credentials through environment-backed configuration. The clean Laravel approach is to bind a BuckarooGateway adapter in the container and keep configuration in config/buckaroo.php. Verify the actual package for any published config or Laravel-specific setup before assuming those conveniences exist.
- Which PHP and Laravel versions does buckaroo/sdk support?
- The provided overview does not state exact PHP or Laravel version constraints, so check composer.json and Packagist before planning. Confirm PSR and HTTP-client or Guzzle constraints against your application lockfile. Because the SDK is a PHP client, Laravel compatibility depends heavily on the adapter and dependency versions you choose.
- Does buckaroo/sdk include a Laravel service provider and facade?
- There is a documentation conflict to resolve: package descriptions mention Laravel service provider and facade support, while technical review says there is no service provider, facade, config publishing, or native webhook handling. Verify composer.json and src before relying on those features. Plan the integration as a framework-agnostic SDK with your own container binding and configuration.
- Which payment methods does Buckaroo SDK support?
- The overview lists iDEAL, credit cards, PayPal, and other Buckaroo payment methods. Transaction management covers create, capture, refund, and query operations. For roadmap methods such as SEPA direct debit, Bancontact, Klarna, gift cards, tokenization, or recurring mandates, confirm current support directly in the SDK and Buckaroo documentation.
- Does buckaroo/sdk handle webhooks, signature verification, and idempotency?
- The technical review indicates native webhook handling is not provided and should be treated as integrator responsibility. You should implement signature verification, idempotent event storage, replay protection, and an explicit payment state machine in your Laravel application. Confirm Buckaroo's current webhook documentation and signing requirements before go-live.
- How should I integrate buckaroo/sdk without leaking Buckaroo objects into my domain?
- Define an application-owned PaymentGateway interface and implement a BuckarooGateway adapter around the SDK. Bind the adapter in Laravel's container, keep credentials in config/buckaroo.php, and orchestrate checkout, refunds, and webhooks in application services. Do not pass Buckaroo request or response objects into Eloquent models, controllers, Blade views, or domain events.
- Is buckaroo/sdk production-ready for online payments?
- A sandbox first payment can be feasible in days, but production readiness is the real scope. Budget for webhook verification, idempotent event storage, payment state handling, refunds and partial refunds, currency and minor-unit correctness, reconciliation, logging, timeouts, retries, and contract tests. A realistic plan is one to two sprints for a single-method iDEAL pilot and another sprint for hardening and expansion.
- Does buckaroo/sdk support refunds, partial refunds, captures, and payment status queries?
- The overview states that transaction management includes create, capture, refund, and query payments. Partial refunds, chargebacks, disputes, multi-currency settlement, and detailed refund semantics are not confirmed by the provided context. Verify those flows against Buckaroo's API documentation and sandbox before designing your financial workflows.
- Should I use buckaroo/sdk or a community wrapper or hosted checkout instead?
- The vendor-official SDK has credibility, but the public footprint described is small, with few stars, no dependents, and limited community examples. A hosted checkout can reduce PCI DSS scope compared with direct card capture, while a community wrapper may offer Laravel conveniences but carries maintenance risk. Enforce a gateway abstraction from day one and verify release cadence, support SLA, and method coverage before committing.