PHPackages marqant-lab/marqant-pay - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Payment Processing](/categories/payments) 4. / 5. marqant-lab/marqant-pay ActivePackage[Payment Processing](/categories/payments) marqant-lab/marqant-pay ======================= A flexible payment provider implementation by Marqant. v0.1.1(5y ago)53662MITPHPPHP ^7.4CI failing Since Apr 27Pushed 5y agoCompare [ Source](https://github.com/marqant-lab/marqant-pay)[ Packagist](https://packagist.org/packages/marqant-lab/marqant-pay)[ RSS](/packages/marqant-lab-marqant-pay/feed)WikiDiscussions master Synced 2d ago READMEChangelogDependencies (6)Versions (48)Used By (2) Marquant Pay ============ [](#marquant-pay) This project aims to make it as easy as possible to implement a payment providers into large projects. Inspired by the `laravel/cashier` package, which is limited to stripe at the moment, we try to bring in more flexibility into the topic by allowing multiple payment providers to coexist. Installation ------------ [](#installation) Require the package through composer. ``` compsoer require marqant-lab/marqant-pay ``` Create the migrations for at least one billable model. ``` php artisan marqant-pay:migrations App\\User # or php artisan marqant-pay:migrations "App\User" ``` Providers --------- [](#providers) For each payment provider that you want to connect to, you will first have to pull in a payment gateway through composer. For example here we pull in the stripe gateway. Make sure to checkout the documentation of the provider package you want to pull in. ``` composer require marqant-lab/marqant-pay-stripe ``` Then you will have to add it to the `marqant-pay.php` config file. Create it if it doesn't exist yet. ``` return [ /* |-------------------------------------------------------------------------- | Gateways |-------------------------------------------------------------------------- | | In this section you can define all payment gateways that you need for | your project. | */ 'gateways' => [ 'stripe' => \Marqant\MarqantPayStripe\StripePaymentGateway::class, ], ]; ``` Next you will have to create an entry for it in the database. To do so you can call the following command. ``` php artisan marqant-pay:providers:update ``` If you also want to remove the providers that are no longer listed in your configuration, then you can add the `--delete` flag to the command. ``` php artisan marqant-pay:providers:update --delete ``` Billables --------- [](#billables) A billable in the context of this package is every model that is prepared to be used as customer - because customers are billable 😉 The setup consists of the database table columns needed to store provider related data and the usage of the `Billable ` trait on the billable model. To create the needed migrations run the following command but replace the `User` model if you want another model to be used as customer, eg. a `Company` model. ``` php artisan marqant-pay:migrations App\\User # or php artisan marqant-pay:migrations "App\User" ``` Then you can just run the migrations as usual to apply the migrations. ``` php artisan migrate ``` **Note that you might need to do the same for the payment gateway package that you pull in, so make sure to checkout the documentation of it.** Plans & Subscriptions ------------------------- [](#plans--subscriptions) Check out the [marqant-lab/marqant-pay-subscriptions](https://github.com/marqant-lab/marqant-pay-subscriptions) package on how to pull in subscriptions functionality into your project. Tests ----- [](#tests) To run tests, you first need to set up a sqlite database that we use to get snapshots of the database state. Run the following command from within your project root to create the sqlite database. ``` touch database/database.sqlite ``` Next you will have to add the tests of this package to the phpunit test suite in the `phpunit.xml` file in the root of your Laravel project. ``` ... ./vendor/marqant-lab/marqant-pay/tests ``` Then you should be able to just run your tests with the following commands. ``` phpunit # or ./vendor/bin/phpunit ``` If you want to just run a specific test or a method on a test, then you can filter them out like shown below. ``` phpunit --filter= ``` If you need to perserve a snapshot of what is going on in the test database, then you can comment out the following line in your `phpunit.xml` file. ``` ``` With this line commented out, Laravel will use the `database/database.sqlite` file to store values. Development ----------- [](#development) TODO: Explain setup of development environment. TODO: Add section for creating new payment providers. ### Extending the MarqantPayService [](#extending-the-marqantpayservice) To extend the `MarqantPayService` class, which is what you use behind the scenes when using the MarqantPay facade , you can create a Macro and attach it in the service provider of your package though the `mixin` method provided by the Macroable trait. - [See API Documentation](https://laravel.com/api/7.x/Illuminate/Support/Traits/Macroable.html) **Note** that you have to take care of your extensions, so only one macro of a kind is required. For example if two extensions would provide the macro for `MarqantPayService::subscribe` method, only one of those would be registered. ### Health Score 29 — LowBetter than 60% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity16 Limited adoption so far Community10 Small or concentrated contributor base Maturity59 Maturing project, gaining track record Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~10 days Recently: every ~67 days Total 30 Last Release 1908d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/13aba1f5a025bc1217e8a41a21ca1db8e20e45373882a4e9e8c2f366bfcfe9c4?d=identicon)[marqant-lab](/maintainers/marqant-lab) --- Top Contributors [![tjventurini](https://avatars.githubusercontent.com/u/4708070?v=4)](https://github.com/tjventurini "tjventurini (9 commits)") ### Code Quality TestsPHPUnit ### Embed Badge ![Health badge](/badges/marqant-lab-marqant-pay/health.svg) ``` [![Health](https://phpackages.com/badges/marqant-lab-marqant-pay/health.svg)](https://phpackages.com/packages/marqant-lab-marqant-pay) ``` ### Alternatives [mollie/laravel-cashier-mollie Laravel Cashier provides an expressive, fluent interface to Mollie's subscription billing services. 172155.4k1](/packages/mollie-laravel-cashier-mollie)[musahmusah/laravel-multipayment-gateways A Laravel Package that makes implementation of multiple payment Gateways endpoints and webhooks seamless 852.2k1](/packages/musahmusah-laravel-multipayment-gateways) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)