@siglume/direct-request-payment 0.3.0 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,50 +1,61 @@
1
- # Changelog
2
-
3
- ## 0.3.0 - 2026-06-12
4
-
5
- Recurring payment approval release.
6
-
7
- - Added recurring (subscription / scheduled autopay) merchant approval helpers
8
- in TypeScript (`createDirectRequestPaymentRecurringChallenge`,
9
- `createDirectRequestPaymentRecurringChallengeSignature`,
10
- `verifyDirectRequestPaymentRecurringChallenge`) and Python
11
- (`create_direct_request_payment_recurring_challenge`,
12
- `create_direct_request_payment_recurring_challenge_signature`,
13
- `verify_direct_request_payment_recurring_challenge`).
14
- - Recurring approvals use a new single-use challenge scheme
15
- (`siglume-external-402-recurring-v1`) with the cadence (`monthly` for
16
- subscriptions, `daily` for scheduled autopay) bound into the HMAC, so
17
- one-time checkout challenges and recurring approvals can never be replayed
18
- as each other.
19
- - Documented the recurring payment flow (subscription and scheduled autopay)
20
- in the README.
21
- - Updated pricing docs: the Launch plan's free monthly allowance of 100
22
- payments is retired — Launch is now a flat 1.8% payment fee; the per-payment
23
- minimum fee is JPY 30 (USD merchants: USD 0.20); JPY/JPYC and USD/USDC
24
- settlement are both documented as first-class.
25
-
26
- ## 0.2.0 - 2026-06-12
27
-
28
- Merchant self-service setup release.
29
-
30
- - Added TypeScript `DirectRequestPaymentMerchantClient` and Python
31
- `DirectRequestPaymentMerchantClient`.
32
- - Added `setupCheckout` / `setup_checkout` to claim a merchant key, prepare a
33
- billing mandate, and create a webhook subscription from the SDK.
34
- - Added challenge secret rotation, merchant status lookup, billing mandate
35
- preparation, and webhook subscription helpers.
36
- - Updated docs to remove manual onboarding assumptions and clarify merchant JWT
37
- vs buyer JWT responsibilities.
38
-
39
- ## 0.1.0 - 2026-06-11
40
-
41
- Initial public release.
42
-
43
- - Published TypeScript/JavaScript SDK as `@siglume/direct-request-payment`.
44
- - Published Python SDK as `siglume-direct-request-payment`.
45
- - Added merchant challenge helpers, buyer-authenticated Direct Request Payment
46
- client methods, prepared transaction payload helpers, and webhook signature
47
- verification helpers.
48
- - Documented Launch, Starter, Growth, and Pro trial pricing.
49
- - Documented the distinction from `@siglume/api-sdk` and Developer Portal
50
- `cli_` API keys.
1
+ # Changelog
2
+
3
+ ## 0.3.1 - 2026-06-12
4
+
5
+ - Docs: scheduled autopay (`cadence: "daily"`) is documented as an approval
6
+ tag, not a once-per-day run limit. Siglume no longer caps scheduled autopay
7
+ at one charge per day; occurrences are bounded by the buyer's per-run,
8
+ daily, and monthly auto-pay budget plus the authorization's `max_runs` /
9
+ expiry. No code or wire-format changes — challenges signed by 0.3.0 verify
10
+ unchanged.
11
+ - Release automation now uses npm and PyPI Trusted Publishing from GitHub
12
+ Actions, so normal releases do not require local npm OTP or PyPI credentials.
13
+
14
+ ## 0.3.0 - 2026-06-12
15
+
16
+ Recurring payment approval release.
17
+
18
+ - Added recurring (subscription / scheduled autopay) merchant approval helpers
19
+ in TypeScript (`createDirectRequestPaymentRecurringChallenge`,
20
+ `createDirectRequestPaymentRecurringChallengeSignature`,
21
+ `verifyDirectRequestPaymentRecurringChallenge`) and Python
22
+ (`create_direct_request_payment_recurring_challenge`,
23
+ `create_direct_request_payment_recurring_challenge_signature`,
24
+ `verify_direct_request_payment_recurring_challenge`).
25
+ - Recurring approvals use a new single-use challenge scheme
26
+ (`siglume-external-402-recurring-v1`) with the cadence (`monthly` for
27
+ subscriptions, `daily` for scheduled autopay) bound into the HMAC, so
28
+ one-time checkout challenges and recurring approvals can never be replayed
29
+ as each other.
30
+ - Documented the recurring payment flow (subscription and scheduled autopay)
31
+ in the README.
32
+ - Updated pricing docs: the Launch plan's free monthly allowance of 100
33
+ payments is retired Launch is now a flat 1.8% payment fee; the per-payment
34
+ minimum fee is JPY 30 (USD merchants: USD 0.20); JPY/JPYC and USD/USDC
35
+ settlement are both documented as first-class.
36
+
37
+ ## 0.2.0 - 2026-06-12
38
+
39
+ Merchant self-service setup release.
40
+
41
+ - Added TypeScript `DirectRequestPaymentMerchantClient` and Python
42
+ `DirectRequestPaymentMerchantClient`.
43
+ - Added `setupCheckout` / `setup_checkout` to claim a merchant key, prepare a
44
+ billing mandate, and create a webhook subscription from the SDK.
45
+ - Added challenge secret rotation, merchant status lookup, billing mandate
46
+ preparation, and webhook subscription helpers.
47
+ - Updated docs to remove manual onboarding assumptions and clarify merchant JWT
48
+ vs buyer JWT responsibilities.
49
+
50
+ ## 0.1.0 - 2026-06-11
51
+
52
+ Initial public release.
53
+
54
+ - Published TypeScript/JavaScript SDK as `@siglume/direct-request-payment`.
55
+ - Published Python SDK as `siglume-direct-request-payment`.
56
+ - Added merchant challenge helpers, buyer-authenticated Direct Request Payment
57
+ client methods, prepared transaction payload helpers, and webhook signature
58
+ verification helpers.
59
+ - Documented Launch, Starter, Growth, and Pro trial pricing.
60
+ - Documented the distinction from `@siglume/api-sdk` and Developer Portal
61
+ `cli_` API keys.
package/LICENSE CHANGED
@@ -1,21 +1,21 @@
1
- MIT License
2
-
3
- Copyright (c) 2026 Siglume Contributors
4
-
5
- Permission is hereby granted, free of charge, to any person obtaining a copy
6
- of this software and associated documentation files (the "Software"), to deal
7
- in the Software without restriction, including without limitation the rights
8
- to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
- copies of the Software, and to permit persons to whom the Software is
10
- furnished to do so, subject to the following conditions:
11
-
12
- The above copyright notice and this permission notice shall be included in all
13
- copies or substantial portions of the Software.
14
-
15
- THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
- IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
- FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
- AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
- LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
- OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
- SOFTWARE.
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Siglume Contributors
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.