How can SDA be used for checkouts?

SDAs can be used for checkout flows by creating dynamic payment addresses that simplify cross-chain payments. Here's how they work for checkout scenarios:

QR Code Payment Flow

You can generate an SDA on any supported chain (like Solana) with the destination address being your merchant account on another chain (like Ethereum). Then build a deep link into a QR code so users only need to scan and confirm the transaction in their wallet. As a fallback, you can display the SDA address and required amount directly.

Cross-Chain Payment Acceptance

SDAs enable you to accept payments from any supported chain without requiring users to bridge funds themselves. For example, a user can pay with USDC on Arbitrum while your system receives USDT on Tron - the SDA handles the cross-chain bridging and token conversion automatically.

Embedded Payment Solutions

SDAs work well for embedded payment products where you want to abstract away blockchain complexity from users. The system can automatically handle deposits from multiple chains and convert them to your preferred token on your preferred chain.

Payment ID Tracking

You can use the addressNote field to add payment IDs or order references to each SDA, making it easier to reconcile payments with specific orders or customers.

Multi-Chain Flexibility

Users can pay from CEXs, different wallets, or any supported chain, while you receive funds in a standardized format on your preferred chain. This significantly reduces friction in the checkout process by eliminating the need for users to manually bridge or swap tokens before payment.

The checkout use case is particularly interesting because it addresses the common problem of users having funds on different chains than what merchants accept, making payments more accessible and user-friendly.