Acme Pay: customer migration status

Across your customers’ repos with Driftfix installed: who has moved off each old API, and what’s holding the rest back.

Installed repos affected1,938repos with Driftfix installed · 6 changes
Migrated80%1,556 repos on the new API
Migrated through Driftfix1,372merged a Driftfix PR · what you’re billed on
Blocked197see why on each change

Share of affected installed repos migrated, by week since announcement

0%25%50%75%100%Week 0Week 4Week 8Week 12Week 16Week 20Week 24Charges v1 shuts down; move to the Payments API · Week 0: 0%Charges v1 shuts down; move to the Payments API · Week 1: 18%Charges v1 shuts down; move to the Payments API · Week 2: 35%Charges v1 shuts down; move to the Payments API · Week 3: 50%Charges v1 shuts down; move to the Payments API · Week 4: 62%Charges v1 shuts down; move to the Payments API · Week 5: 73%Charges v1 shuts down; move to the Payments API · Week 6: 80%Charges v1 shuts down; move to the Payments API · Week 7: 84%Webhook events move to v2 payloads · Week 0: 0%Webhook events move to v2 payloads · Week 1: 10%Webhook events move to v2 payloads · Week 2: 19%Webhook events move to v2 payloads · Week 3: 27%Webhook events move to v2 payloads · Week 4: 35%Webhook events move to v2 payloads · Week 5: 41%Node SDK 5.0: create a client instead of global config · Week 0: 0%Node SDK 5.0: create a client instead of global config · Week 1: 12%Node SDK 5.0: create a client instead of global config · Week 2: 27%Idempotency keys are required on POST requests · Week 0: 0%Idempotency keys are required on POST requests · Week 1: 12%Idempotency keys are required on POST requests · Week 2: 23%Idempotency keys are required on POST requests · Week 3: 33%Idempotency keys are required on POST requests · Week 4: 42%Idempotency keys are required on POST requests · Week 5: 51%Idempotency keys are required on POST requests · Week 6: 58%Idempotency keys are required on POST requests · Week 7: 65%Idempotency keys are required on POST requests · Week 8: 71%Idempotency keys are required on POST requests · Week 9: 77%Idempotency keys are required on POST requests · Week 10: 81%Idempotency keys are required on POST requests · Week 11: 85%Idempotency keys are required on POST requests · Week 12: 88%Idempotency keys are required on POST requests · Week 13: 90%Idempotency keys are required on POST requests · Week 14: 92%Idempotency keys are required on POST requests · Week 15: 93%Idempotency keys are required on POST requests · Week 16: 93%Secret keys are deprecated for server calls; use restricted keys · Week 0: 0%Secret keys are deprecated for server calls; use restricted keys · Week 1: 9%Secret keys are deprecated for server calls; use restricted keys · Week 2: 18%Secret keys are deprecated for server calls; use restricted keys · Week 3: 27%Secret keys are deprecated for server calls; use restricted keys · Week 4: 34%Secret keys are deprecated for server calls; use restricted keys · Week 5: 42%Secret keys are deprecated for server calls; use restricted keys · Week 6: 48%Secret keys are deprecated for server calls; use restricted keys · Week 7: 55%Secret keys are deprecated for server calls; use restricted keys · Week 8: 60%Secret keys are deprecated for server calls; use restricted keys · Week 9: 66%Secret keys are deprecated for server calls; use restricted keys · Week 10: 70%Secret keys are deprecated for server calls; use restricted keys · Week 11: 75%Secret keys are deprecated for server calls; use restricted keys · Week 12: 79%Secret keys are deprecated for server calls; use restricted keys · Week 13: 82%Secret keys are deprecated for server calls; use restricted keys · Week 14: 85%Secret keys are deprecated for server calls; use restricted keys · Week 15: 88%Secret keys are deprecated for server calls; use restricted keys · Week 16: 90%Secret keys are deprecated for server calls; use restricted keys · Week 17: 92%Secret keys are deprecated for server calls; use restricted keys · Week 18: 94%Secret keys are deprecated for server calls; use restricted keys · Week 19: 95%Secret keys are deprecated for server calls; use restricted keys · Week 20: 96%Secret keys are deprecated for server calls; use restricted keys · Week 21: 96%Secret keys are deprecated for server calls; use restricted keys · Week 22: 97%Secret keys are deprecated for server calls; use restricted keys · Week 23: 97%Secret keys are deprecated for server calls; use restricted keys · Week 24: 97%
Charges v1 shuts down; move to the Payments APIWebhook events move to v2 payloadsNode SDK 5.0: create a client instead of global configIdempotency keys are required on POST requestsSecret keys are deprecated for server calls; use restricted keys
ChangeDeadlineAffectedPRs deliveredMigratedVia DriftfixBlocked
Refunds move under payments: /v1/refunds is deprecated
Deprecation · announced Oct 5, 2026 · Not released
 Apr 1, 2027 · 177 days—— — ——
Charges v1 shuts down; move to the Payments API
Breaking change · announced Aug 18, 2026
 Dec 1, 2026 · 56 days
On pace for 98% by then
412389
84%
 87%64
Webhook events move to v2 payloads
Deprecation · announced Sep 2, 2026
 Mar 1, 2027 · 146 days
On pace for 93% by then
268214
41%
 89%58
Node SDK 5.0: create a client instead of global config
Breaking change · announced Sep 21, 2026
 No deadline13388
27%
 86%16
Idempotency keys are required on POST requests
Breaking change · announced Jun 10, 2026
 Sep 15, 2026 (passed)521498
93%
 89%38
Secret keys are deprecated for server calls; use restricted keys
Deprecation · announced Apr 14, 2026
 Jul 1, 2026 (passed)604577
97%
 88%21

These counts cover repos where your customers installed the Driftfix app, not your whole customer base. You never see customer code, diffs, file paths or test output, and counts under 5 are hidden so no single customer can be picked out. Repos are named only when their owners turned that on.