The boring but correct answer.
There are reasons to use other processors — geographic coverage, lower fees, alternative payment methods — but for a small commerce layer built into a CMS, Stripe is the right default. It has the best developer documentation, the most reliable webhook infrastructure, and the broadest support across browsers and devices. Most Devani sites that need to sell something can use Stripe and never think about payments infrastructure again.
The integration surface.
One-time payments
Physical, digital, and pay-what-you-want products all check out through a Stripe Checkout session. Devani builds the session, redirects the customer, handles the return.
Subscriptions
Subscription products use Stripe's recurring billing. Plan name, amount, interval, optional trial period. Customer management runs through your Stripe dashboard, not a Devani admin screen we'd have to maintain.
Webhooks
Stripe pushes order status changes (completed, failed, refunded) to a Devani webhook endpoint. Your order records update automatically without polling.
Stripe Tax
If you enable Stripe Tax, it handles VAT, GST, and US sales tax automatically. Devani passes the line items through; Stripe does the rest.
About fifteen minutes.
No code, no plugin marketplace, no integration wizard. The flow is short.
- Create a Stripe account (free)
- Paste your publishable and secret keys into Devani settings
- Copy Devani's webhook URL into your Stripe webhook configuration
- Pick the events you want Devani to receive (the defaults are sensible)
- Sell something to make sure it works end to end
On your server.
Every successful checkout creates an order record on your Devani install — customer email, shipping details, line items, total, currency, and a reference to the original Stripe session for audit. You own those records. If you ever leave Devani, your order history goes with you.
Sell. Get paid. Done.
Stripe checkout, built into Devani. Free with the CMS — Stripe charges its normal processing fees.