> For the complete documentation index, see [llms.txt](https://cryptic-documentation.gitbook.io/cryptic-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptic-documentation.gitbook.io/cryptic-documentation/technology/2.-technology-overview/2.3-blockchain-and-payment-infrastructure.md).

# 2.3 Blockchain & Payment Infrastructure

#### **Crypto-Native Payment Layer**

Cryptic’s payment infrastructure is designed to bring wallet functionality, transaction coordination, and digital settlement closer to the communication experience.

Rather than forcing users to move between communication tools, wallets, DEX interfaces, and payment tools, Cryptic brings communication and crypto-native payment flows into one product stack across Mobile, Desktop, and SDK infrastructure.

#### **Solana Execution Layer**

Cryptic uses Solana infrastructure to support fast, low-cost transaction activity across its product surfaces.

Solana enables practical payment flows, wallet actions, token transfers, and DeFi interactions inside the Cryptic experience, while additional blockchain support can expand the addressable market over time.

#### **Transaction Authorization & Compatibility**

Cryptic uses post-quantum cryptography for secure communication, identity, invite flows, and protocol-level verification.

For blockchain transactions, Cryptic remains compatible with the signature schemes required by supported networks. This allows the platform to combine post-quantum communication security with existing blockchain execution environments.

> *Cryptic’s approach is practical: strengthen communication and coordination with post-quantum security while remaining compatible with the blockchain networks users already rely on.*

#### **Integrated Wallet & Payment Flows**

Cryptic supports wallet and payment functionality through Mobile and Desktop product surfaces.

This can include:

* Wallet balances and sends
* Contact-based payments
* QR-based payment flows
* Transaction history and confirmation feedback
* Payment coordination inside secure communication flows
* Fiat on-ramp support through integrated providers
* Card-related flows through supported crypto card integrations

#### **DeFi & Routing Integrations**

Cryptic Desktop expands the payment layer into a broader financial workflow surface.

Supported and planned integration categories include:

* **Token swaps and routing** through Jupiter-style swap infrastructure
* **Lending and borrowing** through Kamino-style DeFi workflows
* **Privacy transaction flows** through Privacy Cash-style integrations
* **Permanent storage workflows** through Irys / Arweave
* **Wallet and dApp connectivity** through WalletConnect / Reown and related infrastructure

These integrations allow Cryptic Desktop to become more than a communication tool. It becomes a secure workspace where users can communicate, coordinate, and take financial action without constantly switching between tools.

#### **Privacy-Aware Financial Coordination**

Cryptic is designed for users who care about privacy, control, and secure coordination.

Privacy depends on the specific flow, integration, and network used. Cryptic’s role is to bring private communication, non-custodial wallet functionality, and supported privacy tools closer together inside one user experience.

This can support:

* Private payment coordination
* Secure transaction discussions
* Encrypted file and record sharing
* DeFi workflow coordination
* Team and community financial operations
* More controlled communication around digital value movement

#### **Real-Time Settlement Feedback**

Transaction state and confirmation updates can be returned to users through the app experience, creating a more responsive payment and wallet workflow while preserving non-custodial control where applicable.

> *Cryptic’s payment infrastructure is built around a simple idea: communication and value movement should not live in separate worlds.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cryptic-documentation.gitbook.io/cryptic-documentation/technology/2.-technology-overview/2.3-blockchain-and-payment-infrastructure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.