
Integration → Live → Flovia result → Simulate
HitPay MPP showcase
Integration
HitPay MPP route
app.get("/showcase/hitpay-mpp/paid", (c) =>
protectedPaid(c.req.raw, undefined),
);With Flovia SDK
app.get(
"/showcase/hitpay-mpp/paid",
flovia.paidApi({ provider: "hitpay", rail: "mpp" }),
(c) => protectedPaid(c.req.raw, undefined),
);Live flow
Call the real HitPay MPP endpoint
This PoC does not take a real payment here. First call returns a 402 challenge; then complete the sandbox checkout.
Response summary appears here.
What Flovia joins
Payment dashboards know who paid. API logs know what was used. Flovia connects them.
Payment rail
HitPay / MPP
hitpay_demo_charge_001S$1.00 SGDcheckout URL
API provider
Paid API request
GET /showcase/hitpay-mpp/paidstatus + latencyrequest id + response
→
Flovia join layer
Joined paid API event
payment id×request id
payer / recipient×endpoint
amount / status×workflow
→
Business output
Provider decisions
which endpoints convertwhich workflows retainwhere to price / upsell
Simulated flow
What happens before a live wallet or checkout is involved
1
Agent calls paid API
GET /showcase/hitpay-mpp/paidno payment credentialrequest id created
2
MPP blocks access
HitPay MPP402 challenge + checkout URLstatus 402
3
Payment completes
checkout session + QR paymenthitpay_demo_charge_001S$1.00 SGD
4
API access granted
paid retry + API responsestatus 200response { foo: "bar" }
5
Flovia joins event
payment contextendpoint usageworkflow signal
Payment lane
HitPay MPP
Checkout URL / QRhitpay_demo_charge_001S$1.00 SGD402 challenge + checkout URL
API lane
Provider endpoint
/showcase/hitpay-mpp/paidrequest → 402 → retry200 paid responselatency captured
Flovia lane
Joined analytics event
payment id ↔ request idrail ↔ endpointpaid response ↔ workflowretained demand signal
Event payload preview
{
"requestId": "req_demo_001",
"provider": "hitpay",
"rail": "mpp",
"endpoint": "/showcase/hitpay-mpp/paid",
"paymentId": "hitpay_demo_charge_001",
"responseStatus": 200,
"latencyMs": 47,
"insight": "payment converted into paid API demand"
}