# Stripe
Connect Stripe as the payment account behind Plandalf offers, then test checkout, products, prices, and payout behavior before going live.
Source: /docs/platforms/stripe
Last modified: 2026-06-19
Stripe is the primary payment account behind Plandalf offers. Plandalf orchestrates checkout, products, prices, invoices, coupons, bumps, and automation context while money still lands in your Stripe account.


> **Plandalf is payment-adjacent**
>

  Your Stripe account remains the processor account of record. Plandalf reads and writes through Stripe; it does not become your merchant of record.


## The path


### Connect the Stripe account


    Open the Stripe integration from the Plandalf dashboard and authorize the account that should receive payments.


### Import or create products and prices


    Use existing Stripe products/prices when they already exist, or create Plandalf products and prices for the offer.


### Attach Stripe-backed prices to the offer


    Put the products, prices, bumps, variants, coupons, and payment options into the checkout flow.


### Run a test mode link


    Use a test checkout link before live traffic. The Numi offer share screen runs test sessions against the organization's Stripe test account.


## What Stripe owns


### Stripe-owned records


- `Account` (Stripe account; required):
    The connected account that receives payments and owns Stripe-side payment records.


- `Customers` (Stripe customer):
    Checkout can create or resolve customers through the connected Stripe account.


- `Products and prices` (Stripe objects):
    Existing Stripe prices can prefill Plandalf price fields when a product is connected.


- `Payment attempts` (Stripe payment):
    Card payments run through Stripe and should be tested before the offer goes live.


## What Plandalf owns


### Offer flow


    Pages, checkout blocks, order bumps, upsells, forms, redirects, and completion behavior.


### Commerce context


    The offer, customer, product, line item, coupon, invoice, deadline, and automation context that travels with the purchase.


### Testing path


    Test links let the team rehearse checkout without taking live payments.


### Post-purchase work


    Webhooks and Sequences can react after checkout using the structured purchase context.


## Product and price import

When a product is connected to Stripe, Numi can search Stripe prices and prefill the local price form. This helps keep amount, currency, recurring interval, and price naming aligned with Stripe without retyping everything by hand.


> **Use Stripe as the payment truth, not the checkout UI**
>

  Stripe owns the payment records. Plandalf owns the offer surface, checkout flow, and follow-up context around that payment.


## Test before live traffic


### Open the test link


    Use the test mode link from the offer share screen.


### Complete checkout with a Stripe test card


    Confirm the payment path without creating a real charge.


### Check the completed session


    Verify selected products, bumps, coupons, invoices, redirects, and automation triggers.


### Switch to live only after the flow is clean


    Test mode should catch pricing and checkout errors before customers see them.


## Related docs


### [Create an offer](/docs/offers/create)


    Attach products, prices, layout, and test sessions to a checkout flow.


### [Pricing models](/docs/offers/pricing)


    Model one-time, subscription, tiered, trial, and promo-aware prices.


### [Webhooks](/docs/api/webhooks)


    Send purchase context into your backend and automation stack.