Laravel Barion Laravel Package

Product Decisions This Supports

• Build vs. buy for payments integration: lovaszcc/laravel-barion is a thin Laravel wrapper around Barion (a Hungarian PSP supporting card payments, Barion Wallet, and escrow-style "Barion QR"/split payments). Adopting it turns a multi-week gateway integration into a config-plus-facade task — a strong buy candidate if Barion is already a committed vendor.
• Market-entry roadmap for CEE/Hungary: Barion is a dominant Hungarian gateway. This package is the cheapest way to answer "can we sell in Hungary?" before committing roadmap capacity. It de-risks a small-market launch experiment.
• v1.0.1 specifically unlocks a platform-upgrade decision: Laravel 13 support means the payment layer no longer blocks a framework upgrade. If your upgrade roadmap is gated on third-party payment packages, this release removes that blocker — worth scheduling the Laravel 13 spike now.
• "Tolerate missing config" is a DX/ops signal: the service provider now boots without a published config file, which improves install ergonomics and reduces first-run failures in CI/ephemeral environments. Good for onboarding velocity; also means silent misconfiguration in production is more possible, so pair with your own startup validation.
• Scope boundaries: it wraps an SDK, it does not own reconciliation, refunds workflows, dunning, tax handling, or PCI scope. Those remain your product's responsibility and must be budgeted separately.
• Risk posture: v1.0.1 is a patch on a v1.0.0 with a single external contributor and low visible adoption. Treat as "viable for a bounded pilot," not "approved for primary revenue path" until you have diligence (maintenance cadence, test coverage, security disclosure process, versioning discipline).

When to Consider This Package

Consider it when:

• Barion is a required or strongly preferred gateway (Hungarian entity, HUF settlement, local wallet/QR acceptance, marketplace escrow needs).
• You are on Laravel 10–13 and want the payments layer to track framework upgrades rather than pin you to an older version.
• You need a fast, reversible pilot: a single market, a bounded checkout flow, clear rollback to a hosted/redirect integration.
• Your team is Laravel-fluent and prefers config-driven packages over hand-rolled SDK glue.
• You can accept community-maintained support and want to keep the integration surface thin enough to fork or vendor-in if needed.

Look elsewhere when:

• You need multi-PSP abstraction (Adyen, Stripe, Mollie) — this package is Barion-specific and will not serve as a portable payments layer; consider a gateway-agnostic abstraction instead.
• You require enterprise support SLAs, audit artifacts, or a vendor security questionnaire — a single-maintainer package rarely satisfies procurement.
• Your revenue path is high-volume or regulated (strong customer authentication edge cases, subscriptions, chargebacks at scale) and you cannot absorb the maintenance of a thinly-adopted dependency.
• You are not on Laravel — the value proposition is largely the service provider, config publishing, and facade ergonomics.
• Barion is not contractually chosen yet: run a vendor bake-off first, since lock-in cost here is mostly in the PSP, not the wrapper.

Adoption guardrails: pin the version, add an integration test against Barion's sandbox, wrap the package behind your own PaymentGateway interface so it can be swapped, and monitor upstream release cadence for 2–3 cycles before promoting to primary checkout.

How to Pitch It (Stakeholders)

To executives (one paragraph): Barion is the practical way to accept payments in Hungary. This package is a small, free adapter that lets our Laravel platform talk to Barion with minimal engineering effort — roughly days instead of weeks — and it now supports Laravel 13, so it won't hold back our framework upgrade. It's low-cost and low-commitment: we recommend a bounded pilot in the Hungarian market behind our own abstraction layer, with a 2–3 release observation window before it touches primary revenue flow. Main caveat: it's community-maintained by a very small team, so we retain a fork-and-own fallback and keep the integration thin.

To engineering: v1.0.1 adds Laravel 13 compatibility and a service provider that boots without a published config — install friction is low. Two asks before we merge: (1) isolate all package calls behind our own gateway interface so a swap is a one-file change; (2) add a startup config assertion, because "tolerate missing config" trades install friendliness for silent misconfiguration risk in production. Add sandbox integration coverage for pay/refund/callback and pin the version with a scheduled review against upstream releases.

To finance/legal: settlement currency is HUF via Barion; confirm entity and contract are in place before pilot, and confirm escrow/wallet flows meet your marketplace obligations. Package choice does not change PCI scope — card data never touches our servers in redirect flows.