Waffy products
Three ways to use Waffy. Pick the one that fits how you work — or use two together.
The three ways
| Product | Who uses it | How it works | Setup required |
|---|---|---|---|
| Waffy app | Individuals making personal deals | Two people, the Waffy app in the middle — available on web and mobile. Buyer pays in, seller delivers, funds release. | Download the app or open the web version. No business account needed. |
| B2B portal | Your ops team | Your team logs into a web dashboard to create contracts, confirm delivery, and release funds — no code involved. | None. Waffy provisions your account; your team logs in. |
| API | Your platform (code) | Your system calls Waffy programmatically. Contracts set themselves up when a deal happens on your platform. | Integration work. The B2B portal is included so ops can handle exceptions. |
When your business signs up with Waffy, you get one account. You can use it through the portal, through the API, or both. You decide which at onboarding, and you can change your mind later.
How the portal and API fit together
The portal and the API are two windows into the same system. Anything your code creates through the API shows up in the portal instantly. If something needs human attention — a disputed contract, an exception the code didn't handle, a cashout request — your ops team steps in from the portal without writing a line of code.
That's why every business that builds on the API keeps the portal open alongside it. The portal isn't a fallback; it's the ops layer that makes the integration production-ready.
What your team can do in the portal
Your ops team gets a full operator view of every contract running through your platform:
- View all contracts and their current status — Payment, Delivery, Settlement, Completed
- Confirm or reject delivery when your business is the one deciding the outcome
- Trigger a refund on a rejected contract and track it back to the buyer
- Request a cashout — withdraw your org's share from settled contracts to your registered business bank account
- Handle any exception the API didn't cover — edge cases, manual overrides, operations support
Which one is for you
| Path | Who it's for |
|---|---|
| API + B2B portal (recommended) | Any business with a dev team. Your system handles the happy path through the API; your ops team uses the portal for exceptions, cashouts, and anything else that needs a human. You get both automatically — no extra setup. |
| B2B portal only | No dev team. Every contract is created, confirmed, and settled manually by your team through the portal. No code to write, no servers to run. Upgrade to API + portal later at any time. |
| Waffy consumer app | This is a separate consumer product — for individuals buying and selling with each other. It's not covered in this documentation. Talk to Business Development if your use case involves end users transacting peer-to-peer. |