Discover / paidontempo.xyz

tempo-receipt-verify

■ Challenge detected

Independently verify that a Tempo MPP payment settled on-chain — decodes ERC-20 transfers in the transaction, confirms amount/currency/recipient, returns block and confirmations.

Challenge detected
3 of the last 3 checks
Median response
34 ms
Last checked
9 Oct, 18:22 UTC
In our index since
7 Oct 2026

Endpoint

curl -i https://paidontempo.xyz/api/verify
# 402 Payment Required: pay with a MPP client, then send the request again.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/paidontempo.xyz

Recent checks

7 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.9 Oct 2026
All 3 checks
When (UTC)ResultHTTPResponse
9 Oct, 18:22 UTCChallenge detected40234ms
8 Oct, 09:20 UTCChallenge detected40234ms
7 Oct, 00:22 UTCChallenge detected40239ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 9 Oct, 18:22 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does tempo-receipt-verify advertise?

The listing advertises MPP, Tempo and USDC. Check the seller's current payment challenge and authentication requirements before paying.

Where is tempo-receipt-verify listed?

In mppscan. Superstables first indexed it on 7 Oct 2026.

Something wrong on this page? Tell us.