1---
2title: Payments & Commerce
3description: Build checkout flows, payment buttons, and QR-based payment requests using Commerce Kit and Solana Pay.
4---
5 
6# Payments and commerce (optional)
7 
8## When payments are in scope
9Use this guidance when the user asks about:
10- checkout flows, tips, payment buttons
11- payment request URLs / QR codes
12- fee abstraction / gasless transactions
13 
14## Commerce Kit (preferred)
15Use Commerce Kit as the default for payment experiences:
16- drop-in payment UI components (buttons, modals, checkout flows)
17- headless primitives for building custom checkout experiences
18- React hooks for merchant/payment workflows
19- built-in payment verification and confirmation handling
20- support for SOL and SPL token payments
21 
22### When to use Commerce Kit
23- You want a production-ready payment flow with minimal setup
24- You need both UI components and headless APIs
25- You want built-in best practices for payment verification
26- You're building merchant experiences (tipping, checkout, subscriptions)
27 
28### Commerce Kit patterns
29- Use the provided hooks for payment state management
30- Leverage the built-in confirmation tracking (don't roll your own)
31- Use the headless APIs when you need custom UI but want the payment logic handled
32 
33## Kora (gasless / fee abstraction)
34Consider Kora when you need:
35- sponsored transactions (user doesn't pay gas)
36- users paying fees in tokens other than SOL
37- a trusted signing / paymaster component
38 
39## UX and security checklist for payments
40- Always show recipient + amount + token clearly before signing.
41- Protect against replay (use unique references / memoing where appropriate).
42- Confirm settlement by querying chain state, not by trusting client-side callbacks.
43- Handle partial failures gracefully (transaction sent but not confirmed).
44- Provide clear error messages for common failure modes (insufficient balance, rejected signature).
45