email:send {user} {--Q|queue}

You may assign descriptions to input arguments and options by separating the parameter from the description using a colon:

While your command is executing, you will obviously need to access the values for the arguments and options accepted by your command. To do so, you may use the `argument` and `option` methods:

/**

* Execute the console command.

*

$name = $this->anticipate('What is your name?', ['Taylor', 'Dayle']);

If you need to give the user a predefined set of choices, you may use the `choice` method. The user chooses the index of the answer, but the value of the answer will be returned to you. You may set the default value to be returned if nothing is chosen:

<a name="writing-output"></a>

In addition to providing [authentication](/docs/{{version}}/authentication) services out of the box, Laravel also provides a simple way to organize authorization logic and control access to resources. There are a variety of methods and helpers to assist you in organizing your authorization logic, and we'll cover each of them in this document.

<a name="defining-abilities"></a>

First, add the Cashier package to your `composer.json` file and run the `composer update` command:

Next, register the `Laravel\Cashier\CashierServiceProvider` [service provider](/docs/{{version}}/providers) in your `app` configuration file.

use Laravel\Cashier\Billable;

{

use Billable;

}

Finally, set your Stripe key in your `services.php` configuration file:

'stripe' => [

'secret' => env('STRIPE_API_SECRET'),

],

<a name="creating-subscriptions"></a>

$user = User::find(1);

If you would like to specify additional customer details, you may do so by passing them as the second argument to the `create` method:

'email' => $email, 'description' => 'Our First Customer'

]);

If you would like to apply a coupon when creating the subscription, you may use the `withCoupon` method:

->withCoupon('code')

->create($creditCardToken);

Once a user is subscribed to your application, you may easily check their subscription status using a variety of convenient methods. First, the `subscribed` method returns `true` if the user has an active subscription, even if the subscription is currently within its trial period:

//

}

The `subscribed` method also makes a great candidate for a [route middleware](/docs/{{version}}/middleware), allowing you to filter access to routes and controllers based on the user's subscription status:

public function handle($request, Closure $next)

{

// This user is not a paying customer...

return redirect('billing');

}

If you would like to determine if a user is still within their trial period, you may use the `onTrial` method. This method can be useful for displaying a warning to the user that they are still on their trial period:

//

}

To determine if the user was once an active subscriber, but has cancelled their subscription, you may use the `cancelled` method:

//

}

You may also determine if a user has cancelled their subscription, but are still on their "grace period" until the subscription fully expires. For example, if a user cancels a subscription on March 5th that was originally scheduled to expire on March 10th, the user is on their "grace period" until March 10th. Note that the `subscribed` method still returns `true` during this time.

//

}

$user = App\User::find(1);

<a name="subscription-quantity"></a>

$user = User::find(1);

// Add five to the subscription's current quantity...

// Subtract five to the subscription's current quantity...

Alternatively, you may set a specific quantity using the `updateQuantity` method:

For more information on subscription quantities, consult the [Stripe documentation](https://stripe.com/docs/guides/subscriptions#setting-quantities).

<a name="subscription-taxes"></a>

return 20;

}

To cancel a subscription, simply call the `cancel` method on the user's subscription:

You may determine if a user has cancelled their subscription but are still on their "grace period" using the `onGracePeriod` method:

//

}

<a name="resuming-subscriptions"></a>

If the user cancels a subscription and then resumes that subscription before the subscription has fully expired, they will not be billed immediately. Instead, their subscription will simply be re-activated, and they will be billed on the original billing cycle.

What if a customer's credit card expires? No worries - Cashier includes a Webhook controller that can easily cancel the customer's subscription for you. Just point a route to the controller:

That's it! Failed payments will be captured and handled by the controller. The controller will cancel the customer's subscription when Stripe determines the subscription has failed (normally after three failed payment attempts). Don't forget: you will need to configure the webhook URI in your Stripe control panel settings.

namespace App\Http\Controllers;

class WebhookController extends BaseController

{

<table>

@foreach ($invoices as $invoice)

<tr>

<td><a href="/user/invoice/{{ $invoice->id }}">Download</a></td>

</tr>

@endforeach

<a name="generating-invoice-pdfs"></a>

From within a route or controller, use the `downloadInvoice` method to generate a PDF download of the invoice. This method will automatically generate the proper HTTP response to send the download to the browser:

Route::get('user/invoice/{invoice}', function ($invoiceId) {

- [Extending A Layout](#extending-a-layout)

- [Displaying Data](#displaying-data)

- [Control Structures](#control-structures)

- [Service Injection](#service-injection)

- [Extending Blade](#extending-blade)

{{-- This comment will not be present in the rendered HTML --}}

<a name="service-injection"></a>