In the app we use the messaging.paymentRequest function to send a payment request to particular user.
I think that we should allow sending a paymentRequest with no amount set. This could be used in cases where we don't know how much the counterParty should send us.
Example:
UserA pays for lunch for userB, userC, userD.
UserA doesn't know how much the meals for B,C and D costet, but B,C and D do. In this case userA could just send a paymentRequest with no amount and B, C and D just fill out the amount and pay.
Right now we can submit a paymentRequest with no amoutn specified, but doing so will result in the amount being returned from the clientlib to be {decimals: 1, raw: NaN, value: NaN} which is not ideal?
Thoughts?
In the app we use the messaging.paymentRequest function to send a payment request to particular user.
I think that we should allow sending a paymentRequest with no amount set. This could be used in cases where we don't know how much the counterParty should send us.
Example:
UserA pays for lunch for userB, userC, userD.
UserA doesn't know how much the meals for B,C and D costet, but B,C and D do. In this case userA could just send a paymentRequest with no amount and B, C and D just fill out the amount and pay.
Right now we can submit a paymentRequest with no amoutn specified, but doing so will result in the amount being returned from the clientlib to be {decimals: 1, raw: NaN, value: NaN} which is not ideal?
Thoughts?