Applying a Coupon at Checkout

Hello,
If we are using some coupons with percent reduction instead of amount, how are we supposed to do this?

Hey Kiuega!

I think (but I have a feeling that I'm missing a key part of your question) that it should be the same. The important fact is that Stripe coupons themselves support "amount" and also "percent". So when you create the coupon inside of Stripe, you can choose to create either type. Then, at checkout, the process is the same: apply the coupon & Stripe will handle the rest. We also do this on SymfonyCasts.

But let me know if I'm missing something :).

Cheers!

In fact the problem was with our application. When using a coupon with a percentage reduction, then the summary table of our order did not display the correct percentage reduction. He did not support the percentage discount coupon. Only the one with a fixed amount. For that we had to re-work the code

<b>OrderController:</b>
$cart->setCouponCode($code, $stripeCoupon->amount_off /100);
become
$cart->setCouponCode($code, $stripeCoupon);

<b>ShoppingCart:</b>
Add this function :

    public function findCouponAmount(?\Stripe\Coupon $stripeCoupon)
    {
        if(!$stripeCoupon)
        {
            return null;
        }

        if($stripeCoupon->amount_off)
        {
            return $stripeCoupon->amount_off / 100;
        }

        if($stripeCoupon->percent_off)
        {
            $total = $this->getTotal();
            $discount = $total * ($stripeCoupon->percent_off / 100);
            return $discount;
        }
    }

(I need to check if the coupon is null, and in which case, return null, because when the order is placed, we call in <b>ShoppingCart </b>the <b>$this->setCouponCode(null, null);</b> function. And since in this function we will now use the <b>findCouponAmount()</b> function, so we might as well manage the case in it)

And now, the <b>setCouponCode </b>function become

    public function setCouponCode($code, $stripeCoupon)
    {

        $this->session->set(
            self::CART_COUPON_CODE_KEY,
            $code
        );

        $this->session->set(
            self::CART_COUPON_VALUE_KEY,
            $this->findCouponAmount($stripeCoupon)
        );
    }

It seems that it works.
On the other hand, is it normal that when I create a permanent coupon, and that I make subscribe a user by using this code, the coupon is validated. But if I get a new subscription for the user, then even without entering the coupon, I see in Stripe that it is used

However if I watch the session, the coupon is null

Jo sorry for that much questions :P

But what if the user uses a coupon and the price in his cart is lower than the coupon's price.

1. Is there a way to prevent this? and only set it up if the actual price is higher than the coupon price?
2. Is there a way to set the coupons price to the value of the left money there if the cart price is lower and let the user reuse the coupon if he wants to use it again ?
3. Can I bind a coupon to a defined user ?

Thanks :)

Blueblazer172 No worries... payment stuff is HARD

And great question. In the most recent API versions in Stripe, your user would be able to checkout for free in this case, but that's it: they would NOT also receive any account balance for the future (in older versions of Stripe's API, they would checkout for free AND be given account credit for the future).

1) It's up to you in your code to ultimately decide whether or not you want the coupon to be "accepted" and applied to the order. So, you could definitely use Stripe's API to check the value of the coupon when the user submits it, compare that to the order, and NOT apply it (and give the user a message).

2) Hmm, I don't think you can allow the user to re-use the rest of the coupon's value later. You CAN edit the customer's account balance (by determining how much of the coupon was unused and then using Stripe's API to add that match to the customer's account balance), but this can be tricky later - your system needs to know to lookup the customer's balance to accurately show the final price of future orders on checkout. It might not be worth it. Another option is to create a "coupon" database table locally on your site. You would then create coupon codes in your system, and these would save in your table (but you would not create them in Stripe, at least at first). Then, on checkout, if the user has applied one of your coupons, use Stripe's API to create the coupon and then apply it immediately. In other words, coupons only exist in your system, until the moment they are applied - then you create + apply them in Stripe all at once. With this setup, you could definitely track how much of a coupon has been used and allow them to re-use the rest later. When they do, you would create a new, smaller coupon in Stripe for the correct value. It's a bit more of a complex setup. So again, it might not be worth it (we actually use this method on KnpU).

3) I'm not sure if I understand. In this chapter, we DO bind the coupon to the Stripe customer ... so we're already doing that. If you're asking whether or not you can create a coupon that can only be redeemed by a user in your database, then totally! In this tutorial, we don't keep a record of the coupons in our database. But, in real-life, you might want to do this - e.g. a coupons table. In this case, I would add a user_id to the coupons table, and when you create a coupon, make sure you associate it with whatever user you want. In a really nice setup, you might have an admin interface in your app for creating coupons. On that interface, perhaps you can select the user in your system who this coupon is for. Then, when you submit, it would create the record in your local coupon table, and also create the Coupon object in stripe. In checkout, you could check to make sure (in your database) that the coupon is being used by the person it is assigned to.

Cheers!