Language, language version, and OS: Irrespective of Python version. Test on 2.7 and 3 on Debian Stretch
Issue description
We create a new subscription with an yearly plan and ensure that the subscription created date matches today's date. However, when we compare the first billing date with today's date + 1 year, it does not match until the time is past 5:00AM GMT. If the same test is run immediately after 5:00AM GMT it passes.
Looks like the first billing date is calculated in a different timezone (GMT - 5) while the created time is based on GMT.
test snippet=============================================================
👋 @anu-kailash, please contact Support referencing this issue and your merchant ID. They will partner with the team that owns our recurring billing API to investigate this behavior.
General information
Issue description
We create a new subscription with an yearly plan and ensure that the subscription created date matches today's date. However, when we compare the first billing date with today's date + 1 year, it does not match until the time is past 5:00AM GMT. If the same test is run immediately after 5:00AM GMT it passes.
Looks like the first billing date is calculated in a different timezone (GMT - 5) while the created time is based on GMT.
test snippet=============================================================
======================================================================
TEST_PLAN used ========================================================
Plan ID yearly Name yearly Description Price £10.00 GBP
Trial Period
Duration 12 months
Billing Details
Billing Cycle Every 12 Month(s) Billing Start Immediately after trial Number of Billing Cycles Never Expires