05 Run stepKnox keeps choosing the processor for each payment, by your rules, long after the agent's pull request is merged.
Routing
Choose the processor for every payment.
Connect your own processor accounts as gateways. Priority, volume-split and conditional rules decide which one takes each payment.
Playground
Write a policy. Watch it route.
Write a policy in plain language. Watch it route automagically. Edit it on the left or load a preset, and each payment is traced from Knox through the rules it matched to the processor it lands on.
The simulator re-runs as you type. Semantic ifs: is better with a network token, needs more proof, is a returning customer and choose "…". Rules: when on currency, brand, country, amount (minor units) or risk, split and choose first.
- Payments
- 0
- Approval rate
- –
- Blended cost
- –
- Stripe 0%
- Chase 0%
- Checkout.com 0%
- Adyen 0%
Latest decision
Press Play or Step to send a payment through the policy.
Earlier
Routes payments to: Stripe, Fiserv (3 integrations), NMI, and Paysafe
Rules
Three ways to route
Rules work across the processor accounts you already have. You bring the accounts; Knox decides which one takes each payment.
priorityPriority
List your gateways in order. Each payment goes to the first one that can serve it.
volume_splitVolume split
Send a share of payments to each gateway. The percentages must add up to 100.
conditionalConditional
Choose gateways by currency or amount, with a default order for every other payment.
Switching
Switch processors without a rewrite
Your code keeps calling the same Stripe API. A routing rule is set through Knox's API, and making one active replaces the rule that was active before, so changing processors does not touch your integration.
curl https://meta.knoxapi.com/v1/routing_rules -u $KNOX_SECRET_KEY: \
-d name="Split while we compare" \
-d type=volume_split \
-d "split[0][gateway]=gw_primary" -d "split[0][percent]=90" \
-d "split[1][gateway]=gw_second" -d "split[1][percent]=10" \
-d active=trueCard data
Keep card numbers off your servers
Card fields from knox.js
Knox's browser SDK renders card fields in a frame Knox serves, so card numbers never reach your page or your server.
Tokenized and vaulted
Card numbers are tokenized and held in a secure vault. Read about security
Your agent is ready when you are.
Paste the prompt into your coding agent, or start a test account and look around first. Live payments are available by request.