Weave Code
Payline Sdk Laravel Package
monext/payline-sdk
A PHP SDK for integrating Monext Payline payment services into your application. It provides client classes and helpers for calling Payline web services, managing payment transactions, and connecting PHP projects to the Payline API.
Payline library for PHP
Frequently asked questions about Payline Sdk
- Does monext/payline-sdk support Laravel 10, 11, and 12?
- Yes, indirectly. The SDK is framework-agnostic PHP, so it can be installed alongside Laravel 10, 11, or 12 on PHP 8.1+, but it does not ship Laravel-specific version constraints. Confirm the package's declared PHP constraint in Composer before upgrading, and pin a version in composer.json. Laravel itself is not a dependency of the SDK.
- How do I install and configure monext/payline-sdk in a Laravel application?
- Run composer require monext/payline-sdk and create a config/payline.php file that reads the merchant ID, access key, contract number, and environment from environment variables. Keep secrets in Vault or AWS Secrets Manager rather than committing them to .env files in production images. Then bind a Payline client instance through a service provider in your app.
- Is monext/payline-sdk a Laravel package with a service provider and facade?
- No. monext/payline-sdk is a vendor-authored PHP client, not a Laravel package, so it has no service provider, facade, config file, or migrations. You add the service provider and config yourself. That leaves the integration shape up to you, which is why wrapping it in your own PaymentGateway contract is recommended.
- What PHP version and extensions does the Payline SDK require?
- The SDK requires PHP 7.4 or 8.0+ depending on the release, and Laravel 10/11/12 projects should target PHP 8.1 or later. Historically Payline PHP SDKs rely on ext-curl, ext-json, and sometimes ext-soap, so verify your container image includes them before estimating. A missing SOAP extension is a common container-build blocker.
- How do I switch the Payline SDK between sandbox and production environments?
- The SDK exposes sandbox and production endpoints, and you should drive the selected environment from an environment variable rather than hard-coding it. Keep separate merchant credentials and contract numbers for homologation and production. Sandbox behavior can differ from production in test-card handling, 3DS simulation, and contract scoping, so test each flow explicitly.
- How do I integrate the Payline SDK without leaking Payline objects into my Laravel domain?
- Create an internal PaymentGateway interface with methods such as authorize, capture, refund, and status, and implement it in a PaylineGateway class that wraps the SDK. Keep Payline objects such as Payment, Transaction, Order, and wallet tokens inside that adapter, and emit your own domain events like PaymentAuthorized or PaymentFailed. That keeps controllers, models, and domain events PSP-agnostic and makes a future PSP swap cheaper.
- Can monext/payline-sdk authorize, capture, refund, and cancel payments?
- Yes. The SDK covers authorize, capture, refund, and cancel transactions, along with transaction queries by token or ID. It also supports creating, updating, and reusing stored cards and wallets. Check that the payment methods you need, such as cards, SEPA, wallets, or recurring, are actually covered before committing.
- How do I test Payline payments in Laravel without hitting the production API?
- Use the Payline homologation environment with sandbox credentials and dedicated test cards, and never point automated tests at production. Because the SDK is a transport client, you can also mock your own PaymentGateway interface in feature tests and reserve sandbox calls for integration tests. Expect sandbox 3DS simulation and test-card behavior to differ from production.
- Is monext/payline-sdk safe for production if it has zero GitHub stars and dependents?
- Zero GitHub stars and dependents looks alarming but is a poor proxy for PHP adoption, since vendor SDKs are often mirrored from internal repositories and Composer install counts are not shown. Treat adoption as unknown rather than unproven, and expect to be an early integrator with occasional rough edges. Check the last commit date, release cadence, and Monext commercial support SLA tied to your merchant contract.
- What PCI compliance scope applies when using Payline in a Laravel application?
- Hosted payment page or embedded widget integrations typically keep you in SAQ A-EP, while direct-API card capture pushes you toward SAQ D-EP with broader audit, logging-redaction, and key-management obligations. Settle the integration mode with the business before writing code, because it drives PCI scope and timeline more than any SDK detail. Stored Payline card tokens also do not migrate across PSPs, so switching later means re-tokenizing cards.
Weaver
How can I help you explore Laravel packages today?