Closed Benoit1980 closed 4 years ago
Please resubmit this with a filled out issue template.
I am not understanding
"php": "^7.3",
"ext-dom": "*",
"laravel/cashier-paddle": "^1.2",
"laravel/framework": "^8.6.0",
Database client version: libmysql - 5.6.43
When a subscription is created in Paddle with a billing interval of 1 month, the ends_at column is filled with the right date. When a subscription is created in Paddle with a billing interval of 3 months, the ends_at column shows as NULL.
Paddle example of a 3 months subscription.
Create in Paddle: A 1-month SUBSCRIPTION billing interval. A 3-months SUBSCRIPTION billing interval.
Pass the transaction and wait for the webhook from Paddle to update the database columns to see the issue with the ends_at column.
Please open a new issue with the issue template and don't copy paste your composer.json file. Use the versions from your composer.lock file
I have created in Paddle 2 subscriptions. 1 set with a 1-month billing interval. 1 set with a 3 months billing interval.
When the transactions happen, the webhook call back from Paddle is sent correctly to the Paddle Laravel callback URL on my website. The "next_bill_date" in the json response shows with the first subscription a 1-month billing interval while with the other subscription a 3 months billing interval, all good.
The problem happens in the database table called "subscriptions".
On a 1 month subscription, the "ends_at" column is filled in with the correct 1-month billing interval. On a 3 months subscription, the "ends_at" column stays as null.
I have repeated the process again and again with no luck.
Thank you.