---
url: https://bajoski34.github.io/Laravel/guide/admin.md
---
# Admin page and components
## The admin page
One line gives your team a page for balances, transactions, refunds, settlements, beneficiaries, chargebacks and FX:
```php
// routes/web.php
Route::middleware(['web', 'auth'])->group(function () {
Route::flutterwaveAdmin(); // /flutterwave
// Route::flutterwaveAdmin('billing'); // or another prefix
});
```
The page refunds customers and moves money, so it must sit inside your own authenticated group. Every page and action also checks the `flutterwave.manage` ability, which you define:
```php
// AppServiceProvider::boot()
Gate::define('flutterwave.manage', fn (User $user) => $user->is_admin);
```
To use the endpoints behind the components without the page itself, pass `false`: `Route::flutterwaveAdmin('flutterwave', false)`.
Publish the views to change the layout: `php artisan vendor:publish --tag=flutterwave-views`.
## Blade components
Every piece of the admin page is also a component you can drop into your own views. They share Flutterwave's look and need no build step.
| Component | Use |
| --- | --- |
| `` | A pay button that opens the inline checkout |
| `` | Bank details for a dynamic [virtual account](/guide/virtual-accounts), with a copy button and countdown |
| `` | A searchable bank dropdown (cached for a day) |
| `` | Filterable transactions with refund and resend-webhook actions |
| `` | Refund history |
| `` | Settlements and what was deducted |
| `` | Saved transfer recipients |
| `` | Disputes with accept and decline forms |
| `` | Quote and trade currencies |
The list components take the matching service's `panel()` data, built from the request's query string so filters and paging work:
```blade
```
Actions post to the routes from `Route::flutterwaveAdmin()`. Without those routes, lists are read-only.
The same components exist for [Inertia apps](/guide/inertia) in React, Vue and Svelte.