verify` endpoint keeps returning

[Tinabates]

The /verify endpoint keeps returning:

{"isValid":false,"invalidReason":"missing_permit"}

even when I send paymentPayload.authorization.permit as a JSON object, matching the flow in x402-demo.

Please tell me:

• Should permit be a plain JSON object, a JWT, or a hex‑signed string?
• What is the exact key path and format for permit when using scheme: "exact_gasfree" on tron:mainnet?

{
"paymentPayload": {
"x402Version": 2,
"accepted": { /* network: "tron:mainnet", scheme: "exact_gasfree", amount, asset, payTo / },
"payload": { / token, from, to, amount_raw, signature / }
},
/ tried variants below — see list */
}

Thank you!

[Tinabates]

I’ve tried:

• paymentPayload.authorization.permit as a JSON object (with type: "facilitator", facilitatorId, issuedAt, expiresAt)
• paymentPayload.authorization.permit as a JWT‑style string

Both still return:

{"isValid":false,"invalidReason":"missing_permit"}

What is the exact format and key path for permit when using exact_gasfree on tron:mainnet?

• Does permit need to be:
  • a signed JWT,
  • a hex‑signed message,
  • or something else?
• What is the canonical example?
  I’ve tried:

paymentPayload.authorization.permit as a plain JSON object.

paymentPayload.authorization.permit as a real ES256‑signed JWT (with type: "facilitator", facilitatorId, issuedAt, expiresAt).
Both still return:
json
{"isValid":false,"invalidReason":"missing_permit"}

Thanks!