-
Notifications
You must be signed in to change notification settings - Fork 1
adding sending / receiving vasp methods for demo #204
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
adding sending / receiving vasp methods for demo #204
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @matthappens and the rest of your teammates on |
@@ -38,7 +38,7 @@ import me.uma.protocol.createCounterPartyDataOptions | |||
import me.uma.protocol.createPayeeData | |||
import me.uma.protocol.identifier | |||
|
|||
class Vasp2( | |||
class ReceivingVasp( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call :-)
call.debugLog(sendingVasp.payInvoice(call)) | ||
} | ||
|
||
post("/api/uma/request_and_pay_invoice") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should really be request_invoice_payment
or something. It's not actually paying the invoice, but rather, just sending a notification to the user for them to trigger a payment. Feel free to find a name you think fits better. Would be good to align all of the demo vasps with the same routes.
e71c36c
to
9817cd7
Compare
Initial commit - rename vasp1 & vasp 2 to sending/receiving vasp, add skeleton methods for new routes