@lsvagusa I would (and have in a past project) just have a single CouponService that takes care of both creating the coupons in your database, as well as in Stripe. Reason being, you want them to be in sync. If you have separate services for your model and Stripe, then you’re just going to constantly have to inject that pair of services into every class you wish to interact with coupons.
So, wrap it up into a single service. Your service can then type-hint Stripe’s coupon service in its constructor:
use Stripe\Service\CouponService as StripeCouponService;
class CouponService
{
public function __construct(protected StripeCouponService $stripeCoupons)
{}
}
When you create/update/delete coupons using the service, you can insert/update/delete the record in your database, as well as the corresponding coupon on Stripe:
public function create(CreateCouponParameters $parameters)
{
// Create coupon on Stripe...
$stripeCoupon = $this->stripeCoupons->create(params: [
// Parameters to create Stripe coupon...
]);
// Then create coupon in database...
$coupon = Coupon::query()->create([
'stripe_id' => $stripeCoupon->id,
// Parameters to create coupon Eloquent model...
]);
return $coupon;
}
In tests, you can then mock the StripeCouponService dependency so that you can run your tests without actually hitting Stripe’s API:
public function test_can_create_fixed_amount_coupon(): void
{
$this->mock(StripeCouponService::class, function (MockInterface $mock): void {
$mock->shouldReceive('create')->once()->andReturn(Coupon::constructFrom([
'id' => 'jMT0WJUD',
// And other Stripe coupon parameters you need returning...
]));
});
// Make request to controller action that type-hints your CouponService class...
$this
->post('/coupons', [
// Parameters your create coupon endpoint requires...
])
->assertCreated();
$this->assertDatabaseHas('coupons', [
'stripe_id' => 'jMT0WJUD',
]);
}
