-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Validation mechanism for SPSP #582
Comments
Have been thinking along those lines myself. Would this require some kind of PKI ? The SPSP endpoint would need a lot more state. With the current receipt model, backends integrating WM need to make requests to some receipt verifier upon each packet to "verify". So why not require a request to some SPSP endpoint? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is important, please feel free to bring it up on the next Interledger Community Group Call or in the Gitter chat. |
Please let me know |
receipts_enabled
shared_secret
destination_account
From @marcoscaceres: Would be nice if the SPSP has an algorithm to hook directly into for validation. And it returned true or false. So... "perform simple payment validation", which takes a json object.
The text was updated successfully, but these errors were encountered: