Be Paid to Get Deployed

The project was built to be a way to allow freelance web developers to push amends to client sites upon receiving full payments.

The flow is as follows:

  1. Developer makes change on feature branch
  2. Developer raises PR to main branch
  3. WebHook is triggered to Be Paid to Get Deployed
  4. Be Paid to Get Deployed queries QuickBooks API
  5. QuickBooks API returns whether the payment has been received in full

A client can then be informed that the changes have been made, and an invoice has been sent. The flow is then:

  1. Client makes a payment into a Starling bank account
  2. Starling triggers a WebHook on Be Paid to Get Deployed
  3. Be Paid to Get Deployed triggers a payment to QuickBooks
  4. Be Paid to Get Deployed updates the status of the GitHub branch status
  5. If the branch status succeeds, merge the changes!

Written by Jamie Tanna on 22 October 2017, and last updated on 23 December 2018.