Payment Retry Wizard for Failed Transactions

[Kingsman-99]

Description

When a Stellar payment transaction fails (insufficient fee, sequence number mismatch, destination account not found, etc.), the user currently receives only a raw error code with no actionable guidance. This issue builds a payment retry wizard that intercepts failed transaction submissions, parses the Stellar error code into a human-readable explanation, suggests the appropriate corrective action (bump fee, refresh sequence number, activate destination account), and guides the user through corrected re-submission step by step.

Technical Context

Create lib/stellarErrorParser.ts mapping Stellar result_codes (e.g., tx_insufficient_fee, op_no_destination, tx_bad_seq, op_underfunded) to { title, explanation, suggestedAction, actionType: 'bump-fee'|'refresh-seq'|'fund-destination'|'manual' }. Build components/invoice/PaymentRetryWizard.tsx as a modal triggered when usePaymentSubmission receives a submission error. The wizard shows: step 1 (error explanation), step 2 (corrective action UI including bump fee slider, refresh seq button, or fund-destination link), step 3 (re-build and re-sign transaction with correction applied). Re-building uses TransactionBuilder with fresh loadAccount data for the correct sequence number. Log all retry attempts to the invoice audit trail. Limit automatic retries to 3 before surfacing a manual fallback.

Acceptance Criteria

• A tx_insufficient_fee error surfaces a wizard step with a fee-bump slider pre-set to the median fee from feeStats, and submitting the wizard creates a fee-bump transaction
• A tx_bad_seq error surfaces a "Refresh Sequence Number" button; clicking it calls loadAccount to get the current sequence number and rebuilds the transaction
• An op_no_destination error explains that the destination account is not yet funded and provides a link to fund it on the testnet Friendbot (or a mainnet guide)
• All retry attempts are logged in the invoice audit trail with the error code, corrective action taken, and outcome
• After 3 consecutive failed retries the wizard presents a "Contact support" link and disables further automatic retry
• All CI checks (npm test, npm run build, ESLint/TypeScript) pass and the branch has no merge conflicts

---

[Toyosi5566]

@Toyosi5566 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi maintainer! I’d love to work on this issue if it’s still available. I have a good understanding of the requirements and would be happy to implement the solution. Thanks for considering my request!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Toyosi5566 to this issue.

[Able-faz-system]

@Able-faz-system has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello !!!
I would love to work on this issue. I have experience building production ready applications and collaborating through GitHub workflows. I'll carefully analyze the current implementation, propose a reliable solution, and submit a well-tested PR. My focus is on clean code, maintainability, and timely delivery

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Able-faz-system to this issue.

[drips-wave]

Congratulations, @Able-faz-system! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @Able-faz-system: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊