Patrick Collison: Stripe and Payment Infrastructure

Stripe identifies Patrick Collison as its cofounder and chief executive officer. Its newsroom describes software used by businesses to accept payments and manage online operations, with headquarters in San Francisco and Dublin. For a US merchant, a payment provider is part of the revenue process rather than simply a button at checkout. This profile uses official public sources for the company context. The operating questions are Motenza’s editorial analysis, not an interview, a processing-price quote or a claim that Stripe is the best provider for every business.

Map the steps from an attempted purchase to money reaching the business bank account. Authorization, capture, refunds, disputes and settlement are different events. Assign responsibility for reconciling them against orders and accounting records. A successful checkout screen is not enough to prove a deposit arrived or that every order should be fulfilled. Ask how the chosen setup handles duplicate attempts, failed authentication and delayed confirmations. Test both a normal payment and a refund in an appropriate test environment before launching a new checkout workflow.

Calculate the effective processing rate from an actual statement by dividing relevant processing charges by the associated sales volume. Keep refunds, chargebacks, currency conversion and optional services visible rather than burying them inside one percentage. A hypothetical business with many small transactions can face a different cost pattern from one selling a few expensive services. Compare providers using the same transaction mix and settlement needs. Ask how records and customer payment arrangements can move if the relationship changes. The buying decision should account for support, reconciliation and continuity as well as the headline rate.