# Laravel Spark
Laravel Spark is the perfect starting point for your next big idea. When combined with a Laravel application starter kit like Laravel Jetstream (opens new window) or Laravel Breeze (opens new window), or the frontend of your choice, Spark provides a well-designed billing management panel for your application. Spark, which is built on the power of Laravel Cashier (opens new window), allows your customers to subscribe to monthly or yearly billing plans, manage their payment method, update their subscription plans, and download their receipts all from a self-contained, beautifully designed billing portal.
# Supported Payment Providers
Spark supports two payment providers, and purchasing a Spark license grants you the ability to use either of these payment providers. At this time, it is not possible to implement your own custom payment provider when using Spark. We'll provide a brief overview of each provider below.
Paddle (opens new window) is a robust billing provider that serves as a merchant of record for your application. Paddle removes the burden of tax compliance from your SaaS business by handling the complexity of gathering and paying your VAT for you. In addition, Paddle provides support for accepting payments from your customers via credit card or PayPal, localized pricing, and hosted invoices.
Spark's Paddle support is provided by the underlying Laravel Cashier Paddle (opens new window) library.
Paddle Account Approval
Your Paddle account must be approved by Paddle before you can begin using Spark. To apply for an account, please visit the Paddle website (opens new window). While you are developing your application, you may use the Paddle Sandbox (opens new window).
We have listed some known limitations of using the Paddle payment provider below:
- When a recurring coupon is used while subscribing to a plan, the coupon discount will be applied on every billing cycle. However, if the subscription's quantity or plan changes, Paddle will remove the coupon from the subscription.
- Because Paddle does not allow plan quantity changes during trial periods, the Paddle edition of Spark does not support requiring a credit card up front when beginning a trial. All trial periods are started without a credit card or payment method provided up front during the user's initial registration process.
Stripe (opens new window) is a global leader in payment infrastructure with direct integration with card networks and banks, a fast-improving platform, and battle-tested reliability. In addition, intelligent optimizations help increase revenue across conversion, prevent fraud, and assist with revenue recovery. Finally, Stripe provides a robust sandbox environment for you to test your application's payment system.
Spark's Stripe support is provided by the underlying Laravel Cashier Stripe (opens new window) library.
We have listed some known limitations of using the Stripe payment provider below:
- The Stripe payment provider does not provide a PayPal integration.
# Frequently Asked Questions
# Is it possible to upgrade an application from Spark Classic to Spark?
No. However, we will continue to provide bug fixes and security updates to Spark Classic indefinitely.
# Does Spark support any other payment providers?
No. Spark only supports Stripe and Paddle and it is not possible for developers to customize Spark to accept additional providers. If you need to use another payment provider you should not purchase Laravel Spark.
# Am I required to use Tailwind / Blade / Vue / etc. in order to use Spark?
No. Spark's billing portal is totally isolated from the rest of your Laravel application and includes its own pre-compiled frontend assets. Your own application may be built using the frontend technologies of your choice.
# Why are my customers presented with a payment confirmation screen?
Extra verification is sometimes required in order to confirm and process a payment. When this happens, Paddle or Stripe will present a payment confirmation screen. Payment confirmation screens presented by Paddle, Stripe, or Spark may be tailored to a specific bank or card issuer's payment flow and can include additional card confirmation, a temporary small charge, separate device authentication, or other forms of verification.