Route on price
Every payment records the fee it paid, so a price rule can send each card to the processor that charges least for it.
Every payment, to the processor that suits it.
Route on price, approval rate, card or country. Retry soft declines, fail over when a processor is down, and see every processor's payments and fees in one ledger. On its own, or alongside the rest of Cedar.
Six of Fern & Field's payments pass through routing rules to Cedar, Processor A or Processor B. A $120 Visa goes to Cedar, which has the highest approval rate. A $24 US debit card goes to Processor A, the lowest fee. A $60 French card goes to Processor B for 3D Secure. A $45 Mastercard goes to Processor A as part of a 30% share of volume. A $32 Visa gets a soft decline on Processor B and is retried on Cedar, which approves it. A $75 card goes to Processor A, finds it down, and goes on to Cedar. Every payment lands in one ledger with the processor and the fee it paid, reconciled, with fees adding up to $10.53.
How it works.
Connect the processors you have, tell us how to choose between them, and we do the rest.
- Connected
Connect your processors
Add Stripe and other processors with your own accounts. Your rates and contracts stay yours, and your checkout doesn't change.
- Ruled
Set your rules
Route by price, approval rate, card, country, amount or a share of volume, in the dashboard or through the API.
- Routed
Route and retry
Each payment goes where its rules send it. Soft declines retry on the other processor, and if one is down, payments fail over.
- Reconciled
See it all in one ledger
Every processor's payments, fees and refunds land in one ledger, matched to your books.
Pay less. Get more approved.
And keep taking payments when a processor has a bad day, without touching your checkout.
Route on approval rate
Approval rates by card type, country and amount, on each processor, and a rule that sends each payment where it's most likely to go through.
Retry soft declines
A decline that might go through elsewhere, like a bank that didn't answer, is retried on your other processor. Hard declines never are.
Fail over when a processor is down
If a processor stops answering, payments move to the other one until it's back, and your customers never notice.
In the dashboard
When the card is debit and from the US, send it to whichever of Adyen and Stripe charges less. If it's a soft decline, retry on Stripe.
await cedar.routing.rules.create({
when: { card: "debit", country: "US" },
route: "lowest_fee",
processors: ["adyen", "stripe"],
retry: { on: "soft_decline", with: "stripe" },
});Rules in plain words, or in code.
Write a rule in the dashboard or through the API. Change it any time, and the next payment follows it.
- Split volume
- Send a share of payments to each processor, to test a new one or spread the risk.
- Route 3D Secure
- Authenticate cards where the law asks for it, on the processor you choose.
- Every change logged
- Who changed which rule, and when, is in the audit log.
Head to head.
Four ways to take payments, and what each one ties you to.
| Your rules, one ledgerCedar | Locked to one processorYour one processor | One more vendorA standalone orchestrator | Months of engineeringBuild your own | |
|---|---|---|---|---|
| Route between multiple processors (AI or custom rules) | Included | Not included | Included | Included |
| Rules without code | Included | Not included | Included | Not included |
| Cards stay yours to move | Included | Not included | Included | Included |
| PCI DSS compliance handled for you | Included | Included | Included | Not included |
| 1 place to see all your processors' fees | Included | Not included | $Extra cost | Not included |
| Same system of record as your books | Included | Not included | Not included | Not included |
Included$ Extra cost
It's all part of the bigger build.
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.
Fern & FieldCoffee Roasters**** **** **** 4242**** **** **** 4444Pay $24.00Pay $60.00
Card saved as
tok_7gq2x9Visa •••• 4242Mastercard •••• 4444You are hereRuleHighest approval rate→ Cedar
Your ledger$24.00 via CedarFee $1.00 · Sales tax $1.94$60.00 via Processor AFee $1.62 · Sales tax $4.85Booked
Questions about Payments orchestration.
Anything else? Book a call with us.
Which processors can we route to?
Stripe and Adyen, alongside Cedar Payments. You bring your own accounts, so your rates and contracts stay yours. Using another processor? Book a call and tell us which.
Does routing change our checkout?
No. Customers pay in the same checkout. Cards are saved once in Token vault, and each charge is routed behind the scenes.
How do retries avoid charging someone twice?
We retry only soft declines, like a bank that didn't answer in time, and never hard ones, like a stolen card or insufficient funds. Every attempt belongs to one payment, so a customer is charged once at most.
How do you compare processors' fees?
Every payment records the fee it paid, so the ledger shows what each processor costs you, by card type and country. A price rule sends each payment to the cheaper processor for that card.
Do we need Token vault?
Routing needs cards that every processor can charge, so they're kept in Token vault. Cards already saved with Stripe can be imported, and your customers never type them again.
Can we use Payments orchestration on its own?
Yes. Use it with the processors you have today, or alongside Cedar Payments and the rest of Cedar. The same tokens work everywhere.
Can our agents change the rules?
Yes, through the API with the permissions you give them. Every rule change is recorded in the audit log, with who made it.
Start building.
Book a call and we'll connect your processors and write your first rules with you.
Prefer email? Write to hello@usecedar.co.