PayFence Live Demo
Walk through real API monetization flows. Each demo uses live PayFence tokens, real quota tracking, and authentic 402 Payment Required responses.
API Provider Demos
Step-by-step API call demos showing token auth, quota metering, and 402 responses.
FakeExpedia
CheckingProxy Mode
Travel booking API protected by PayFence Gateway proxy. All traffic flows through the gateway, which handles auth, quota enforcement, and rate limiting. The origin server rejects direct access.
FakeAmazon
CheckingMiddleware Mode
E-commerce API with PayFence middleware integrated directly. The app validates tokens on each request, enforces quotas, and returns 402 with checkout URLs when quota is exhausted.
Consumer App Demos
Real consumer apps built on PayFence-protected APIs. See what your API customers would build.
TravelAgent
CheckingProxy Consumer
A travel search & booking app consuming FakeExpedia via the PayFence gateway. Search flights and hotels, place holds, book trips — with real quota tracking and 402 payment walls.
DealFinder
CheckingMiddleware Consumer
A price comparison tool scanning FakeAmazon alongside mock retailers. See scan intensity controls, quota burn rates, and 402 payment walls when the API budget runs out.
Architecture
Browser (You)
|
+--- Demo Console (BFF) --------+--- TravelAgent (BFF) ----+--- DealFinder (BFF) ------+
| Step-by-step API demos | Travel search app | Price comparison app |
| | | |
v v v |
PayFence Gateway -----> FakeExpedia API FakeAmazon API <---+
(proxy mode) (origin-protected) (middleware mode)
+ FakeBestBuy (mock)
+ FakeWalmart (mock)All API tokens remain server-side. The browser never sees or sends PayFence tokens directly. This is the Backend-For-Frontend (BFF) pattern.
Request authorized, quota deducted, response returned.
Quota exhausted. Response includes checkout URL.
Direct origin access blocked. Must go through gateway.