filament-payments
Manage your payments inside FilamentPHP app with multi payment gateway integration
Extends filament
composer require tomatophp/filament-payments- filament-plugin
- payment-gatew
- payment-manager
- payment-page
- payments
- payments-integration
Readme
Filament Payment Manager
Manage your payments inside FilamentPHP app with multi payment gateway integration
Screenshots
Features
- Payments List
- Payment View
- Payment Filter And Groups by Status
- Payment Gates
- Payment Gate Options
- Payment Action
- Payment Facade Method
- Payment Page
- Payment Drivers
- StripeV3 Integration
- Plisio Integration
- Paypal Integration
- Paymob Integration
- Tap Integration
- Myfatoorah Integration
- Creptomus Integration
- Paddle Integration
- Lemon Squeezy Integration
- Binance Integration
- PayTabs Integration
- Moyaser Integration
- Payfort Integration
- Fawery Integration
Compatibility
| Package version | Filament | Laravel | PHP |
|---|---|---|---|
| 5.x | 5.x | 12 / 13 | 8.2+ |
1.x (v3 branch) | 3.x | 10 / 11 | 8.1+ |
Installation
we need the Media Library plugin to be installed and migrated you can use this command to publish the migration
after install your package please run this command
finally register the plugin on /app/Providers/Filament/AdminPanelProvider.php
Using
you can use payment with the very easy way just use Facade FilamentPayments like this
if you want to return it as json you can just make json: true, this method return a URL for you with the payment, you can share this link with anyone to make the payment done.
Use Payment Action
you can use a Table Action to make it easy to link Payment with your table like this
Integrate With Filament Subscription
if you like to use this package with Filament Subscription you can use this code
it will redirect you to payment after the hook is called.
Payment Page Guard
The payment page (/pay/{trx}) requires an authenticated user. Since v5 it uses config('filament-payments.guard'), which defaults to your app's default guard (before v5 it was hard-coded to auth:accounts). To use another guard, or to get the old behaviour back, publish the config and set:
Gateway Secrets
Gateway parameters are stored encrypted with your APP_KEY, and secret parameters are never sent to the browser: in the gateway edit modal they are empty password inputs, and leaving one blank keeps the current value. Each driver declares its secret keys; a custom driver opts in like this:
If you rotate APP_KEY, re-enter your gateway keys.
Publish Assets
you can publish config file by use this command
you can publish views file by use this command
you can publish languages file by use this command
you can publish migrations file by use this command
Other Filament Packages
Checkout our Awesome TomatoPHP