# Crypto payments for SaaS checkout and invoices

Canonical: https://apa.app/solutions/crypto-payments-for-saas

Add crypto payment links or API checkout sessions to SaaS billing flows while keeping settlement non-custodial.

## Product fit

### Use links for manual invoices and API sessions for app checkout

Early SaaS teams can start with payment links for annual invoices or manual renewals. Product-led teams can create checkout sessions from the backend and reconcile through webhooks.

- Payment links for sales-led invoices
- API sessions for self-serve checkout
- Order id and metadata for workspace, plan and customer references

### Activate access only after a signed paid event

Crypto payments are asynchronous. A SaaS backend should treat the hosted redirect as customer UX and use signed webhook events as the source of truth for activating or renewing access.

- Listen for payment.paid before provisioning
- Handle expired and failed sessions cleanly
- Record refund-required states for support follow-up

## Key capabilities

- Works without custody: Subscription or invoice payments settle to your wallet instead of a processor balance.
- Stablecoin-friendly: Receive USDC or USDT on supported networks to reduce crypto price noise.
- Developer-ready: Use checkout sessions, metadata, idempotency and webhooks for SaaS billing logic.

## FAQ

### Can SaaS teams use Apa for recurring subscriptions?

Apa currently fits checkout sessions and payment links. Recurring billing can be built by creating new payment requests for renewal cycles.

### Can I attach workspace or customer metadata?

Yes. Metadata and order ids are echoed on payment objects and webhook events.

### When should the SaaS app provision access?

After a signed terminal success event such as payment.paid, not merely after a browser redirect.