feat: add public payment invoice flow#81
Merged
Conversation
|
@Tybravo 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! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
This PR implements the foundational public payment experience for customer-facing invoice payments in the Shade frontend application.
The implementation introduces a clean hosted-payment style layout, reusable invoice summary UI, and invalid invoice handling flow using mock async data patterns for future backend integration readiness.
Features Implemented
✅ Public Payment Page Wrapper
✅ Payment Invoice Summary Card
Created reusable invoice summary component
Displays:
Added graceful merchant logo fallback handling
Structured component for future API/smart contract integration
✅ Invalid Invoice Error State
Added reusable invalid/expired invoice state component
Includes:
Supports invalid and expired invoice scenarios
✅ Mock Async Invoice Flow
Added mock async invoice retrieval flow
Implemented:
Structured to support future backend integration with minimal refactor
Technical Notes
Testing
Tested:
Future Integration Ready
The implementation is structured for future integration with:
Related Issues
Closes #45
Closes #47
Closes #48