Payment Decorator #129
Closed
Payment Decorator #129
Conversation
This file contains 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
Signed-off-by: Sam Curren <telegramsam@gmail.com>
Signed-off-by: Sam Curren <telegramsam@gmail.com>
|
I would love to see more flexible format considering these use cases
Can we reuse (or try to be compatible with) the Payment Request API defined by the Web Payments Group? |
|
@TelegramSam and @tmarkovski : Would you mind if I took a crack at converting this to an Aries RFC and addressing some of Tomislav's suggestions? |
@dhh1128 Please do. I'm happy to contribute and would love to see payment RFCs out for discussion. |
|
This is now superseded by hyperledger/aries-rfcs#75. @TelegramSam , can we close this PR? |
|
closed, per @dhh1128's note above. |
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.
Signed-off-by: Sam Curren telegramsam@gmail.com