TAP Message Structure Check

Paste one Transaction Authorization Protocol message, or a short thread as a JSON array, and see whether it has the structure the published schemas describe: the type it matched, missing required fields, wrong field types, party and agent shape problems, and whether each reply points at an earlier message in the paste. It does not verify signatures, does not resolve identifiers, does not contact any counterparty and is not a statement that a transfer is compliant. Covered types: Transfer, Payment, Authorize, Reject, Settle, Cancel and Revert. Every other type is listed as not covered.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only. Free-text fields must hold the literal SYNTHETIC or a length marker such as [len:12]; anything else is refused.

Pasted message or thread

A single message object, or an array of messages in the order they arrived. At most 32 messages.

Basis

The walk follows copies of the public TAIPs JSON Schemas for the seven covered types, pinned at one commit of the TAIPs repository (CC0-1.0). Signature or JWS material is reported as present and not verified. Where the published test vectors and the published schemas disagree, the schemas are followed.

Source: TransactionAuthorizationProtocol/TAIPs, commit c160ae573a981828b5f8d589cda0493b04bdda95, schemas/messages and schemas/common, as pinned in the node's cited clause digests.