Integration Flow: Web App Using CRE8 APIs

Consider a third-party web platform (say a freelance site that wants to offer crypto escrow via CRE8) – what steps would it take?

1. User Authentication: Redirect user to CRE8 to connect their wallet, or use an OAuth-like handshake with CRE8 (if CRE8 provides one). The result is the third-party gets an API token linked to the user’s CRE8 account.

2. Listing Creation: When a user posts a job on the third-party site, the site calls CRE8’s API to create a corresponding tokenized service listing (with details and price). It stores the returned listing ID.

3. Displaying to Buyer: On the third-party site, buyers see an option “Pay with Crypto (via CRE8)”. If chosen, the site uses CRE8 API to initiate purchase.

4. Payment Process: The buyer confirms the transaction in their wallet (the third-party can show a QR or deep link if buyer is on mobile, to their wallet, using CRE8’s provided transaction).

5. Escrow Confirmation: CRE8 notifies via webhook or callback that payment is in escrow. The third-party site updates the order status to “In Escrow”.

6. Service Delivery: Off-chain as usual (the third-party continues to manage the workflow or directs users to use CRE8 chat).

7. Completion: When done, either the third-party site calls the CRE8 API to release (if they trust their own confirmation triggers) or asks the user to confirm via CRE8’s interface.

8. Settlement: Funds release to the seller’s wallet. The third-party could call CRE8 API to get the final outcome and update records (mark as paid, maybe record transaction hash for reference).

This integration flow allows existing platforms to plug into CRE8 for the blockchain components without rebuilding them from scratch.