Repositories / orbit-labs
Acme Pay · deprecation
Secret keys are deprecated for server calls; use restricted keys
Merged
- Deadline
- Jul 1, 2026
- Announced
- Apr 14, 2026
- Pull request
- #74 · opened Apr 16 · merged Apr 21
- Diff
- 2 files · +10 −5
- Tests
pytest· 170 passed, 0 failed · 74s
From the Acme Pay migration guide
Server-side calls should use a restricted key:
new Acme({ apiKey: process.env.ACME_RESTRICTED_KEY }). Secret keys stop working for these endpoints on July 1.
Found the code that uses the old API2s
Wrote the fix from the migration guide41s
Safety check on the patch40 ms
Ran your tests in a sandbox2m 39s
Opened the pull request2s
Acme Pay · breaking change
Idempotency keys are required on POST requests
Merged
- Deadline
- Sep 15, 2026
- Announced
- Jun 10, 2026
- Pull request
- #75 · opened Jun 10 · merged Jun 12
- Diff
- 2 files · +23 −21
- Tests
pytest· 102 passed, 0 failed · 126s
From the Acme Pay migration guide
Every POST must send an
Idempotency-Key header. The SDK adds one when you pass idempotencyKey in the request options.
Found the code that uses the old API3s
Wrote the fix from the migration guide64s
Safety check on the patch40 ms
Ran your tests in a sandbox2m 19s
Opened the pull request2s
Acme Pay · breaking change
Charges v1 shuts down; move to the Payments API
Merged
- Deadline
- Dec 1, 2026
- Announced
- Aug 18, 2026
- Pull request
- #76 · opened Aug 19 · merged Aug 23
- Diff
- 2 files · +15 −4
- Tests
pytest· 168 passed, 0 failed · 130s
From the Acme Pay migration guide
charges.create() is replaced by payments.create(). Arguments and the returned object are unchanged, except source is now payment_method.
Found the code that uses the old API944 ms
Wrote the fix from the migration guide62s
Safety check on the patch40 ms
Ran your tests in a sandbox2m 25s
Opened the pull request2s
Acme Pay · deprecation
Webhook events move to v2 payloads
Needs a person
- Deadline
- Mar 1, 2027
- Announced
- Sep 2, 2026
- Why
- The handler verifies signatures over the raw v1 payload, and the guide does not say how v2 signatures are computed
From the Acme Pay migration guide
In v2 events the changed object is at
event.data.resource instead of event.data.object. Event type names do not change.
Found the code that uses the old API3s
Wrote the fix from the migration guide · the handler verifies signatures over the raw v1 payload, and the guide does not say how v2 signatures are computed69s
Also checked and not affected: Acme Pay: Node SDK 5.0: create a client instead of global config · Nimbus AI: embeddings-v1 shuts down; use embed-2 · Nimbus AI: nimbus-text-2 is retired; use nimbus-text-3 · Nimbus AI: Offset pagination is removed from list endpoints