Weave Code
Paylands Php Laravel Package
wearemarketing/paylands-php
A PHP SDK for integrating the Paylands payment gateway into Laravel or standalone PHP applications, with helpers for payment requests, tokens, and API interactions.
wearemarketing/paylands-php is a PHP client for integrating the Paylands payment gateway into Laravel and other PHP applications. It provides a clean wrapper around the Paylands API, helping you configure credentials and send payment requests without managing raw HTTP calls.
- Composer-installable PHP package
- Configurable Paylands API credentials
- Create and submit payment requests
- Suitable for Laravel or standalone PHP projects
- Lightweight wrapper for simpler maintenance
Frequently asked questions about Paylands Php
- How do I install wearemarketing/paylands-php in a Laravel application?
- Install the package with Composer using composer require wearemarketing/paylands-php. If the package includes a Laravel service provider, Laravel auto-discovery should register it; otherwise add the provider manually according to the package docs. After installation, publish the package configuration and add your Paylands merchant credentials.
- Does this package support Laravel, and which Laravel versions can I use?
- The package is a PHP client for the Paylands REST API and can be used inside Laravel applications for payment orders, card tokenization, and refunds. The information provided does not list explicit Laravel or PHP version constraints, so check the package composer.json and Packagist metadata before installing. Match those constraints against your application's Laravel and PHP versions.
- How do I configure Paylands merchant credentials with this package?
- Publish the package configuration, typically with php artisan vendor:publish, then set your Paylands merchant credentials in the published config file or environment variables. Keep credentials out of version control and use different values for sandbox and production. Confirm the exact credential keys in the package documentation because Paylands may require multiple merchant identifiers.
- How do I switch between Paylands sandbox and production environments?
- The package provides environment switching through its publishable configuration, so you can point it at Paylands sandbox for testing and production for live payments. Keep separate environment variables or config values for each environment and never reuse sandbox credentials in production. Verify the active environment before creating orders or issuing refunds.
- Can I create Paylands payment orders with this Laravel package?
- Yes, the package is intended for creating payment orders through PaynoPain's Paylands REST API. You typically build an order with amount, currency, customer details, and a card token or payment reference, then send it through the client. Inspect the API response and persist the Paylands order identifier so you can reconcile payments later.
- Does wearemarketing/paylands-php support card tokenization?
- Yes, the package supports tokenizing cards through the Paylands API. Use tokenization so your Laravel application can reference a Paylands token instead of storing raw card numbers. This helps reduce PCI scope, but you should still follow Paylands guidance and avoid logging sensitive card data.
- How do I issue a refund with this Paylands PHP client?
- Use the package's refund method with the original Paylands order or transaction reference and the amount to refund. Test partial and full refunds in the sandbox before using them in production, and store the refund response for reconciliation. Check Paylands API rules for refund windows and whether multiple partial refunds are allowed.
- How should I test a Paylands integration without charging real cards?
- Use Paylands sandbox credentials and test card details provided by Paylands, and switch the package configuration to the sandbox environment. Exercise payment order creation, tokenization, and refunds in sandbox before going live. Keep sandbox and production credentials separate and add automated tests around your application's payment workflow.
- What production concerns should I handle when using this package in Laravel?
- Store Paylands credentials in environment variables or a secrets manager, not in committed config files. Handle API errors and timeouts explicitly, log only non-sensitive identifiers, and reconcile orders and refunds against Paylands records. Since the package handles card tokenization, avoid persisting or logging raw card data in your application.
- Is wearemarketing/paylands-php actively maintained, and what alternatives exist?
- Check the repository and Packagist release history for recent commits, open issues, and compatibility with your Laravel and PHP versions. Alternatives include calling the Paylands REST API directly with Laravel's HTTP client or Guzzle, using an official Paylands SDK if one exists, or evaluating other community Paylands clients. Compare maintenance activity and API coverage before choosing a package for production.
Weaver
How can I help you explore Laravel packages today?