Jennie Robinson Faber cf59931814 fix(helcim): read dateBilling on subscription CREATE to populate next-billing cache ... Helcim returns next-charge as `dateBilling` on POST /subscriptions, but the two CREATE sites were reading `subscription.nextBillingDate`, leaving `member.nextBillingDate` empty after every signup and free→paid upgrade. The lazy refresh in subscription.get.js (which already accepts both shapes) masked it on next account-page load, so renders eventually populated — but the success response we returned to the client also had `nextBillingDate: undefined`. Mirror the GET-side resolution at both CREATE sites: prefer `dateBilling`, fall back to `nextBillingDate`. Existing Number.isNaN guard unchanged; defensively rejects malformed strings from either field.		2026-04-27 19:44:35 +01:00
..
client	feat(payments): persist helcimCustomerCode + skip getOrCreateCustomer on card-on-file	2026-04-27 19:16:32 +01:00
server	fix(helcim): read dateBilling on subscription CREATE to populate next-billing cache	2026-04-27 19:44:35 +01:00