Skip to content

Subscription: batch_charge - #138

Open
edwina105 wants to merge 1 commit into
stellar-sub:mainfrom
edwina105:fix/drips-edwina105-49
Open

edwina105 wants to merge 1 commit into
stellar-sub:mainfrom
edwina105:fix/drips-edwina105-49

Conversation

@edwina105

Copy link
Copy Markdown
Contributor

Subscription: batch_charge

Adds batch_charge(merchant, ids) so a merchant can charge many subscriptions in one transaction.

  • Every id goes through the full charge checks (CAP, INTERVAL, REVOCATION), and the merchant authorizes once.
  • The batch is all or nothing. The first failing id returns its error and the whole call rolls back, so nothing is charged. Skip-and-report was not used, because an error returned from an internal call to charge does not roll back that call's writes.
  • At most MAX_BATCH (20) ids are accepted, otherwise BatchTooLarge.
  • Tests cover a full batch, rollback when one id fails, another merchant's id, and the size limit.

Closes #49

The issue was marked "Needs design" and asked for maintainer agreement first. This PR implements it at the contributor's request, so maintainers may want to confirm the all-or-nothing choice and the batch size.

The code has not been compiled or run. Please check it in CI.

🤖 Generated with Claude Code

… once (stellar-sub#49)

Add batch_charge(merchant, ids). Every id goes through the full charge
checks (CAP, INTERVAL and REVOCATION), and the merchant authorizes once for
the call. The batch is all or nothing: the first id that fails returns its
error and the whole call is rolled back, so nothing is charged. This is
deliberate. An error returned from an internal call to charge does not roll
back its writes, so skip-and-report would leave partial state. At most
MAX_BATCH (20) ids are accepted, otherwise BatchTooLarge is returned. Tests
cover a full batch, rollback when one id fails, another merchant's id, and
the size limit.

Closes stellar-sub#49

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@drips-wave

drips-wave Bot commented Oct 21, 2026

Copy link
Copy Markdown

@edwina105 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add batch_charge(merchant, ids) so a merchant can charge many subscriptions in one transaction

1 participant