Thank you! We'll get these bugs fixed asap. The board is mainly for subcontracting/delegating tasks to other devs so it asks for a separate funding source. I see where this is confusing and we will iterate accordingly. I really appreciate the feedback here.

Great point. You would actually use your standard contract with clients as you do now so your clause would still be active. We have a dispute process in place now if a client steals code without paying for it, it ultimately triggers an investigation and can impact client's reputation within our system.

As a consultant, failure-to-pay is always on my mind--I'm sure you guys have seen it too. Why should a client care about their reputation within your system? If they're burning a developer, they can burn you too just as easily.

I would be much more likely to use your service, instead of just an Excel invoice or whatever (it's really just not that difficult to do once you've done it once, IMO) if I got something concrete for doing it. "Reputation", as we have all seen from Amazon's marketplace and from eBay and the rest, just doesn't mean all that much. It seems logical for this service to provide escrow, or at least partner with someone who does.

> it ultimately triggers an investigation and can impact client's reputation within our system

TrapFi will notify all future developers that the client has acted unethically in the past, before you agree to work with them. Truthfully, we have not yet encountered an issue with a client stealing code.

We hear your concerns and see that this is a priority for the community, so we'll work on a more robust solution.

first

> It's money you've earned, delivered instantly.

second

> it ultimately triggers an investigation and can impact client's reputation within our system

Hmm, this is confusing. Is bad reputation in your system the only penalty for an employer not paying? And that's it?

So you can design and implement a complex automated system implementing your own logic, a 3rd party API and a payment service.

But this, you didn't understand before doing so?

Do you get you are on HN, not facebook, and therefor people may doubt your sincerity on this point?

Just to save you a marketing shaped comment as a response, it's rhetorical.

So where did you get the emails?

Thanks for your feedback! The payout is only triggered when a client approves a pull request.

Thanks for the feedback and great question here.

PRs are still attached to an hourly or flat rate that you and the client have agreed upon. This means you will not make more money for submitting more PRs. You just receive your payments sooner.

The client also approves your pull request to trigger the payout. The minute your code is accepted into their codebase you receive payment.

I'd love to hear more thoughts on your concern here and if this solves it, really great insight.

Would love to hear your comments on my second point as well. How does this not ruin long-term prospects of projects?

The payouts are issued on PR approval, which has mitigated the spamming of low quality work.

> I'm not concerned about the long-term of the project

You're right. With TrapFi, we try to fix this with a high degree of transparency regarding the quality of work that the developer is charging the client for.

> With TrapFi, we try to fix this with a high degree of transparency regarding the quality of work that the developer is charging the client for.

This sounds a bit ominous — you do what exactly to create a high degree of transparency?

We simply link to the pull requests in the client's bill. Also, a repo admin can review the work before a payment is issued.

We're actually adding international support this week. I will respond back here as soon as it's live.

Great question. So far we've seen users receive a partial payment upfront with the remaining balance paid out automatically at code delivery.

Awesome! Yes, we take care of the paper trail as well.