← Back to reports

Conformance report
open-pay.jp

Checked: 2026-10-20T00:29:58.180Z

Resource: GET /api/paid/usdc/stablecoin-payments?changedSince=2026-08-01

Result: 11/11 passed

Fingerprint: sha256:0428ffa75ff56c4306977aa7b9f4d64b4f5405f95e19be4aab27fe0ac3f908ab

Open seller site ↗

Individual checks

CheckHTTPGradeReason
challenge_present
Does an unpaid request answer with a valid 402 challenge?		402passedValid HTTP 402 challenge.
malformed_signature
Is an unreadable payment header refused rather than answered with a 5xx?		402passedRefused with HTTP 402.
wrong_recipient
Is a payment to a different recipient refused?		402passedRefused with HTTP 402.
wrong_asset
Is a token other than the one demanded refused?		402passedRefused with HTTP 402.
underpayment
Is an amount below the price refused?		402passedRefused with HTTP 402.
wrong_network
Is a payment on the wrong chain refused?		402passedRefused with HTTP 402.
expired
Is an expired authorization refused?		402passedRefused with HTTP 402.
replayed_nonce
Is a reused nonce refused?		402passedRefused with HTTP 402.
not_yet_valid
Is a not-yet-valid authorization refused?		402passedRefused with HTTP 402.
domain_version
Is a contract version supplied by the request ignored?		402passedRefused with HTTP 402.
domain_chain_id
Is a chain id supplied by the request ignored?		402passedRefused with HTTP 402.

Method and limits

An unpaid challenge is requested first. The remaining requests carry unreadable or altered payment headers with fabricated signatures. No valid payment is ever sent and no money moves. The responses demonstrate HTTP refusals, not isolated cryptographic field or replay security. At most 11 requests per origin including the challenge, one per second.

Original data (JSON)

Report history