Skip to content

feat: add addrecipient() to append a recipient before payment#128

Closed
Sundriveauto wants to merge 4 commits into
Stellar-split:mainfrom
Sundriveauto:feat/add-recipient-to-invoice
Closed

feat: add addrecipient() to append a recipient before payment#128
Sundriveauto wants to merge 4 commits into
Stellar-split:mainfrom
Sundriveauto:feat/add-recipient-to-invoice

Conversation

@Sundriveauto
Copy link
Copy Markdown
Contributor

@Sundriveauto Sundriveauto commented May 30, 2026

Closes #70

Closes #71

Closes #72

Closes #73
Allows the creator to call addrecipient() on a pending invoice as long as no payment has been received yet (funded == 0). Appends the new recipient and amount to the parallel recipients/amounts/tokens/claimed vecs, emits a recipient_added event, and writes an audit entry.

Allows the creator to call addrecipient() on a pending invoice as long
as no payment has been received yet (funded == 0). Appends the new
recipient and amount to the parallel recipients/amounts/tokens/claimed
vecs, emits a recipient_added event, and writes an audit entry.
@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented May 30, 2026

@Sundriveauto 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

Emits a structured invoice_completed event from _release_full (both main
release and group-member release) and _release_tranches when an invoice's
status becomes Released. The payload includes invoice_id, creator, total,
recipient_count, and completion_timestamp so off-chain systems can
process completions without polling.
If refund() detects the contract token balance is insufficient to repay
payers (e.g. due to a contract bug draining funds), it draws from the
insurance_pool deposited by the creator at invoice creation. Emits an
insurance_used event with shortfall and remaining pool details. On
cancel, release, or normal refund, unused insurance is returned to the
creator.
…ents

schedule_pay() registers a payment intent at a specific future ledger
timestamp, consuming the nonce to prevent double-use. A separate
execute_scheduled_pay() call processes the transfer once the timestamp
is reached, requiring payer authorization at execution time. Emits a
payment_scheduled event on scheduling.
@Kingsman-99
Copy link
Copy Markdown
Contributor

please resolve your conflict

@Sundriveauto Sundriveauto closed this by deleting the head repository May 30, 2026
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.

Implement invoice payment scheduling Build refund insurance pool Add invoice completion webhook trigger Implement dynamic recipient addition

2 participants