Add Validation mechanism for SPSP
AlexLakatos opened this issue · comments
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.
Have been thinking along those lines myself.
But true/false seems less leaky than returning a balance (having said that you probably already know this anyway, from the receipt you have)
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.
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.
Please let me know