Skip to content

Fix expired FX quote retry and confirmed payout-plan compatibility - #46

Draft
TracSystems wants to merge 129 commits into
mainfrom
fix/stripe-fx-quote-expiry-v263
Draft

TracSystems wants to merge 129 commits into
mainfrom
fix/stripe-fx-quote-expiry-v263

Conversation

@TracSystems

Copy link
Copy Markdown
Contributor

Stripe changes an FX quote's lock status from active to expired. A retry of an already prepared payout then rejected the same quote because its full JSON hash changed, preventing normal reconciliation. The writer now accepts that specific status transition only when the remaining quote fields still match the prepared hash, and it retains the prepared hash in settlement evidence.

The CLI also resumes a confirmed v27 payout plan during v28 settlement without trying to re-sign or replace the immutable plan. Newly created plans continue to use v28. The contract is unchanged.

Validation: focused Rust tests passed; read-only live planning succeeded against confirmed v27 and v28 plans. A writer-only canary passed the previous FX quote hash failure point.

This branch has not been deployed

No deployments
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.

1 participant