For the supplied Stripe v1 pagination interfaces, limit shapes one response. Completion comes from continuation state, while any processing budget remains an application decision.
A Stripe v1 pagination design should make one owner responsible for every follow-up request: either a documented client-library helper or application-controlled manual traversal.
Use strong ETags with If-Match to make a shared-document save conditional on the version a user actually read. Learn where wildcard checks differ, why weak validators fail, and how to bound recovery after a failed precondition.
Design an application-owned boundary that distinguishes Stripe v1 list object-ID cursors from search continuation tokens, records navigation intent, and rejects incompatible cursor use before request construction.
A recovery-oriented design for Stripe v1 list imports: separate cursor traversal from target durability, make replay safe, and treat interrupted pages as explicit states.