Clarify accounting and window semantics of agent_wallet_spend_limits.used

Open
  • Is something wrong?
#508 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
go, typescript
Domain
documentation

Research direction

This is a request for the supported accounting and window contract behind daily.used and thirty_day.used in user-info retrieve, not a code change. Start from the linked Go SDK types in packages/sdk-go/types.go and the spend-request documentation, and check whether the CLI source defines any of the counting. Done means a maintainer-confirmed definition of counted amounts, window boundaries, currency and payment correlation fields, or a clear statement that some of it is server-defined.

Written by the indexing model from the issue text.

Description

I am integrating @stripe/[email protected] and need to interpret daily.used and thirty_day.used from user-info retrieve correctly.

The spend-request documentation describes these values in cents. The 1.0.0 Go SDK types describe both counters as rolling. I could not find the accounting definition needed to compare them with request/payment history.

Could you clarify or link to the supported contract for:

  1. Counted amounts: Do used values count requested, approved/reserved, authorized or completed payment amounts? When do cancellation, expiry, failure, refund and amount changes affect them?
  2. Windows and timing: Does daily mean the preceding 24 hours and thirty_day the preceding 720 hours? Which event timestamp and boundary rule determine membership? Is there an observation timestamp or documented update delay for the counters?
  3. Source scope and currency: Do these counters and spend-request list --include-history cover the same user/grants? What history retention or pagination limits apply? Is counter usage always USD cents, including requests in other currencies?
  4. Correlation: Which payment identity, amount and time fields should be used to explain usage in both windows without counting the same payment twice? In particular, what event and time unit does payment_status_details.created represent, and is the supported transaction ID at request level or inside payment details? Is request history sufficient, or is that reconciliation unsupported through these commands?

This is a documentation question, not an account-specific incident. No credentials, account lookup or payment reproduction are needed. If the behavior differs from CLI 1.0.0, please identify which semantics are version-specific and which are server-defined.

Dominant language
TypeScript
Stars
885
Forks
156
Avg merge
1d 2h
Merged PRs (30d)
62

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stripe/link-cli

All issues in stripe/link-cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.