Product

Today we are excited to announce that Cashier Stripe has received some long anticipated updates, including support for [Stripe Checkout](https://stripe.com/en-be/payments/checkout) as well as support for [Metered Billing](https://stripe.com/docs/billing/subscriptions/metered-billing) subscription plans. ## Stripe Checkout Stripe Checkout makes it a cinch to implement a way to bill your customers in without writing the billing UI implementation yourself. Simply define the products and prices in your Stripe dashboard and let your customer go through the checkout flow using Stripe's hosted checkout page: ```php $checkout = Auth::user() ->newSubscription('default', 'price_xxx') ->checkout(); return view('your-checkout-view', [ 'checkout' => $checkout, ]); ``` More information about using Stripe Checkout with Cashier can be found in [Cashier's documentation](https://laravel.com/docs/billing#checkout). ## Metered Billing Using Metered Billing, you can invoice customers based on their usage, rather than a fixed recurring amount. For example, an email delivery service might charge customers per 10,000 emails sent by their account. To get started, you simply start a new subscription: ```php $subscription = Auth::user()->newSubscription('default', []) ->meteredPlan('price_metered') ->create($request->paymentMethodId); ``` Then, you may report the customer's account usage via the `reportUsage` method: ```php Auth::user()->subscription('default')->reportUsage(15); ``` More information regarding metered billing can be found in [Cashier's documentation](https://laravel.com/docs/billing#metered-billing).

Forge is used by agencies all over the world to provision servers and deploy sites on behalf of their clients. Currently, when Forge provisions a server, that server's SSH key is added to the SSH keys of the Forge user's connected source control providers. This allows the server to clone any repository that the user has access to. However, sometimes you may wish to only grant the Forge user access to clone a specific repository. This is typically accomplished by adding an SSH key to that repository's "Deploy Keys" on the repository's GitHub, GitLab, or Bitbucket dashboard. Beginning today, you may opt-out of having a server's SSH key added to your source control provider account. Instead, when adding a new site to the server, you may choose to generate a Deploy Key for that application. Once the key has been generated, you can add it to the repository of your choice via your source control provider's dashboard - allowing the server to clone that specific repository. In summary, we're introducing two new security enhancements to Forge: - You may now choose to provision a server **without** adding its SSH key to your connected source control providers. - You may choose to create a **Deploy Key** for newly created sites. Forge will configure SSH to always use that deploy key when cloning or pulling that site's repository. You can learn more about these changes at [https://forge.laravel.com/docs/1.0/servers/ssh.html](https://forge.laravel.com/docs/1.0/servers/ssh.html). If you don’t have a [Forge](https://forge.laravel.com) account, now is a great time to sign up! Forge allows you to painlessly create and manage PHP servers which include MySQL, Redis, Memcached, database backups, and everything else you need to run robust, modern Laravel applications.

In this episode, I discuss recent comments regarding my previous podcast, give a recap of the authentication packages covered in the last podcast, and discuss Laravel Passport and Sanctum with particular focus on SPA authentication.