Payment Stack Guide Find providers
← Learning libraryoperations · reviewed 2026-07-27

What you still handle with direct payments

Direct payments give you control. They also leave a larger operating surface attached to your company.

9 minute readFoundersOperationsFinance
00Key takeaways

The short version.

  • Direct payment acceptance leaves the merchant responsible for the customer sale.
  • Tax, disputes, billing, support, security, and reconciliation need named owners even when software automates parts of them.
  • The direct model is strongest when control and modularity are intentional rather than accidental.
01

The sale and customer contract

Your company is normally named as the seller, sets the sale terms, issues the commercial promise, fulfills the product, defines the refund policy, and supports the customer. The payment provider's own terms govern its payment service, not your product obligations.

02

Indirect tax

Your business determines where it has registration obligations, registers where required, validates customer location and status, calculates tax, keeps evidence, files returns, remits funds, and handles notices or audits. Tax software can automate pieces of this workflow, but ordinary calculation does not transfer the liability.

03

Payment operations

You configure fraud controls, monitor authorization and failure rates, respond to disputes, manage refunds, reconcile payouts, and support billing questions. Providers supply important tools, but eligibility rules and protection limits decide what they actually absorb.

04

Billing and records

Subscriptions require catalog, proration, retry, cancellation, invoice, credit, and entitlement logic. You must preserve financial and tax records even if the provider dashboard later changes or the account closes. Export and migration planning should begin before you need to switch.

Use this before choosing

Decision checklist.

  1. Assign an owner for tax registrations, filings, and remittance.
  2. Write the refund, dispute, and failed-payment workflows.
  3. Confirm PCI DSS and checkout-security responsibilities.
  4. Reconcile orders through provider balances and bank payouts.
  5. Maintain an exit path for customer, payment, and subscription data.
Stories from the field

How this shows up in real businesses.

These are anecdotes and first-party accounts, not policy evidence. Use them to discover questions worth verifying.

indie hackers · first personAn early founder reaches revenue before understanding sales tax

A founder describes launching direct and Gumroad sales before building a clear VAT, GST, and sales-tax process, a common sequence that turns tax architecture into a reactive task.

The discussion is informal and jurisdiction-specific comments may be incomplete or outdated.
Primary sources

Review the evidence.

  1. Stripe Tax product and responsibility contextReviewed 2026-07-27
  2. PayPal Checkout options and risk responsibilitiesReviewed 2026-07-27