@adonis-agora/payments 0.9.0 → 0.11.0

package/CHANGELOG.md

@@ -1,5 +1,59 @@
 # @adonis-agora/payments
 
+## 0.11.0
+
+### Minor Changes
+
+- [#36](https://github.com/DavideCarvalho/adonis-agora-payments/pull/36) [`1bcff3b`](https://github.com/DavideCarvalho/adonis-agora-payments/commit/1bcff3bc62edbbdf4a8e972782dca407d92fe278) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - `payments:sync --subscriptions` — backfill and drift-correct subscription price, cycle and status.
+  
+  A subscription's price only reaches the store when a `subscription.created`/`updated` delivery
+  carries it. Every subscription created before that shipped therefore has no `amount`/`cycle` on
+  its row, and recurring-revenue maths skips it until the gateway happens to send an update —
+  which for a healthy subscription nobody edits is never.
+  
+  This is the backfill. Afterwards it is the drift correction: an amount changed in the gateway's
+  own dashboard produces no webhook on some gateways, and a reconcile is the only thing that
+  would notice.
+  
+  Two kinds of row are skipped, for opposite reasons. **Managed** ones: the library owns that
+  recurrence, the gateway has never heard of it, and "correcting" it from a gateway answer would
+  overwrite the only authority there is. **Rows with no gateway id**: a free plan or an admin
+  courtesy, with nothing to ask about.
+  
+  A subscription the gateway does not recognise is reported and left alone — never cancelled. A
+  rotated API key and a wrong environment both produce exactly that answer, and cancelling in bulk
+  from it would be worse than the problem this command solves.
+  
+  The reconcile is exported as `reconcileSubscriptions(manager, store, { provider, log })`, so it
+  can be driven from a job or a test without an ace kernel.
+
+## 0.10.0
+
+### Minor Changes
+
+- [#34](https://github.com/DavideCarvalho/adonis-agora-payments/pull/34) [`920ec01`](https://github.com/DavideCarvalho/adonis-agora-payments/commit/920ec017e7339fc59c4f8be0349144b6332a8449) Thanks [@DavideCarvalho](https://github.com/DavideCarvalho)! - MRR counts gateway-owned subscriptions too, not just the library-managed ones.
+  
+  The previous release scoped recurring revenue to managed subscriptions, arguing that a
+  gateway-owned one keeps its price at the gateway. True about the SOURCE and wrong about the
+  DATA: the drivers already normalised `amount`, and the cycle was sitting in every gateway's
+  payload — Asaas as `cycle`, Stripe as `price.recurring`. Nobody propagated it. Summing half a
+  book and calling it MRR was the bigger error.
+  
+  - `Subscription` gains `cycle`, mapped by the Asaas and Stripe drivers.
+  - `SubscriptionWebhookData` gains `amount`, `currency` and `cycle`, so a
+    `subscription.created`/`updated` delivery carries the price to the store.
+  - `saveSubscription` persists them. **Absent does not erase**: a `subscription.canceled`
+    carries no price, and overwriting with null would drop what `created` recorded — MRR falling
+    because of an event that never mentioned money.
+  
+  Stripe's cycle reads `interval` **and** `interval_count`: "every 3 months" is `month` × 3, and
+  reading only `interval` would count it as MONTHLY and inflate MRR threefold, silently. A
+  combination with no name here (every 5 months) yields `undefined` and is skipped by the
+  calculation rather than guessed.
+  
+  A subscription with no price or no known cycle is still ignored rather than assumed monthly, so
+  the figure stays incomplete-but-honest instead of wrong-upwards.
+
 ## 0.9.0
 
 ### Minor Changes