Verify payment reference
Partner Auth: EIP-191 signature by the partner's registered backend key, with X-Api-Deadline and optional X-Api-PublicKey headers. See the Signature and verify guide.
The user's URID (NFT token id).
Network identifier: 5000 for mainnet, 5003 for testnet.
Signature generated by the user's wallet key (EIP-191).
SHA3/Keccak256 hash of the original request payload.
Signature expiry: server timestamp plus a validity window (max 20 minutes).
The payment reference to validate.
Response envelope. For the user API, retCode 0 means success; for the partner API, code 0 means success. Business rejections return HTTP 200 with a non-zero code.
Standard response envelope for the user API (api.ur.app).
0 on success; non-zero indicates failure.
Human-readable message; error details when retCode is non-zero.
Business payload. Shape depends on the endpoint; some endpoints return it as a JSON-encoded string.
Server timestamp in milliseconds.
POST /api/v1/verify-reference HTTP/1.1
Host: api.ur.app
X-Api-Signature: YOUR_API_KEY
tokenId: text
network: text
sign: text
hash: text
deadline: text
Content-Type: application/json
Accept: */*
Content-Length: 32
{
"reference": "Invoice 2026-001"
}Response envelope. For the user API, retCode 0 means success; for the partner API, code 0 means success. Business rejections return HTTP 200 with a non-zero code.
{
"retCode": 0,
"retMsg": "success",
"result": {
"clientPayoutRefParams": {
"purposeId": 8,
"refId": "REF-7A6C2A8E"
}
},
"timeNow": 1703123456789
}Last updated