job result -> job feedback

[patrickReiis]

If I understood correctly:

1. the user announces a service it wants fulfilled
2. the service provider gives a feedback requiring a payment before proceeding
3. once the payment is complete, the service provider gives the desired output.

It doesn't make sense to zap after the output is performed, because people could just ask for services and never pay them back.

The zap should be to the job feedback, no?

Of course step 2 is not required but I think this will happen in 90% of the cases

[pablof7z]

some coffeeshops ask you to pay when you order, some coffeeshops ask you to pay when you leave because it's a better customer experience.

not top-down directing how customer/businesses must engage allows for flexibility in business models / sampling of outputs / etc

[patrickReiis]

I see, so in this case, the documentation should be changed to zap the job result or job feedback event?

[patrickReiis]

Also, it says: Service Providers MUST use the payment-required feedback event to signal that a payment is required and no further actions will be performed until the payment is sent.