The Waffy API allows companies and online platforms, such as marketplaces and e-commerce stores, to integrate Waffy’s escrow service directly into their own platforms without directing customers to the Waffy website.
Your platform does not need to hold or transfer the funds at any point. Waffy handles the entire process of holding, collecting, and releasing the funds. Your team only needs to notify Waffy through an API call when delivery is completed.
Who are the parties involved?
Every transaction through the Waffy API involves three parties:
- Buyer (CUSTOMER): Pays the amount into the escrow account, receives the product or service, and can receive a refund if the delivery is rejected.
- Seller (PROVIDER): Delivers the product or service and receives the payment once the transaction is completed.
- Company (BROKER): Your platform, which creates the contract, confirms or rejects the delivery, and sends the final settlement request to distribute the funds.
How does it work?
When the buyer makes a payment, Waffy holds the funds in escrow without releasing them to either party. The funds remain secure until your platform, acting as the broker, tells Waffy what to do with them—whether to release the funds to the seller after delivery is confirmed or return them to the buyer if the delivery is rejected.
This gives your customers the same escrow protection available on the Waffy platform without requiring them to leave your website or app.
Example
The Trusted Purchase service on Haraj is an example of the Waffy API in action. Buyers and sellers use the escrow service directly within the Haraj platform, while Waffy manages the fund protection in the background.