[1.6] KTC-131 Subscriptions with Stripe

[Keysie27]

General:

Management of plans, prices, subscriptions, and items using Stripe. The GraphQL mutations allow creating, updating, and deleting these resources both in Stripe and the database.

Tasks:

• Mutations for creating, updating, and deleting entities.
• Interaction with Stripe.
• Unit tests.
• Optimize the flow by delegating to Stripe using webhooks with Laravel Cashier.
• Database restructuring: create a subscriptions database, a prices table, and a stripe_customers table.
• Manage notifications.
• Handle errors and exceptions (observers).
• Define additional queries and mutations for the frontend.
• Refactor to optimize the mutations.

Requirements:

• Select Plan: Handled by the createSubscription mutation, where companies can select a plan and its associated items (prices).
• Change Plan: Handled by the updateSubscription mutation, allowing users to switch plans and update subscription items.
• Cancel Subscription: Handled by the deleteSubscription mutation, which cancels the subscription in Stripe and updates the database.
• Expiration and Free Trial to Paid Plan: Managed by Stripe's billing cycles. Free trial periods are set using the trial_days parameter in the createSubscription mutation. Stripe automatically transitions the subscription to a paid plan after the trial ends. (Pending, for using webhooks)

Considerations:

• Stripe subscriptions can have multiple plans, and a plan can have multiple prices.
• Stripe customers must be created before making a subscription.
• Each SubscriptionItem in Stripe can only have one price_id.
• Payment intervals, currency, and amounts are managed in prices in Stripe.
• A subscription cannot have prices with different payment intervals in Stripe.
• The frontend can use Stripe.js or Stripe Elements to capture payment details and generate the payment_method_id. This delegates payment handling to Stripe, removing the need for a local payment_methods_id table, and instead using a payment_methods table with the stripe_id.
• Stripe does not allow updating certain attributes like currency and interval for existing prices via the API; these can only be updated through the Stripe dashboard.

[FredPeal]

Do you know if Stripe has validation for not create duplicate records?

[Keysie27]

Each product or price has a different ID in Stripe even if it has the same name and detail. That's why en is linked by the Stripe price_id.

[FredPeal]

We have this functionality in the base model Check this file

[FredPeal]

You can do it different
$price = Kanvas\Subscription\Prices\Models\Price::getById($id, $app);
$plan = $price->plan;

In Laravel , when you use eloquent queries, all relationships are retrieved in the result, in this case plan, and you can access to it with maggic attribute plan

Also our models has default relationships

• user
• company
• app

[Keysie27]

When using companies subscriptions to apps, you can have prices/plans without a relationship with a company and user, because plans/prices belong to apps, companies can subscribe to apps, so you can have plans/prices that companies are not using so not relationship

[FredPeal]

This id, I believe that is move to env, @kaioken can be add this id to the test env

[FredPeal]

@kaioken @Keysie27 What do you think about create a workflow diagram about Subscription, for doc the integration with front, back and stripe

[FredPeal]

Btw, good job 😊😁