Send customers from your app to a pay page we host. They pay by card, ACH, Apple Pay or Google Pay, and come straight back to you, paid. One API call, nothing to design.
On Fern & Field Coffee's website, a customer presses Checkout for a cold brew soda 12-pack. Fern & Field's server creates a checkout session with one API call and gets back a pay_url. The browser goes to the Cedar-hosted pay page, where the customer can pay with Apple Pay, Google Pay, a card or a bank account. They pay $24.00 by card and the browser returns to Fern & Field's thank-you page. A checkout_session.updated webhook tells Fern & Field's server the session is completed, and Cedar emails the customer a receipt.
Address autocomplete, autofill and real-time card validation get customers through the form fast, and returning customers pay in a tap with CedarGo. Optional 3D Secure and network tokenization help more payments go through.
The checkout looks and feels like part of your site, yet card details never touch your servers. You stay compliant without the extra work, and go live faster.
Change the checkout's colors, font, shapes and brand settings to match your own, then embed it right on your website.
Once a payment goes through, Cedar emails the customer a PDF receipt. There's nothing for you to send.
In the dashboard, Cedar suggests three changes to Fern & Field Coffee's checkout: show Apple Pay first on iPhone, drop the phone number field, and offer bank transfers. Fern & Field turns on all three. A $24.00 Apple Pay payment comes in, and a chart of paid checkouts rises from the day the changes were turned on.
Send the order from your own app and get back a link to a pay page we host. Send the customer there, and we send them back to you once they've paid.
curl https://api.usecedar.co/v1/checkout_sessions \
-H "Authorization: Bearer $CEDAR_SECRET_KEY" \
-H "Idempotency-Key: order-1042" \
-H "Content-Type: application/json" \
-d '{
"currency": "USD",
"line_items": [
{
"name": "Cold brew soda, 12-pack",
"quantity": 1,
"unit_amount": 2206,
"currency": "USD"
}
],
"tax_amount": 194,
"customer_email": "maya@hollis.studio",
"success_url": "https://fernandfield.coffee/thanks"
}'Response
{
"id": "cs_4Tq8Vn2k",
"status": "open",
"amount_total": 2400,
"currency": "USD",
"pay_url": "https://pay.usecedar.co/checkout/cpt_7Kq2mX…",
"expires_at": "2026-09-26T15:34:00Z"
}Follow one payment from the checkout to your books. It passes through six blocks, and they fit together on one system of record.
A customer pays on Hosted checkout. The card goes into Token vault and comes out as a token. A second customer pays with another card, saved as a token of its own. Payments orchestration picks a processor: the first payment goes to Cedar for the highest approval rate, the second to Processor A for the lowest fee. Both are approved, and Accounting and Tax book each one with its fee and sales tax.
tok_7gq2x9Visa •••• 4242Mastercard •••• 4444Anything else? Book a call with us.
A pay page that Cedar hosts for you. Your app creates a checkout session with one API call, sends the customer to its link, and gets them back once they've paid.
By card, ACH bank transfer, Apple Pay or Google Pay, all on the same page.
Your business name, what they're buying with any tax, shipping and discount, and the total due. Once they pay, they head straight back to your site.
Cedar sends your server a checkout_session.updated webhook and the session's status turns completed. You can also read the session back at any time.
30 minutes, unless you set your own expiry when you create it. A link closes for good once it's paid, expired or canceled.
Yes. Create a checkout session in the dashboard with line items, tax, shipping and a discount, then open or share its pay page.