Expand description
Implementation of the Transaction Authorization Protocol (TAP)
This crate provides the core functionality for the Transaction Authorization Protocol (TAP), including message definitions, serialization, validation, and DIDComm integration.
The Transaction Authorization Protocol (TAP) is a multi-party protocol for authorizing, documenting, and recording financial transactions for cryptocurrency asset transfers.
Re-exports§
pub use didcomm::Attachment;pub use didcomm::AttachmentData;pub use didcomm::Base64AttachmentData;pub use didcomm::JsonAttachmentData;pub use didcomm::LinksAttachmentData;pub use didcomm::OutOfBand;pub use didcomm::PlainMessage;pub use didcomm::PlainMessageExt;pub use didcomm::UntypedPlainMessage;pub use error::Error;pub use error::Result;pub use message::create_tap_message;pub use message::AddAgents;pub use message::Agent;pub use message::Authorize;pub use message::DocumentReference;pub use message::ErrorBody;pub use message::Invoice;pub use message::LineItem;pub use message::MessageContext;pub use message::OrderReference;pub use message::Party;pub use message::Payment;pub use message::Presentation;pub use message::Reject;pub use message::Settle;pub use message::TapMessageBody;pub use message::TaxCategory;pub use message::TaxSubtotal;pub use message::TaxTotal;pub use message::TransactionContext;pub use message::Transfer;
Modules§
- didcomm
- error
- Error types for the tap-msg crate.
- message
- Message types and processing for TAP messages.
- utils
- Utility functions for TAP core
Derive Macros§
- TapMessage
- Procedural derive macro for implementing TapMessage, MessageContext, and optionally TapMessageBody traits.
- TapMessage
Body