Skip to main content
Podium supports four payment methods. This page covers how each one works, the webhook events that drive them, and how creators get paid through Stripe Connect.

Payment Methods at a Glance


Stripe Payments

Payment Intent Flow

Creating a PaymentIntent

Response:
The amount reflects the order total minus any points discount, plus shipping fees. If a PaymentIntent already exists for this order and the points amount hasn’t changed, the existing intent is returned. If points changed, the old intent is cancelled and replaced.

Frontend Integration

Use the clientSecret with Stripe.js or Stripe Elements:

Shipping + Payment Amount Updates

When a shipping quote is requested, the shipping fee is added to the order and the Stripe PaymentIntent amount is updated automatically:

Stripe Webhooks

Podium listens for these Stripe webhook events: All webhook endpoints verify the Stripe signature before processing.

Stripe Connect (Creator Payouts)

Creators receive their share of each sale through Stripe Connect. The platform retains an application fee (STRIPE_PLATFORM_APPLICATION_FEE_BPS) on each transaction.

Onboarding a Creator

Creates a Stripe Connect account for the creator. Returns an account link URL for the creator to complete onboarding (identity verification, bank details).

Payout Flow

1

Payment Received

When a customer’s payment succeeds, Stripe holds the funds.
2

Application Fee Deducted

The platform fee (configurable in BPS) is automatically deducted.
3

Transfer to Creator

Stripe creates a transfer to the creator’s Connect account. The transfer.created webhook records this in Podium as a CreatorPayout.
4

Creator Payout

Funds are deposited to the creator’s bank account on Stripe’s standard payout schedule.

x402 Payments (USDC on Base)

Machine-native payments using the HTTP 402 protocol. Agents pay with USDC — no authentication, no card entry, no human interaction. See x402 Protocol Deep Dive for the full specification.

Payment Flow

Payment Requirements Response (402)

When called without an X-PAYMENT header:

X402Payment Model


Embedded Wallet Checkout

For automated crypto checkout using Privy server-managed wallets:

How It Works

  1. Your backend uses the Privy SDK to initiate a USDC transfer from the user’s embedded wallet
  2. Wait for on-chain confirmation
  3. Submit the txHash to this endpoint
  4. Podium creates a CryptoPaymentIntent (status CONFIRMED), moves order to PAID, decrements stock
  5. OrderConfirmationEvent fires if email is provided

Request Schema


Coinbase Commerce

Multi-token crypto checkout via Coinbase Commerce:
Creates a CoinbasePayment record (status PENDING), updates order to PAID, decrements stock, and sends confirmation.

Payment Models


Endpoint Summary