Stripe readiness
Charges enabled
The connected account must be ready before Pay now can be offered.
Optional card checkout · account-friendly fallback
Accept wholesale card payments without forcing every buyer online
Connect Stripe Express for Pay now orders and keep Pay later for account customers. Orderverse resolves the right checkout path before the buyer reaches the payment step.
Stripe connection is optional. Pay later ordering remains available without a ready card account.
Checkout Policy Resolver
Route this wholesale order
- stripe_ready
- true
- customer_override
- inherit
- workspace_default
- pay_now
Effective mode
Pay now
Continue to Stripe-hosted Checkout after the order is submitted.
One controlled payment path
From connected account to confirmed order
Orderverse owns the wholesale order context. Stripe enters only when the resolved checkout mode requires a card payment.
- 01
Connect the supplier account
A workspace admin starts Stripe Express onboarding from Orderverse. Card checkout stays unavailable until the connected account can accept charges.
- 02
Resolve the checkout policy
Orderverse combines Stripe readiness, the customer override and the workspace default to resolve Pay now or Pay later for the order.
- 03
Lock the submitted total
The checkout session uses the order-line price snapshot, so a later catalogue price change does not rewrite the amount already submitted.
- 04
Open Stripe-hosted Checkout
For Pay now, the buyer continues to Stripe's hosted payment page to enter card details and complete the payment attempt.
- 05
Confirm the payment result
Webhook and payment-status handling update the Orderverse order and invoice records after Stripe reports the payment outcome.
Policy before payment
Keep card checkout optional at the customer level
A single workspace can serve prepaid buyers and established account customers without maintaining separate order portals.
Customer override
Inherit · Pay now · Pay later
Keep an account customer on invoice terms or override the workspace default.
Workspace default
Pay now or Pay later
Set the normal checkout behaviour once in Order Settings.
Safety fallback: if Stripe is not connected or charges are unavailable, the effective checkout mode is Pay later—even when Pay now was selected upstream.
Product evidence
Connect payments, then choose the default checkout mode
Payments shows connected-account readiness. Order Settings controls whether the normal buyer path is Pay now or Pay later.
Two valid outcomes
Payment terms can follow the buyer relationship
Card checkout is an option inside the ordering workflow, not a requirement for every wholesale account.
Pay now
Submit the wholesale order, open Stripe-hosted Checkout and return to a payment status screen while Orderverse confirms the result.
- Requires a ready Stripe connection
- Uses the submitted order total
- Fits prepaid or card-required buyers
Pay later
Submit the order without a card step. The supplier reviews the order and handles invoicing or agreed account terms separately.
- Works without a Stripe connection
- Preserves account-based ordering
- Automatic fallback when card checkout is unavailable
Clear ownership
Know which system owns each part
| System | Owns | Important boundary |
|---|---|---|
| Orderverse | Order context, checkout policy, price snapshot, session request and payment-status record | Does not replace Stripe's hosted card-entry and payment-processing service |
| Stripe | Connected-account onboarding, hosted Checkout, payment processing and payout capability | Account requirements, availability, processing fees and payout timing remain subject to Stripe |
| Supplier | Customer terms, workspace default, customer overrides and connected-account compliance | Confirm commercial, accounting and refund policies before rollout |
Check the implementation boundaries
Orderverse behaviour is documented locally. Stripe platform facts were reviewed against official Stripe documentation on 14 August 2026.
Orderverse Payments
Connection status, capabilities, actions and checkout fallback.
Product documentationOrderverse Checkout
Pay now, Pay later, customer override and buyer result flow.
Product documentationStripe Checkout
Official overview of Stripe-hosted Checkout and Checkout Sessions.
Official sourceStripe Connected Accounts
Official account-type, onboarding and connected-account guidance.
Official sourcePayment questions
Stripe wholesale payment FAQ
Confirm Stripe availability, fees, payout timing and compliance requirements for your own connected account before going live.
Do all wholesale customers have to pay by card?
No. A workspace can default to Pay later, and a customer can inherit or override the workspace setting. This lets you offer card checkout to selected buyers while keeping invoice-based ordering for established account customers.
What happens if Stripe is not connected or ready?
Orderverse resolves the order to Pay later when the Stripe connection is missing or charges are not enabled. The buyer can still submit the order without entering card details.
Where does the buyer enter card details?
For Pay now, the buyer is redirected to a Stripe-hosted Checkout page. Orderverse creates the Checkout Session from the submitted order and handles the return and payment-status workflow.
Can payment behaviour differ by customer?
Yes. Customer checkout settings support Inherit, Pay now and Pay later. The effective result still checks Stripe readiness, so an unavailable card connection cannot force a broken card step.
Can product price changes alter an order already sent to payment?
No. The Checkout Session is created from the price snapshot stored with the submitted order lines. Later catalogue changes apply to future orders, not the submitted total.
Does the public Orderverse demo take a real payment?
No. The demo is deliberately isolated and does not connect to a Stripe account, create a Checkout Session or take a payment. The product screenshots and documentation show the real configuration boundaries.
Continue through the wholesale workflow
Wholesale order form
See the full buyer form, fulfilment details and structured order output.
Read the guideCustomer pricing
Resolve customer and UOM prices before the order reaches checkout.
Read the guideNo-login ordering
Let repeat buyers open their ordering context without an account password.
Read the guideXero ordering
Follow the separate accounting handoff after the Orderverse order.
Read the guideChoose the payment path per buyer
Add card checkout without removing Pay later
Start with the wholesale ordering workflow, connect Stripe when you are ready and keep established customer terms under your control.