BitPay published a card-program architecture guide this week. The guide documents five proven patterns operators use when scaling past 10 cards, plus the trade-offs of each and the hybrid approaches most operators end up running.
The five patterns: by department (ads, content, engineering, sales), by ad account (one card per platform account), by vendor type (SaaS, cloud, AI tools, advertising, travel, marketplace), by risk profile (low-trust vs high-trust vendors), and by time horizon (cards with 7-day expiry for trial vendors, perpetual for operational use).
Most operators run a hybrid. A media buyer running 20 ad accounts might use ad-account isolation for advertising (one card per account) plus by-risk-profile for marketplace vendors. An agency running 15 client engagements might use by-department for internal spend plus by-ad-account for client campaigns.
The guide covers 13 pages with diagrams, decision frameworks, and worked examples. Each architecture is documented with: what it optimizes for, what trade-offs it has, when to use it, and how it interacts with the other architectures. Operators can use the guide to plan their program structure before scaling.
