Developer Yemi outlined a checkout design for Flow on Nov. 14 that lets the recipient fix the amount and asset an invoice calls for while the payer chooses a supported asset. In his example,
Developer Yemi outlined a checkout design for Flow on Nov. 14 that lets the recipient fix the amount and asset an invoice calls for while the payer chooses a supported asset. In his example, a recipient requests 150 NEAR on the NEAR network. A customer holding SOL on Solana gets a quote for how much SOL to send to settle that request.
The design gives merchants a way to set a price in the asset they want to receive while letting customers start from a balance they already hold. Yemi built Flow for a NEAR hackathon and said its payment links use the NEAR Intents 1Click API to find a route and track delivery.
The recipient decides what asset and network they want to receive.
— Yemi (@yemigraffix) November 14, 2026
In an exact-output quote, the destination amount is fixed and the input amount can include a buffer for price changes during execution. The provider returns a deposit address and expiration time. Its documentation says that any input beyond what the swap actually uses goes back to the designated refund address after completion. The input buffer and the recipient’s payout are separate fields in the quote.
Flow’s settlement specification calls for confirming delivery on the destination chain before crediting the recipient. A transaction hash from Solana can identify the deposit. The 1Click status response distinguishes that step from delivery and can return transaction hashes for both networks, as well as a separate refund status.
The 150 NEAR invoice illustrates the proposed checkout. Flow’s published readiness report describes a separate, limited rehearsal for a single low-value Solana-to-Base payment, subject to approval. Yemi said improving mainnet settlement monitoring was among the team’s next priorities.
